Grok Build

MemIndex records work from Grok Build, xAI's grok command-line agent. It brings recent project notes into a new session. You can also ask Grok to search your memory.

Install Grok Build and sign in first. Then run:

npx memindex@latest install --ide grok

Choose how MemIndex should write notes when the installer asks. See Install for the shared requirements and choices.

The installer adds MemIndex hooks to ~/.grok/hooks/memindex.json and adds the memory search connection, mcp-search, to ~/.grok/config.toml. It keeps your other hooks, connections and settings. If you use GROK_HOME, keep it set to the same folder whenever you install, run Grok, check status or uninstall.

Start a new Grok session after installation. Use /hooks-list to check that the MemIndex hooks loaded and /mcps to check the search connection. Recent project notes arrive when Grok connects to mcp-search at startup, so keep that connection turned on.

MemIndex records prompts, tool calls and the results Grok reports. Grok sometimes reports only whether a tool worked, not its full output. A session summary needs Grok's last reply, and Grok does not always send it, so some sessions have notes but no summary.

If you also use Claude Code, you can install MemIndex for both. Each agent's work is recorded once, and both share one memory.

Ask Grok something specific, such as "What did we decide about the sign-in flow?" Check the MemIndex viewer after a small task to confirm that new notes appear.

To inspect or remove the connection:

npx memindex grok status
npx memindex grok uninstall

If search is missing, run grok mcp doctor mcp-search and look for a project .grok/config.toml that defines a different mcp-search; Grok prefers the project's version. If notes do not appear, use Troubleshooting.