Skip to main content
Grok Build is Capture tier. Memory Crystal registers the tool surface, captures turns automatically, installs skills, and writes a Managed Block to ~/.grok/AGENTS.md. Recall is deliberate, not automatic: the harness ignores hook stdout on passive events, so it cannot inject context. Call crystal_recall or crystal_what_do_i_know when you need past context. Do not expect memories to appear in the prompt on their own. Do not use Claude-compat ([compat.claude]) as a substitute for this install.
PowerShell configures MCP and skills. Shared capture hooks and the Managed Block are installed by the Bash installer (hooks.shells is bash-only).

​
Agent Instructions

For local data storage, add --backend local in Bash or -Backend local in PowerShell. See Local-First Setup.

​
What the Bash installer writes

  • MCP via grok mcp add when the CLI is present, otherwise [mcp_servers.memory-crystal] with url and headers in ~/.grok/config.toml
  • Capture hooks at ~/.grok/hooks/memory-crystal.json (SessionStart, UserPromptSubmit, Stop — no matcher on lifecycle events)
  • Skills under ~/.grok/skills/
  • Managed Block in ~/.grok/AGENTS.md only (no other instruction files)
GROK_HOME overrides the default directory for MCP, hooks, and skills. The managed instructions remain at ~/.grok/AGENTS.md.

​
Verify

Restart Grok or run grok inspect. After Bash installation, confirm the MCP server, hooks, skills, and managed instructions. After native PowerShell installation, verify MCP and skills; that installer does not write the hooks or managed instructions.

​
Uninstall

Removes the hook file, the MCP entry, the Managed Block, and Crystal skills. See Uninstall.