Open-source tool makes Grok Build's saved sessions searchable
After xAI Grok Build this week, it became clear the tool saves every session locally under ~/.grok/sessions/, storing an event stream in updates.jsonl plus a generated title in summary.json. That data — every bug fixed, every command that worked — was just sitting there unused, since nothing read it back. The open-source memory project deja-vu added Grok Build support in v0.10.0.
It works retroactively, indexing the session files already on disk with no separate capture step. It shares one index across Claude Code, Codex, opencode, Cursor, Gemini CLI, aider, and Antigravity, so a fix found in a different agent becomes searchable from inside Grok Build too. Running `deja install grok` adds an MCP tool called recall to Grok's config file (~/.grok/config.toml), letting Grok itself search past sessions.
`deja resume` reopens a found session and continues it via `grok --resume`. Indexing runs entirely locally as a flat binary index with no embeddings and no cloud calls, and secrets are redacted automatically before indexing. One noted limitation: Grok's hooks don't currently support a certain kind of automatic injection.
Key points
- Grok Build stores sessions locally under ~/.grok/sessions/ as updates.jsonl and summary.json
- deja-vu v0.10.0 indexes those existing files retroactively, no capture step needed
- It shares one across Claude Code, Codex, Cursor, Gemini CLI, and more
- `deja install grok` adds an MCP recall tool so Grok itself can search past sessions
- Indexing is fully local with no embeddings or cloud calls, and secrets are redacted first