Share memory between Claude Code and Cursor

Claude Code and Cursor each keep their own context, so a decision you give one is unknown to the other. Hivemind sits underneath both and gives them one memory.

Connect both

npx @get-hivemind/cli init

It signs you in, finds Claude Code and Cursor, and writes each one's configuration. Restart both afterwards.

Try it

In Claude Code:

Remember that we cap production deploys at three per month, on Tuesdays.

In Cursor, a minute later:

How often can we deploy?

Cursor answers from what Claude Code was told. The memory is the same one, so it works in the other direction too.

What each tool sees

Each tool asks for context and receives only the memories relevant to the question, packed to a token budget. Open the retrieval inspector in the dashboard (press Cmd+K and search "Retrieval") to see exactly what was sent and what was left out.

After Claude Code compacts

When a long conversation is compacted, the summary keeps the story and drops the specifics: the rule you gave at the start, the decision from an hour ago. Hivemind saved those as you went, so when the conversation is compacted or resumed it puts that session's memories back. Nothing to switch on: it comes with the hooks that init installs. Run npx @get-hivemind/cli hooks install to add it to an install made before this existed.

Keep projects apart

Memories are filed by the project you are in, so a decision about one codebase does not appear in another. See views.

If it does not work

Run npx @get-hivemind/cli doctor. It tests the connection and prints the command that fixes anything failing. More in troubleshooting.