Remembra Relay
One agent stops. The next one already knows.
When an agent's session ends, Remembra Relay saves a handoff built from what git says happened.
The next agent, on another machine, from another vendor, or next week, starts from it.
Website • Relay guide • Docs • Changelog • Discord
Install
pipx install --force 'remembra[mcp]>=0.16'
remembra-install --all
remembra-relay connect
Get a free key at app.remembra.dev, or host the server yourself.
remembra-install asks for the key at a hidden prompt (or reads REMEMBRA_API_KEY) and shows its changes before it writes.
connect is a dry run that shows exactly what it would change; add --apply to write the hooks. remembra-relay ships in remembra 0.16.0.
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 starts with:
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 collected by remembra-relay from git and the session transcript) (the agent's summary contradicts these recorded facts)
The done, not done and failing sections come from git and the session's test runs, never from an LLM. The agent's own summary is optional; it is checked against those facts and shown as unverified, or, as here, contradicted.
How it works
- Close. When a session ends,
remembra-relay closereads the branch, commits, changed and uncommitted files and unpushed commits from git, and for Claude Code the test runs and open items in the local transcript. The transcript never leaves your machine; secrets are redacted before anything does. - Brief. When the next session starts, in any tool,
remembra-relay brief(or thesession_briefMCP tool) gives the agent who worked last, what is done, what is failing and the next step, in about 1,500 tokens. Everything another agent recorded is wrapped as untrusted data. - 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
| Agent | Session hooks | How it reads and writes handoffs today |
|---|---|---|
| Claude Code | verified | Hooks: brief at start, close at end, with test results from the transcript |
| Codex | verified (codex-cli 0.155.0-alpha.16.4, a prerelease) | Hooks: brief at start, close at end, with commands and test runs from the rollout; trust them once with /hooks in Codex |
| Cursor, Gemini CLI, Qwen Code, Kimi | unverified | MCP tools (session_brief, close_session) |
| Any other MCP agent | none | MCP tools |
Claude Code's and Codex's session hooks are verified (Codex with codex-cli 0.155.0-alpha.16.4, a prerelease; no stable Codex release has been run yet). The hooks for Cursor, Gemini CLI, Qwen Code and Kimi are unverified: they follow each tool's docs but have not been run against it yet. connect leaves them out unless you add --include-unverified. Until they are tested, those agents read the brief and write their handoff through Remembra's MCP tools, as does any MCP agent.
How it compares
| Remembra Relay | Vendor memory (Claude Code, Codex, Copilot, Windsurf) | Local handoff tools | Memory APIs (Mem0, Zep, Letta) | |
|---|---|---|---|---|
| Works across machines | Yes, by git remote | Mostly no | No | Yes |
| Works across vendors | Yes | No, one vendor each | Yes | Through their API |
| Handoff facts from git | Yes, with the summary checked | No | Transcript or diff | No |
| Durable trail of sessions | Yes | No | No | No |
| Enforced coordination between agents | Crew mode, in build | Claude-only agent teams | No | No |
Details, with a source and date for every claim: Remembra and other handoff tools and the competitive landscape. 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."
In v0.16.0 the memory layer also keeps the exact source text of every derived fact, points each fact back to it, and flags a fact that does not match its source as unverified.
Self-host the server (2 minutes)
One Command Install
curl -sSL https://raw.githubusercontent.com/remembra-ai/remembra/main/quickstart.sh | bash
That's it. Remembra + Qdrant + Ollama start locally. No API keys needed.
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 Acme?", "user_id": "demo"}'
Connect ALL Your AI Agents (NEW in v0.10.0)
One command configures everything:
pip install remembra
remembra-install --all --url http://localhost:8787
This auto-detects and configures: Claude Desktop, Claude Code, Codex CLI, Cursor, Gemini CLI. (Windsurf is unverified: remembra-install --agent windsurf writes it, --all does not.)
Verify setup:
remembra-doctor all
Manual MCP Config (if needed)
Claude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"remembra": {
"command": "remembra-mcp",
"env": {
"REMEMBRA_URL": "http://localhost:8787",
"REMEMBRA_USER_ID": "default"
}
}
}
}
Claude Code:
claude mcp add remembra -e REMEMBRA_URL=http://localhost:8787 -- remembra-mcp
Cursor — add to .cursor/mcp.json:
{
"mcpServers": {
"remembra": {
"command": "remembra-mcp",
"env": {
"REMEMBRA_URL": "http://localhost:8787"
}
}
}
}
Now ask Claude: "Remember that Alice is CEO of Acme Corp" — then later: "Who runs Acme?"
Python SDK
pip install remembra
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."
TypeScript SDK
npm install remembra
import { Remembra } from 'remembra';
const memory = new Remembra({ url: 'http://localhost:8787' });
await memory.store('User prefers dark mode');
const result = await memory.recall('preferences');
Memory features
🧠 Smart Extraction — LLM-powered fact extraction from raw text
👥 Entity Resolution — "Adam", "Mr. Smith", "my husband" → same person
⏱️ Temporal Memory — TTL, decay curves, historical queries
🔍 Hybrid Search — Semantic + keyword for accurate recall
🔒 Security — PII detection, anomaly monitoring, audit logs
📊 Dashboard — Visual memory browser, entity graphs, analytics
📊 Benchmarks
One small LoCoMo run, not a benchmark result: in March 2026 we ran 1 of the 10 LoCoMo conversations, 199 questions, judged by gpt-4o-mini. 76% overall. The 47 adversarial questions, whose answer is not in the conversation, all scored 0, because Remembra did not detect them; the other 152 questions scored 100%. The numbers are in benchmarks/results_20260307_040346_summary.json. A run over all 10 conversations has not been done yet.
Run it yourself: python benchmarks/locomo_runner.py --data /tmp/locomo/data/locomo10.json
📖 Documentation
| Resource | Description |
|---|---|
| Quick Start | Get running in minutes |
| Python SDK | Full Python reference |
| TypeScript SDK | JavaScript/TypeScript guide |
| Remembra Relay | Handoffs, briefs and the trail across agents |
| MCP Server | Tool reference and setup guides for the 21 tools |
| REST API | API reference |
| Self-Hosting | Docker deployment guide |
🛠️ MCP Server
Give any AI coding tool persistent memory with one command. Works with Claude Code, Cursor, VS Code + Copilot, Windsurf, JetBrains, Zed, OpenAI Codex, and any MCP-compatible client.
pip install remembra[mcp]
claude mcp add remembra -e REMEMBRA_URL=http://localhost:8787 -- remembra-mcp
Available tools (21):
| Group | Tools |
|---|---|
| Remembra Relay | session_brief, close_session, resolve_project, store_status, list_status |
| Inbox between agents | send_to_inbox, get_inbox, ack_inbox |
| Memory | store_memory, recall_memories, update_memory, forget_memories, list_memories, ingest_conversation |
| Entities and time | search_entities, timeline, relationships_at |
| Sharing | share_memory, list_spaces, create_space |
| Connection | health_check |
🏗️ Architecture
┌─────────────────────────────────────────────────────────────┐
│ Your Application │
├──────────┬──────────────┬───────────────────────────────────┤
│ Python │ TypeScript │ MCP Server (Claude/Cursor) │
│ SDK │ SDK │ remembra-mcp │
├──────────┴──────────────┴───────────────────────────────────┤
│ Remembra REST API │
├──────────────┬──────────────┬───────────────┬───────────────┤
│ Extraction │ Entities │ Retrieval │ Security │
│ (LLM) │ (Graph) │ (Hybrid) │ (PII/Audit) │
├──────────────┴──────────────┴───────────────┴───────────────┤
│ Storage Layer │
│ Qdrant (vectors) + SQLite (metadata/graph) │
└─────────────────────────────────────────────────────────────┘
🤝 Contributing
We welcome contributions! See CONTRIBUTING.md for guidelines.
# Clone
git clone https://github.com/remembra-ai/remembra
cd remembra
# Install dev dependencies
pip install -e ".[dev]"
# Run tests
pytest
# Start dev server
remembra-server --reload
📄 License
MIT License — Use it however you want.
⭐ Star History
If Remembra helps you, please star the repo! It helps others discover the project.
Built with ❤️ by DolphyTech
remembra.dev • docs • twitter • discord
Metadata
Release files for remembra 0.16.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| remembra-0.16.0.tar.gz | 1.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| remembra-0.16.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.1 MB
Release files / remembra-0.16.0.tar.gz
| Download URL | remembra-0.16.0.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
867339e085520a81ea3570ff671a11f6198c6cfdcdf0cc569310f24a1b1f6327
|
|
BLAKE2b-256 checksum How to use checksums |
af6dc7f5455f04076af86f824eb6c1f3a0c7e9b77ff48fc1f7037629f8097653
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency logRelease files / remembra-0.16.0-py3-none-any.whl
| Download URL | remembra-0.16.0-py3-none-any.whl |
|---|---|
| Size | 842.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0217a6f9c58a739c272061448bbf079e97d514f9eb0728c06e15edd837ce5af1
|
|
BLAKE2b-256 checksum How to use checksums |
87a183dc8239400fdf344d7e1c0c6b758651b05b0ac9347dfdca05f738bf0db8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency log