Third-party tool
grokbot-tui
What job it does
A third-party terminal user interface for interacting with Grok Bot from the keyboard — useful when you want roster/chat workflows without leaving a terminal multiplexer.
Platforms
Follow the smarzban/grokbot-tui README for supported OS versions and runtime requirements. Expect it to sit beside — not replace — the official desktop/mobile clients.
Install
Install per the repository README (language runtime, binary, or package manager as documented there). Sign in / authenticate the way the project documents. Keep official apps for computer takeover, Teach a task, and plugin OAuth.
How it differs from the official app
A TUI is a presentation layer. It is not the official Grok Bot client, not the Grok Build coding CLI, and not grok-app (the Tauri GUI for Grok Build). Feature parity with desktop (Agent Computer preview, routines UI, secrets cards) will lag or be missing.
What the TUI is for
Use grokbot-tui when you already live in a terminal multiplexer and want roster or chat keystrokes without opening the Electron window. Typical jobs: switch Bots, read a thread, send a message you would have typed in the app. It is a presentation layer on the same account. It is not the official client, not grok-bot-cli (scripted commands), not grok-app (a Grok Build GUI), and not a second computer.
What will be missing
Expect Agent Computer preview, Teach a task, secrets cards, plugin OAuth, Recover / Update / Reset, and routine webhook controls to lag or be absent. Those stay on the official desktop or phone. If a keystroke would send mail, spend money, or change production, switch to the official app and watch the computer. Feature lists in the README change — read the current one before you treat the TUI as your only door.
Tokens, Recover, and usage
A TUI that stores session cookies or tokens locally expands the same surface as grok-bot-cli. Do not copy that state into a gist, a VM, or another user. Messages still burn the weekly pool. If the official desktop is black but iOS still works, Recover before Reset — a TUI reconnect is not a rebuild. Prefer official paths for payments, OAuth plugins, and computer surgery. Verify the repo is maintained before you leave a token on disk.
Risks
Any TUI that stores tokens or session cookies locally expands your attack surface. Prefer official paths for payments, OAuth plugins, and Reset/Recover. Verify upstream license and whether the project is actively maintained.
License and source
License. As declared in the upstream repository README
Open GitHub source Prefer official install Symptom-based fixes
Third-party tools can touch a local session. They do not replace Require Approval, secrets cards, or Recover/Update in the official desktop app.