Traces CLI v0.5.11 adds support for Grok Build, the open-source coding CLI from xAI. You can now capture and share the Grok Build sessions directly on Traces.
Grok Build stores every session under ~/.grok/sessions/, organized by working directory. Traces reads that on-disk data directly.
Each session directory holds a summary.json (title, git metadata, model) and an updates.jsonl event log; Traces treats a directory as a valid session only when both are present. TO list sessions quickly, Traces reads Grok's own session_search.sqlite search index, and falls back to scanning the filesystem when the index is incomplete.
Groke's updates.jsonl is a stream of updates keyed by sessionUpdate, and Traces normalizes them into a common trace shape:
user_message_chunk), assistant text (agent_message_chunk), assistant reasoning (agent_thought_chunk), tools calls (tool_call), and tool results (tool_call_update) each map to their own strace event.run_terminal_command, read_file, grep) from skills, prefixing the latter with skill: and renders file edits as a before/after diff.success only on a completed status; error, failed, and cancelled terminal states surface as errors.grok-code-fast-1) from the session summary and per-line metadata.Because Grok stamps a stable per-line _meta.eventId on every update, Traces keys events by Grok's own identity under the v2 id scheme, which enables re-syncing a session.
traces share --agent grok to publish a session; Traces resolves the right one from your working directory, or you can pick one by ID. Subagent sessions (from best-of-n, implement, review, etc.) are automatically discoverable and can be shared individually via --list.gorok --resume <id>..grok/hooks/traces.json, and the session summary carries the git branch and commit so traces link back to your code.traces setup to install the Grok hook and connect sessions to your commits.traces share to publish a session and get a link.