Grok Bot

MemIndex reads Grok Bot's conversation files to record work. This connection uses those files rather than hooks inside the agent.

Install Grok Bot first. Then run:

npx memindex@latest install --ide grok-bot --runtime worker

Complete the shared setup in Install. Run installation on the machine that holds Grok Bot's agent data.

Keep the local MemIndex worker running so it can watch the files. If it was already running during setup, restart it to load the new watch:

npx memindex restart

The installer looks for Grok Bot's data folder and sets up a watcher for each agent it finds. If your data lives elsewhere, set GROK_BOT_AGENT_DATA to that folder before installation.

The watcher reads prompts, replies, tool calls, and results from new conversation content. It starts at the end of the watched files. This setup does not promise to import all earlier conversations.

Grok Bot can also use a local MemIndex search connection. For a client that accepts a command and arguments, the bundled connection uses:

Command: npx
Arguments: -y memindex mcp

Do a small task in Grok Bot, then check the MemIndex viewer for new notes. Ask the bot to find a decision from that task once its memory search connection is available.

The worker can write a compact timeline into each agent's memory log. That timeline gives the bot note IDs it can use to retrieve more detail. The installer does not need Cursor to record Grok Bot work.

If no new notes appear, check that the selected folder contains Grok Bot's agents and agent-transcripts folders. MEMINDEX_TRANSCRIPTS_ENABLED=false disables recording from those files, even when search works. See Troubleshooting for the local service and note-writing checks.