Grok Bot

Long-term memory for Grok Bot and Cursor, shared across your Bots and your other AI tools.

Each Grok Bot keeps its own conversation and learned context, so one Bot cannot see what another worked out, and a scheduled routine starts every run from zero. Hindsight gives each Bot its own memory bank plus one shared bank for the whole team, and lets Bots read the banks your other agents (Claude Code, ChatGPT, Hermes, OpenClaw) already write to.

Hindsight Cloud (recommended)

Sign up free. The plugin connects with OAuth, so there is no API key to copy and nothing to configure.

Install

1. In Grok Bot, select Connect apps below the message box to open the Marketplace. Search for Hindsight, open it and select Add.
2. Grok Bot asks you to connect Hindsight. Sign in on Hindsight's own page and choose the organization to authorize.
3. Ask any Bot to "set up Hindsight memory". The memory-setup skill checks the connection and creates the banks below. Name the Bot first: its name becomes its bank id, so a Bot still called "Grok Bot" is asked for a name before setup continues.

The same plugin works in Cursor: install it from the Cursor Marketplace.

Memory Banks

Bank	Holds	Written by
grok-bot::<bot-name>	What one Bot learns in its own work. A Bot named "Sales Researcher" uses grok-bot::sales-researcher.	That Bot
cursor::<project-name>	What a Cursor agent learns in one project, named after the open workspace folder. The plugin installs into Cursor whenever you add it in Grok Bot.	Cursor agents in that project
grok-bot::shared	What every Bot should know, handoffs between Bots, and the "About the user" profile.	Any Bot
Your other banks	Memory from your other AI tools.	Those tools only; Bots read them

The plugin connects to the root MCP server, https://api.hindsight.vectorize.io/mcp, which reaches every bank in the organization you authorize.

How It Works

In Grok Bot, a plugin's hooks never run: the Bot installs a plugin's MCP server and skills, and nothing else. So memory here is driven by skills, and each skill's description tells the Bot when to use it.

Skill	Use
memory-setup	Connect, verify with list_banks, create the banks and the profile
memory-context	Recall relevant memory before starting any task
memory-retain	Save outcomes, decisions and preferences when a task finishes
memory-reflect	Answer questions about history and past decisions with reflect
routine-memory	Writes recall and retain steps into each routine it creates; reads the last run before a routine starts and records this run when it ends
bot-handoff	Keep a durable record of work passed between Bots, which Bots that were never messaged can also pick up

The skills never call delete_bank, clear_memories, invalidate_memory, delete_document or delete_mental_model. If something should be deleted, the Bot tells you and you do it from the Hindsight dashboard.

Self-Hosted Hindsight

Grok Bot needs a public HTTPS MCP endpoint with OAuth 2.1 discovery and dynamic client registration. Put the cloudflare-oauth-proxy in front of your instance, check it with the Meta Muse integration's preflight tool (Grok Bot connects the same way), then change the url in the plugin's mcp.json.

Verifying Setup

Ask a Bot:

• "Set up Hindsight memory." → memory-setup lists your banks and creates the Bot's own
• "What do you remember about our vendor shortlist?" → memory-context recalls before answering
• "How do we usually handle renewals?" → memory-reflect

Then check the Hindsight dashboard: the Bot's bank and grok-bot::shared should appear, with memories tagged source:grok-bot.