Workflows

Relay in your build process.

Per-tool guides that show exactly how Relay fits — setup, daily use, and the patterns that make context actually portable.

← Start with the intro guide New to Relay? Start there first.

What these guides cover

1

Tool setup

MCP config, API keys, and confirming Relay is connected — takes under 5 minutes per tool.

2

Daily patterns

The specific commands and habits that make context portable within your normal workflow.

3

Real examples

Actual before/after: what a session looks like without Relay vs. with a Code in play.

4

Team patterns

When context needs to cross people or agents — how Codes flow and what the receiving side does.

Choose your tool

The most direct path — Relay connects via MCP and runs alongside your sessions. Build a Pulse for each project, carry context between conversations, package handoffs in one command.

Claude Desktop MCP config relay_pulse_create relay_session_package

Read the guide →

For developers who live in the editor. Add Relay to Cursor's MCP layer, log what matters during a coding session, and hand off a working context — not a wall of notes — when you switch branches or collaborators.

Cursor MCP config relay_session_log relay_transfer_create

Teams & Handoffs

When context has to cross people. How to package what you're working on, send a Code, and onboard a teammate into the actual state of your work — not a Slack summary they have to decode.

Any MCP client relay_transfer_create relay_transfer_receive Codes

Agent Pipelines

Building with multiple agents across runtimes. Route context between them via Codes, maintain a custody chain, and stay root authority — every agent action is traceable back to a human decision.

Relay API Multi-agent relay_transfer_forward Provenance

Don't have Relay yet?

These guides assume you have an account. Request access first — it's free during the Loop.