Grok CLI
An open-source autonomous agent powered by Grok.
Ask AI about Grok CLI
Powered by Claude · Grounded in docs
I know everything about Grok CLI. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
grok-cli: an open-source coding agent for the Grok API
CI npm License: MIT TypeScript Bun
Disclaimer: This project is community-built, open-source, and not affiliated with, endorsed by, or sponsored by xAI Corp. "Grok" is a trademark of xAI Corp. This tool uses the publicly available Grok API.
An open-source terminal coding agent that connects to xAI’s Grok API — real-time X search, web search, the full Grok model lineup, sub-agents on by default, remote control via Telegram (pair once, drive the agent from your phone while the CLI runs), and a terminal UI built with Bun and OpenTUI.
https://github.com/user-attachments/assets/7ca4f6df-50ca-4e9c-91b2-d4abad5c66cb
Install
curl -fsSL https://raw.githubusercontent.com/superagent-ai/grok-cli/main/install.sh | bash
Alternative installs (requires Bun on PATH):
bun add -g grok-dev
Self-management (script-installed only):
grok update
grok uninstall
grok uninstall --dry-run
grok uninstall --keep-config
Prerequisites: a Grok API key from x.ai and a modern terminal emulator for the interactive OpenTUI experience. Headless --prompt mode does not depend on terminal UI support. If you want host desktop automation via the built-in computer sub-agent, also enable Accessibility permission for your terminal app on macOS.
Run it
Interactive (default) — launches the OpenTUI coding agent:
grok
Supported terminals
For the most reliable interactive OpenTUI experience, use a modern terminal emulator. We currently document and recommend:
- WezTerm (cross-platform)
- Alacritty (cross-platform)
- Ghostty (macOS and Linux)
- Kitty (macOS and Linux)
Other modern terminals may work, but these are the terminal apps we currently recommend and document for interactive use.
Pick a project directory:
grok -d /path/to/your/repo
Headless — one prompt, then exit (scripts, CI, automation):
grok --prompt "run the test suite and summarize failures"
grok -p "show me package.json" --directory /path/to/project
grok --prompt "refactor X" --max-tool-rounds 30
grok --prompt "summarize the repo state" --format json
grok --prompt "review the repo overnight" --batch-api
grok --verify
--batch-api uses xAI's Batch API for lower-cost unattended runs. It is a good
fit for scripts, CI, schedules, and other non-interactive workflows where a
delayed result is fine.
Continue a saved session:
grok --session latest
grok -s <session-id>
Works in interactive mode too—same flag.
Structured headless output:
grok --prompt "summarize the repo state" --format json
--format json emits a newline-delimited JSON event stream instead of the
default human-readable text output. Events are semantic, step-level records such
as step_start, text, tool_use, step_finish, and error.
Computer sub-agent
Grok ships a built-in **computer** sub-agent backed by [agent-desktop](https://github.com/lahfir/agent-desktop) for host desktop automation on macOS.
Ask for it in natural language, for example:
grok "Use the computer sub-agent to take a screenshot of my host desktop and tell me what is open."
grok "Use the computer sub-agent to launch Google Chrome, snapshot the UI, and tell me which refs correspond to the address bar and tabs."
Notes:
- Screenshots are saved under
**.grok/computer/**by default. - The primary workflow is snapshot -> refs -> action -> snapshot using
agent-desktopaccessibility snapshots and stable refs like@e1. computer_screenshotis available for visual confirmation, but the preferred path iscomputer_snapshotplus ref-based actions such ascomputer_click,computer_type, andcomputer_scroll.- macOS requires System Settings → Privacy & Security → Accessibility access for the terminal app running
grok. agent-desktopcurrently targets macOS.- If Bun blocks the native binary download during install, run:
node ./node_modules/agent-desktop/scripts/postinstall.js
Scheduling
Schedules let Grok run a headless prompt on a recurring schedule or once. Ask for it in natural language, for example:
Create a schedule named daily-changelog-update that runs every weekday at 9am
and updates CHANGELOG.md from the latest merged commits.
Recurring schedules require the background daemon:
grok daemon --background
Use /schedule in the TUI to browse saved schedules. One-time schedules start
immediately in the background; recurring schedules keep running as long as the
daemon is active.
List Grok models and pricing hints:
grok models
Pass an opening message without another prompt:
grok fix the flaky test in src/foo.test.ts
Generate images or short videos from chat:
grok "Generate a retro-futuristic logo for my CLI called Grok Forge"
grok "Edit ./assets/hero.png into a watercolor poster"
grok "Animate ./assets/cover.jpg into a 6 second cinematic push-in"
Image and video generation are exposed as agent tools inside normal chat sessions.
You keep using a text model for the session, and Grok saves generated media under
.grok/generated-media/ by default unless you ask for a specific output path.
What you actually get
| Thing | What it means |
|---|---|
| Built for the Grok API | Defaults tuned for the xAI API; models like grok-4.3, grok-4.20-non-reasoning, grok-4.20-multi-agent-0309, plus current flagship and multi-agent variants—run grok models for the full menu. |
| X + web search | **search_x** and **search_web** tools—live posts and docs without pretending the internet stopped in 2023. |
| Media generation | Built-in **generate_image** and **generate_video** tools for text-to-image, image editing, text-to-video, and image-to-video flows. Generated files are saved locally so you can reuse them after the xAI URLs expire. |
| Sub-agents (default behavior) | Foreground **task** delegation (e.g. explore, general, or computer) plus background **delegate** for read-only deep dives—parallelize like you mean it. |
| Verify | **/verify** or **--verify** — inspects your app, builds, tests, boots it, and runs browser smoke checks in a sandboxed environment. Screenshots and video included. |
| Computer use | Built-in **computer** sub-agent for host desktop automation via **agent-desktop**. It prefers semantic accessibility snapshots and stable refs, with screenshots saved under **.grok/computer/** when requested. |
| Custom sub-agents | Define named agents with **subAgents** in **~/.grok/user-settings.json** and manage them from the TUI with **/agents**. |
| Remote control | Pair Telegram from the TUI (/remote-control → Telegram): DM your bot, **/pair**, approve the code in-terminal. Keep the CLI running while you ping it from your phone. |
| No “mystery meat” UI | OpenTUI React terminal UI—fast, keyboard-driven, not whatever glitchy thing you’re thinking of. |
| Skills | Agent Skills under **.agents/skills/<name>/SKILL.md** (project) or **~/.agents/skills/** (user). Use **/skills** in the TUI to list what’s installed. |
| MCPs | Extend with Model Context Protocol servers—configure via **/mcps** in the TUI or **.grok/settings.json** (mcpServers). |
| Sessions | Conversations persist; **--session latest** picks up where you left off. |
| Headless | **--prompt** / **-p** for non-interactive runs—pipe it, script it, bench it. |
| Hackable | TypeScript, clear agent loop, bash-first tools—fork it, shamelessly. |
Coming soon
Deeper autonomous agent testing — persistent sandbox sessions, richer browser workflows, and stronger "prove it works" evidence.
API key (pick one)
Environment (good for CI):
export GROK_API_KEY=your_key_here
**.env** in the project (see .env.example if present):
GROK_API_KEY=your_key_here
CLI once:
grok -k your_key_here
Saved in user settings — ~/.grok/user-settings.json:
{ "apiKey": "your_key_here" }
Optional **subAgents** — custom foreground sub-agents. Each entry needs **name**, **model**, and **instruction**:
{
"subAgents": [
{
"name": "security-review",
"model": "grok-4.3",
"instruction": "Prioritize security implications and suggest concrete fixes."
}
]
}
Names cannot be general, explore, vision, verify, or computer because those are reserved for the built-in sub-agents.
Optional: **GROK_BASE_URL** (default https://api.x.ai/v1), **GROK_MODEL**, **GROK_MAX_TOKENS**.
Telegram (remote control) — short version
- Create a bot with @BotFather, copy the token.
- Set
**TELEGRAM_BOT_TOKEN**or add**telegram.botToken**in~/.grok/user-settings.json(the TUI**/remote-control**flow can save it). - Start
**grok**, open**/remote-control**→ Telegram if needed, then in Telegram DM your bot:**/pair**, enter the 6-character code in the terminal when asked. - First user must be approved once; after that, it’s remembered. Keep the CLI process running while you use the bot (long polling lives in that process).
Voice & audio messages
Send a voice note or audio attachment in Telegram and Grok will transcribe it with the Grok Speech-to-Text API (POST https://api.x.ai/v1/stt) before passing the text to the agent. The endpoint accepts Telegram's OGG/Opus voice notes and common audio containers (MP3, WAV, M4A, FLAC, AAC) directly — no local model download, whisper-cli, or ffmpeg required.
Prerequisites
- A valid
GROK_API_KEY(the same key used for the agent). Transcription reuses the CLI'sapiKey/baseURLresolution, so if the agent can reach xAI, transcription will too.
Configure in ~/.grok/user-settings.json
{
"telegram": {
"botToken": "YOUR_BOT_TOKEN",
"audioInput": {
"enabled": true,
"language": "en"
}
}
}
| Setting | Default | Description |
|---|---|---|
enabled | true | Set to false to ignore voice/audio messages entirely. |
language | en | Language code forwarded to /v1/stt. Enables Inverse Text Normalization (numbers, currencies, units → written form). |
Optional headless flow when you do not want the TUI open:
grok telegram-bridge
Treat the bot token like a password.
Hooks
Hooks execute shell commands at key agent lifecycle events — enforce policies, run linters, trigger tests, or log activity.
Configure in ~/.grok/user-settings.json:
{
"hooks": {
"PreToolUse": [
{
"matcher": "bash",
"hooks": [
{
"type": "command",
"command": "./scripts/lint-before-edit.sh",
"timeout": 10
}
]
}
]
}
}
Hook commands receive JSON on stdin (event details) and can return JSON on stdout. Exit code 0 = success, 2 = block the action, other = non-blocking error.
Supported events: PreToolUse, PostToolUse, PostToolUseFailure, UserPromptSubmit, SessionStart, SessionEnd, Stop, StopFailure, SubagentStart, SubagentStop, TaskCreated, TaskCompleted, PreCompact, PostCompact, Notification, InstructionsLoaded, CwdChanged.
Instructions & project brain
**AGENTS.md** — merged from git root down to your cwd (Codex-style; see repo docs).**AGENTS.override.md**wins per directory when present.
Project settings
Project file: **.grok/settings.json** — e.g. the current model for this project.
Sandbox
Grok CLI can run shell commands inside a Shuru microVM sandbox so the agent can't touch your host filesystem or network.
Requires macOS 14+ on Apple Silicon.
Enable it with --sandbox on the CLI, or toggle it from the TUI with /sandbox.
When sandbox mode is active you can configure:
- Network — off by default; enable with
--allow-net, restrict with--allow-host - Port forwards —
--port 8080:80 - Resource limits — CPUs, memory, disk size (via settings or
/sandboxpanel) - Checkpoints — start from a saved environment snapshot
- Secrets — inject API keys without exposing them inside the VM
All settings are saved in ~/.grok/user-settings.json (user) and .grok/settings.json (project).
Verify
Run **/verify** in the TUI or **--verify** on the CLI to verify your app locally:
grok --verify
grok -d /path/to/your/app --verify
The agent inspects your project, figures out how to build and run it, spins up a sandbox, and produces a verification report with screenshots and video evidence. Works with any app type.
Troubleshooting
Common issues and solutions:
Installation issues
Install script fails on macOS
Make sure you have a modern shell and curl available:
# Verify curl is installed
which curl
# If using an outdated shell, try with bash explicitly
bash -c "$(curl -fsSL https://raw.githubusercontent.com/superagent-ai/grok-cli/main/install.sh)"
Bun not found
The install script bundles Bun, but if you want to use your own:
curl -fsSL https://bun.sh/install | bash
bun add -g grok-dev
API key issues
"Missing GROK_API_KEY" error
Set your API key using one of these methods:
# Environment variable
export GROK_API_KEY=your_key_here
# Or save to user settings
grok -k your_key_here
Get your API key from x.ai.
Terminal UI issues
UI doesn't render correctly
Try a different terminal emulator. Recommended:
- WezTerm (cross-platform)
- Alacritty (cross-platform)
- Ghostty (macOS/Linux)
- Kitty (macOS/Linux)
Screen flickering or artifacts
Ensure your terminal supports true color and Unicode. Update your terminal emulator to the latest version.
Telegram remote control
Bot doesn't respond
- Verify
TELEGRAM_BOT_TOKENis set correctly - Ensure the CLI process is still running (long polling lives in the process)
- Check that you've completed the
/pairflow and been approved
Voice messages not transcribing
- Verify
GROK_API_KEYis set (transcription uses the same key) - Check
~/.grok/user-settings.jsonhastelegram.audioInput.enabled: true
Sandbox mode
Sandbox only works on macOS 14+ with Apple Silicon
If you're on Intel Mac or Linux, sandbox mode is not available. Use standard mode without --sandbox.
Performance issues
Slow response times
- Check your network connection to x.ai API
- Try
grok-4.20-non-reasoningfor non-reasoning workloads - Reduce
--max-tool-roundsfor headless runs
High memory usage
- Long-running sessions accumulate context; start a fresh session periodically
- Use
/compactin TUI to compress conversation history
Getting help
- Check existing issues
- Open a new issue with:
- OS and terminal emulator version
- Grok CLI version (
grok --version) - Steps to reproduce
- Error messages or logs
Development
From a clone:
bun install
bun run build
bun run start
# or: node dist/index.js
Other useful commands:
bun run dev # run from source (Bun)
bun run typecheck
bun run lint
Trademarks
"Grok" is a registered trademark of xAI Corp. This project is not affiliated with, endorsed by, or sponsored by xAI Corp. All trademarks belong to their respective owners.
License
MIT
