Grok — Delegate coding to xAI Grok Build CLI (features, PRs)
Grok — Delegate coding to xAI Grok Build CLI (features, PRs)
Start with meaning, then move to detail.
This lesson explains Grok — Delegate coding to xAI Grok Build CLI (features, PRs) as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, When to use, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Grok — Delegate coding to xAI Grok Build CLI (features, PRs) without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Session & memory
- A session holds conversation context, while memory keeps selected facts that should persist.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Delegate coding to xAI Grok Build CLI (features, PRs)
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03When to use
Read this after the foundation, then connect it to the previous step.
- 04Prerequisites
Read this after the foundation, then connect it to the previous step.
- 05Two Orchestration Modes
Read this after the foundation, then connect it to the previous step.
- 06Mode 1: Headless (-p) — Non-Interactive (PREFERRED)
Read this after the foundation, then connect it to the previous step.
- 07Mode 2: Interactive PTY — Multi-Turn TUI Sessions
Read this after the foundation, then connect it to the previous step.
- 08Headless Deep Dive
Read this after the foundation, then connect it to the previous step.
- 09Common Flags
Read this after the foundation, then connect it to the previous step.
- 10Output Formats
Finish here to verify the result and special cases.
Copy only after you understand the effect.
terminal(command="grok --no-auto-update -p 'Add a dark mode toggle to settings'", workdir="/path/to/project", timeout=180)# Launch in a tmux session for capture-pane monitoring
terminal(command="tmux new-session -d -s grok-work -x 140 -y 40")
terminal(command="tmux send-keys -t grok-work 'cd /path/to/project && grok' Enter")
# Wait for startup, then send a task
terminal(command="sleep 5 && tmux send-keys -t grok-work 'Refactor the auth module to use JWT' Enter")
# Monitor progress
terminal(command="sleep 15 && tmux capture-pane -t grok-work -p -S -50")
# Exit when done
terminal(command="tmux send-keys -t grok-work '/quit' Enter && sleep 1 && tmux kill-session -t grok-work")# Structured result for parsing
terminal(command="grok --no-auto-update -p 'List all TODO comments in src/' --output-format json", workdir="/project", timeout=120)
# Auto-approve for autonomous building
terminal(command="grok --no-auto-update --always-approve -p 'Refactor the database layer and run the tests'", workdir="/project", timeout=300)Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.