remembra-ai/remembra

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:
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:
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
| 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 in Codex (Settings > Hooks, or /hooks in the CLI), and again when one changes |