Early access · free while we learn what breaks

Tell one AI tool something.
The rest already know.

You explain your project to Claude Code. Then again to Cursor. Then again to ChatGPT. Hivemind keeps that context in one place and puts the relevant part of it in front of whichever tool you are using next.

Start free Read the quickstart No card. One command to set up.
Claude Code · Tuesday
We cap production deploys at three a month, on Tuesdays.
Noted.
no copying
Cursor · Friday
Can we ship this today?
Not today — deploys are Tuesdays, capped at three a month.

The difference

Most memory tools decide what to remember.
This one also decides what to send.

Remembering is the easy half. Choosing what reaches the model — and what to leave out — is where a memory layer either saves you tokens or quietly costs you them.

It fits a budget you set

Ask for 4,000 tokens and you get the most useful set that fits — not the top ten, whatever they happen to cost.

It returns nothing when nothing fits

Ask something your memory has no bearing on and you get an empty payload. A tool that always finds something buries the answer.

It orders context to be read

Models attend to the start and end of a long prompt far more than the middle. Memories are placed accordingly.

It hands over work, not just facts

A handoff carries decisions, priorities and warnings — so the next agent picks up your reasoning, not just your output.

It knows what you are doing now

Threads open on their own and bias retrieval toward current work — without hiding what the folder already knows.

It shows its reasoning

See exactly what was considered, what was sent, what was dropped and what it saved. No other memory tool shows you this.

Measured

Numbers we can show our working for

Measured against the running deployment on 12 September 2026, not against a research prototype. The full method, the weak categories and the error bars are public.

74.8%of the evidence needed to answer a question is retrieved — LoCoMo, 397 questions, against the live system
9.9memories returned per query. Recall is easy to buy by sending more; the budget is the hard part
13AI clients configured by a single command
0failed searches across the benchmark run

Everywhere you already work

One command sets all of it up

It opens a browser, signs you in, finds what is installed, and writes each tool's configuration in its own format. Nothing to copy, nothing to paste.

$ npx hivemind-cli init

   Claude Code      configured
   Cursor           configured
   VS Code          configured
   Codex CLI        configured
  
  8 clients configured. Restart them to pick up the change.

$ # then it reads what you already wrote for your agents

   57 memories stored across 4 folders
Claude CodeClaude Desktop CursorVS Code WindsurfZed ClineRoo Code Codex CLIGemini CLI AmpOpenCodeWitsy ChatGPTClaude GeminiGrok PerplexityT3

Browser chats work through an extension that captures and injects — on the sites above, and on any other chat site you enable.

It does not read your chat history. The import takes the context files you wrote yourself — AGENTS.md, CLAUDE.md, .cursorrules — because those were already written to be read by an agent. Nothing is sent to a model to be summarised, everything found is shown to you first, and --dry-run sends nothing at all.

For builders

Give your own agents the same memory

A TypeScript SDK and a REST API. The payload comes back ready for a prompt.

import { Hivemind } from "@hivemind-ai/sdk";

const hm = new Hivemind({ apiKey: process.env.HIVEMIND_API_KEY });

await hm.remember({ content: "We cap deploys at 3 a month" });

const { payload, tokensSaved } = await hm.recall({
  q: "how often can we deploy?",
  budget: 2000,
});

Every memory tool remembers facts about you. This one carries work between agents — the decisions, the priorities, and the things not to try again.

What we are actually building

Stop explaining yourself twice

Free while we are in early access. Set up in about five minutes, and tell us what breaks.