Grok Build Conversation History: Find and Resume Sessions

Updated July 28, 2026

Grok Build persists sessions under its data root so you can continue work later. The CLI exposes --continue, --resume, grok sessions, and grok export. CodeAgentSwarm adds a cross-agent searchable history UI on top. Grok Build is xAI's coding CLI (grok), not the Grok chatbot. Resume was verified against grok --help (-c/--continue, -r/--resume).

Resume from the CLI

bash

# Continue most recent session for this directory
grok --continue

# Resume by id or title
grok --resume
grok --resume "auth refactor"

# Optional: fork instead of reusing the same session id
grok --resume SESSION --fork-session

grok sessions list and grok sessions search help you find older work. grok export writes a Markdown transcript when you need a shareable artifact.

Where history lives

Session data lives under ~/.grok/ (or GROK_HOME). Do not casually delete that tree if you care about resume. Back it up like any other local agent state.

CodeAgentSwarm history

CAS indexes conversations across Claude Code, Codex, OpenCode, Kimi Code, Grok Build and more so you can search from one modal and reopen a session into a terminal. That is the multi-agent layer the raw CLI does not provide alone.

FAQ

Run grok --continue in the same project directory.

Use grok sessions list or grok sessions search, then grok --resume with the id or title.

CAS provides searchable history across agents, including Grok Build sessions it has indexed from your machine.

Resume Grok Build in the CLI, or browse every agent's chats from CodeAgentSwarm's conversation history.

Download it freemacOS & Windows

View Claude Code Changes in Real Time: Live Diff, Git Diff & AI Tracking

If you use Claude Code to make changes to your code, there's something that has probably happened to you more than once.

Read guide

View all guides