The Code is the atom: a unit of context you send and receive. Everything else is built on it. Living context that stays current, whole sessions you can resume, handoffs that carry continuity to whoever comes next, recurring streams, full provenance, and a connection graph. All of it native inside your agent.
Six capabilities and one toolset, each a different shape of the same primitive. A Code is a moment; the platform makes it a heartbeat, a session, a handoff, a stream, a record, a relationship.
A Code is a moment; a Pulse is a heartbeat. Pulses are focus areas that stay current. They accumulate state, items, and contributions over time, so a project's context is always live, never a stale paste from last week.
Package an entire working session, goals, decisions, and state, then resume it later, on another machine, or hand it to the next agent. The "show up ready every time" promise, made literal. Continuity, not re-briefing.
A named, recurring relay, like weekly-sync. Drop context into the series; everyone subscribed receives the latest. One Code that keeps giving, instead of a fresh paste every time.
A Handoff is a special transfer: a continuity package. The full working state of a session, wrapped to carry forward. Hand it to a teammate, the next agent, or future-you, and whoever receives it resumes mid-stride instead of starting cold. This is the heart of Relay: continuity that survives the gap between sessions, people, and tools.
Sharing across people and orgs isn't a free-for-all. Cross-user claims go through request, approve, receive, so context lands with the right person, with consent. Durable connections skip the gate next time.
Every relay carries a timeline: who sent it, who received it, every forward, every timestamp. Org visibility controls, claim approvals for cross-user shares, encryption, and retention. Context you can audit and govern, end to end.
Relay isn't a website you visit, it's tooling your agent already has. Around 24 MCP tools expose every capability above directly inside Claude or any MCP client. No app-switching, no copy-paste. Context operations where the work actually happens.
You never type a tool name. Say what you want in plain English; your agent picks the right Relay tool and calls it. The toolset is for the agent, not for you.
{
"mcpServers": {
"relay": {
"command": "npx",
"args": ["-y", "@relayctx/mcp-server"],
"env": {
"RELAY_API_KEY": "your-key-here"
}
}
}
}
One primitive, a whole platform of tooling, native inside your agent. Join the Loop and get a direct line to the founding team.
Join the Loop →