grok-cli

Grok CLI

Use Grok Build as a separate coding agent on the same machine. The bundled client launches grok agent --no-leader stdio, keeps its ACP session open, and returns a task ID immediately. This is an external task: it does not appear in Codex's native spawn_agent tree or inherit its conversation.

Grok Build must already be installed and configured. Use the project's Python 3.12+ interpreter to run scripts/grok.py; the client uses only the standard library. If the project has no interpreter, uv run --python 3.12 <script> ... also works. Resolve the script relative to this installed skill, not the repository being investigated.

Delegate a task

Give Grok the goal, absolute working directory, relevant files and evidence, scope boundaries, and the check that proves completion. It cannot see the conversation that led to the assignment. Keep independent work with the supervising agent while Grok runs.

Use a UTF-8 prompt file for substantial instructions. In these examples, <script> is the absolute path to this skill's scripts/grok.py:

python <script> start --cwd <absolute-project-path> --prompt-file <task-file>
python <script> wait <task_id> --timeout 30
python <script> status <task_id>
python <script> reply <task_id> --prompt-file <follow-up-file>
python <script> cancel <task_id>
python <script> close <task_id>

Retain the returned task_id. Use wait when there is no independent work left; its timeout returns the current state without cancelling the task. Use reply after the current turn finishes to continue the same Grok session. A running turn must finish or acknowledge cancellation before a follow-up is accepted. Close the task once no more follow-ups are needed.

The helper's --help is the command reference. For output fields, storage, timeouts, and troubleshooting, read references/client.md.

Configuration and permissions

Inherit Grok's model, authentication, and permission configuration unless the task requires a specific override. Subscription login, API keys, and configured providers are Grok's concern; do not change the user's configuration or choose another authentication route to get past a failure. The helper uses Grok's advertised noninteractive default authentication method when available. Interactive authentication is completed separately through Grok itself.