Remembra Relay

Remembra Relay

One agent stops. The next one already knows.

When a connected agent's session ends, Remembra Relay saves a handoff (a session that did nothing leaves none).

With the session hooks it is built from git and, for Claude Code and Codex, the session transcript.

An agent that closes through MCP reports its own facts, marked unverified.

The next agent, on another machine, from another vendor, or next week, starts from it.

Website • Relay guide • Docs • Changelog • Discord

Install

First get a free key at app.remembra.dev, then run:

pipx install --force 'remembra[mcp]>=0.16'

remembra-install --all remembra-relay connect --apply

remembra-install asks for the key at a hidden prompt (or reads REMEMBRA_API_KEY) and shows its changes before it writes. connect --apply writes the hooks and keeps a backup of each file; run remembra-relay connect alone first to see every change without writing. Codex runs the hooks only after you trust them: Settings > Hooks > Trust in the Codex app, or /hooks in the Codex CLI. When a hook's command changes, Codex skips it until you trust it again. Hosting the server yourself? Add --url to remembra-install. remembra-relay ships in remembra 0.16.0.

Handoffs not arriving? remembra-relay doctor says where the baton dropped, from this machine's files and your trail, with one fix per problem; it only reads. Inside your agent the local MCP server has the same checks as read-only tools: remembra_doctor, remembra_setup (the install steps for this machine) and remembra_help. See Doctor.

What the next agent sees

Claude Code finished a session and wrote in its summary that the work was done and pushed. Git disagreed. The next agent's brief includes this line:

Last session: claude-code (key-verified), 12m ago, on feat/pdf-export@a41f2c9: done: a41f2c9 Add PDF export for invoices; 77c01aa Embed fonts in exported PDFs; tests passing: pytest tests/test_pdf.py (12 passed); changed 3 file(s): invoices/pdf.py, invoices/fonts.py, tests/test_pdf.py / NOT done: 2 commit(s) not pushed to origin/feat/pdf-export / failing: none / next (derived from the recorded facts): push 2 commit(s) to origin/feat/pdf-export (facts reported as collected by remembra-relay from git and the session transcript (not checked)) (the agent's summary contradicts these recorded facts)

With the session hooks, remembra-relay builds the done, not done and failing sections from git and, for Claude Code and Codex, the session's test runs, never from an LLM. The server does not check where the facts came from; the brief says they were reported by remembra-relay. The agent's own summary is optional; it is checked against those facts and shown as unverified, or, as here, contradicted. A handoff written through the close_session MCP tool holds the facts the agent declares, labeled "declared by the agent (not checked)".

How it works

1. Close. When a session ends, remembra-relay close reads the branch, commits, changed and uncommitted files and unpushed commits from git, and, for Claude Code and Codex, the commands, test runs and open items in the local transcript (Codex's is its rollout file). The transcript itself stays on your machine. Secrets that match Remembra's patterns are redacted from what is sent.
2. Brief. When the next session starts, in the same tool or another, remembra-relay brief (run by the verified session hooks) or the session_brief MCP tool (any MCP agent can call it) gives the agent who worked last, what is done, what is failing and the next step. The text brief is capped at about 1,500 tokens (6,000 characters). session_brief returns only that text with compact=true; by default it also returns the full brief as JSON, which is larger. Everything another agent recorded is wrapped as untrusted data.
3. Trail. Every handoff stays in order: remembra-relay trail, or the Trail page in the dashboard. A git log for your agents.

The same repository on a laptop, a server or in a worktree is one project, because it is identified by its git remote. Give each agent its own scoped key and its handoffs show as key-verified.

Agents

Claude Code's and Codex's session hooks are verified (Codex with codex-cli 0.155.0-alpha.16.4, a prerelease, and the same tests also pass on the stable 0.157.1). The Gemini CLI, Qwen Code and Kimi Code hooks are verified too: each was run against the real tool at the version in the table, with a local stand-in for the model, and put the brief in the model's request and posted the handoff; other versions have not been run. The Cursor hooks are unverified: Cursor's own hook runner ran them, but no logged-in Cursor session has yet. connect leaves them out unless you add --include-unverified. Until they are tested, Cursor reads the brief and writes its handoff through Remembra's MCP tools, as does any MCP agent.

Crew mode

Several agents in one repository at once, without one undoing another's work. Name the areas of the repo in .remembra/zones.yml and commit it on the default branch:

version: 1

zones: api: include: ["src/api/"] web: include: ["src/web/"]

Then, at a terminal (it shows every change and asks before writing):

remembra-crew connect --apply                 # Claude Code

remembra-crew connect --agent codex --include-unverified --apply remembra-crew verify --agent codex # one round trip on your machine; Codex then enforces

The first agent to write in a zone holds it. Another agent's write there is stopped before it happens and the agent is told who holds it; it can ask for a handover with crew_say, or you hand it over from the dashboard.

Git hooks (connect --git-hooks) also stop a commit or push that touches a held zone, for every agent. The honest limit: these local layers stop cooperating agents' mistakes, not a deliberately hostile agent on the same machine. Crew mode needs a server that runs it (REMEMBRA_CREW_MODE; on for Remembra Cloud). The guide is Crew mode.

How it compares

Details, with a source and date, for claude-mem, agentmemory, the local handoff tools and Claude Code's own features: Remembra and other handoff tools. claude-mem and agentmemory are larger projects that also carry memory between sessions; the comparison says where each is the better pick.

Pricing

Handoffs, briefs, the inbox, the trail and search are free on every plan. Remembra Cloud: Free, Solo $12/mo, Pro $29/mo, Team $15/seat/mo (pricing). Self-hosting is free under the MIT license.

The memory API underneath

Remembra Relay runs on Remembra's memory layer, which you can also use directly: store facts, recall them by meaning, and let it pull out the people, projects and relationships in them.

from remembra import Memory

memory = Memory(user_id="user_123") memory.store("Had a meeting with Sarah from Acme Corp. She prefers email over Slack.") result = memory.recall("How should I contact Sarah?") print(result.context)

"Sarah from Acme Corp prefers email over Slack."

Since v0.16.0 the memory layer also keeps the exact text that facts were derived from and points each fact back to it. By default a fact that does not match its source is not stored: the store response lists it under dropped_facts. With REMEMBRA_GROUNDING_ACTION=flag such a fact is stored and marked unverified instead.

Self-host the server

One Command Install

curl -sSL https://raw.githubusercontent.com/remembra-ai/remembra/main/quickstart.sh | bash

This starts Remembra, Qdrant and Ollama locally, with auth off and local embeddings, so the server needs no API key. The first start downloads the images and the embedding model, so how long it takes depends on your connection.

Or with Docker Compose directly:

git clone https://github.com/remembra-ai/remembra && cd remembra

docker compose -f docker-compose.quickstart.yml up -d

Try it:

# Store a memory

curl -X POST http://localhost:8787/api/v1/memories \ -H "Content-Type: application/json" \ -d '{"content": "Alice is CEO of Acme Corp", "user_id": "demo"}'

Recall it

curl -X POST http://localhost:8787/api/v1/memories/recall \ -H "Content-Type: application/json" \ -d '{"query": "Who runs Ac