Third-party tool
grok-bot-cli
What job it does
List your Grok Bot roster and send messages from a terminal by reusing an already signed-in macOS desktop session — a side door for power users who live in the shell.
Platforms
macOS only in practice: it depends on a logged-in official Grok Bot desktop session on the same machine. Not a cloud API client.
Install
Follow the README at ScriptedAlchemy/grok-bot-cli. Typical flow: clone or install the published package, keep the official Grok Bot app signed in, then use the CLI to list Bots and post messages. The CLI does not replace in-app approvals, Take Over Computer, or Teach a task.
How it differs from the official app
Unlike the official desktop, this is a third-party terminal bridge. Unlike Grok Build / grok-app, it talks to Grok Bot teammates (roster + messaging), not a local coding CLI. Unlike grok-bot-skill, it is meant for humans at a prompt, not for Cursor/Claude coding agents.
What the CLI can and cannot do
Treat grok-bot-cli as a side door into an already-running official desktop session. Typical jobs: list the roster, post a message you would have typed in the app, and script a check you already trust. It does not open Agent Computer, does not Take Over for passwords or 2FA, does not show the secrets card, and does not replace Require Approval. Teach a task, routines, and plugin OAuth still live in the official app. If a command would send mail, spend money, or change production, stop and do that click in the desktop or phone client where you can watch the computer.
Session reuse on macOS
The useful trick is also the risk. The CLI reuses login state from the signed-in Grok Bot desktop app on the same Mac. That is why it is not a cloud API client and why it does not help a Linux box or a CI runner. Quit the official app, lock the session, or sign out, and the CLI should go quiet. Do not copy session files into another user account, a VM, or a gist. Anyone with that state can act as you and burn the weekly usage pool. Prefer a dedicated Mac user if you must leave a session open for scripts.
Approvals and weekly usage still apply
Messages sent from a terminal still count as Grok Bot work on the Cursor account. Chief-of-Staff chatter and long inbox walks burn the weekly pool the same way they do in the app. On-Demand spillover still follows the cost lesson on this site. The CLI will not warn you that the pool is empty. Pair it with the official plans screen or a usage meter, and keep Auto-review / Require Approval rules in the official client — a shell wrapper is not a second policy engine. Read the upstream README for the current command list before you alias anything to send. If a script fails with a stale session after a password change, sign out of the official Mac app completely, quit it, sign in again, then retry the CLI — do not treat that as a missing plan.
Risks
It may reuse local login state from the official app. Treat it like any tool that can act as you: review outbound messages, do not paste secrets into chat, and do not use it to bypass Require Approval. License and maintenance status belong to the upstream repo — verify before production use.
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.