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.

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 + Pulses
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. Pick up exactly where you stopped.
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 Pulse for the project. It accumulates decisions and state as work happens, so anyone — or any agent — joining is instantly up to speed.
Pulses
Teams · recurring
Standing context drops.
A named Series like weekly-sync that the whole team subscribes to. Drop the latest once; everyone receives it. No re-sending, no chasing the right link.
Series
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

Context in.
Context out.

See the platform tooling, or join the Loop and get a direct line to the founding team.

Explore the platform →
Registration is open — access by activation code as Early Access expands.