Use cases

Built for the way
work actually moves.

Context doesn't live in one head or one session. Here's where Relay fits — from a solo builder resuming yesterday's work to a fleet of agents running a pipeline with provenance.

One Code carries the whole package · single-use or multi-claim.
Scenarios

Six ways context travels.

Solo · across sessions
Resume your own work.
Your agent starts every session cold. Package where you left off and load it back tomorrow — same machine or not. No re-explaining yourself to your own tools.
Sessions + Streams
Teams · mid-task
Hand off without a briefing.
Pass the goals, decisions, and current state to the next teammate or agent. They receive it whole — not a summary, not a status update. That's a handoff: a transfer built for continuity.
Handoffs · single-use or multi-claim Codes
Operators · pipelines
Multi-agent, with provenance.
Chain agents into a workflow where each step carries context forward — and you can see who touched what, when. Provenance built into the pipe, not bolted on after.
Provenance + multi-claim Codes
Projects · always-on
A brief that stays current.
Instead of a doc that rots, keep a living Stream for the project. It gathers decisions and state as work happens, so anyone — or any agent — joining is instantly up to speed.
Streams
Teams · recurring
Standing context drops.
A named Stream like weekly-sync that the whole team subscribes to. Drop the latest once; everyone receives it. No re-sending, no chasing the right link.
Streams
Orgs · cross-boundary
Share across orgs, with consent.
Send context to a partner or another org and it lands through request → approve → receive. The right person gets it, with a record — and a durable connection skips the gate next time.
Connections · approvals + org policy
Builders & Agents

Context between sessions.

An agent has no memory of yesterday. Follow one Code — K7BX2Q — and the thread never breaks: package a session when you stop, receive it when you start, and the work resumes mid-thought instead of from a blank prompt.

Sessions
Package a whole working session — goals, decisions, current state — and resume it anywhere.
relay_session_*
Streams
Living context that stays current between runs. A Code is a moment; a Stream is context that keeps flowing.
relay_save · relay_search
Handoffs
A transfer built for continuity. Carry the working state forward into the next session, whole.
relay_session_package
Operators

Pipelines that carry meaning.

A pipeline is only as trustworthy as its trail. Code R4PNT9 moves through every agent in the chain carrying its own provenance — who sent, who received, every hop, every timestamp — so a multi-agent run is auditable end to end, not a black box.

Provenance
Who sent, who received, every hop, every timestamp. Received status tracked end to end.
chain of custody
Connections
Wire agents and orgs together through request, approve, receive — a durable, policy-aware pipe.
relay_request_*
Streams
A named, recurring relay each stage subscribes to. The next agent always gets the latest.
relay_series_*
Teams

Handoffs that land whole.

Re-explaining is where context leaks. Code TM6VK3 carries the goals, the decisions, and the current state to the next person — received whole, not summarized — so the handoff lands and nobody starts the day guessing.

Handoffs
Stop re-briefing. The next person receives the full working state, not a status update.
relay_session_package
Streams
Standing drops like weekly-sync — send once, the whole team receives.
relay_series_*
Connections
Share across people and orgs with consent and a record. Approve once, skip the gate next time.
relay_request_*
One Code

The same Code,
moving through hands.

K7BX2Q leaves a builder's session, feeds an operator's pipeline, and arrives in a teammate's inbox — the same package, whole at every hop. We move it. We don't read it.

Context in.
Context out.

Join the Loop and your first 12 months are on us. A direct line to the founding team included.

Join the Loop →
Registration is open — access by activation code as Early Access expands.