THE MISSION CONTINUES

Keep the work.
Switch the agent.

Hit a limit. Lose the thread. Want a second opinion.
Whatever the reason, starting over shouldn’t be part of it.

Relayvora briefs your next coding agent on exactly where you left off. Real changes. Verified checks. No twenty-minute recap.

Get Relayvora See a handoff

npm install -g relayvora

MIT licensed · Local-first · No telemetry

CONTINUITY PROTOCOLRV / 001

Claude CodeSESSION LIMIT REACHED

relayvora

✓ CONTEXT SECURED

CodexREADY TO CONTINUE

OpenCode ↗

SAME MISSION. FRESH CONTEXT.

YOUR TOOLS. CONNECTED.

Claude Code

Codex

OpenCode

Windows / macOS / Linux

01 / THE HANDOFF

New agent.
Already up to speed.

The next agent needs the brief, not your entire history.
Here’s what one relay looks like.

CHOOSE YOUR NEXT AGENT

Switch agents above, then run the demo.
This is an illustration. Nothing runs on your machine.

~/your-projectINTERACTIVE DEMO

# The agent stopped. The work doesn’t.

❯ relayvora handoff --from claude --to codex --verify auto --confirm

01Read the sessionGoal, latest requests, last agent report✓

02Capture the evidenceGit changes, commits, and real check results✓

03Build a compact handoffFacts labelled. Context budget respected.✓

Codex is ready. Same mission, fresh context.

02 / TRUST THE BRIEF

Less “I think it worked.”
More “here’s the evidence.”

A summary can sound confident and still be wrong.
Relayvora keeps facts and claims separate.

HANDOFF.md4,000 TOKEN DEFAULT BUDGET

# Continue: fix leap-year handling

user Keep the public API unchanged.

observed src/calendar.ts has uncommitted changes.

observed npm test exited with code 1.

agent-reported The basic date parser is fixed.

inferred Century-year handling may be the blocker.

## Next step
Handle years divisible by 400, then rerun tests.

ILLUSTRATIVE HANDOFF / EVERY FACT HAS A SOURCE

The repository tells the truth.

Capture uncommitted diffs, new files, and session commits. Run the project’s own checks and carry the actual exit codes forward.

Every claim shows its source.

Observed, user-provided, agent-reported, or inferred. Your next agent knows what’s verified and what still needs a look.

A briefing. With a budget.

Goal, blockers, checks, and changed files come first. Supporting detail fits around them. The rest becomes a pointer to fetch when needed.

03 / BEYOND ONE TERMINAL

Work moves.
Your context should, too.

Catch the limit before it catches you.

Hooks save checkpoints automatically. Relay radar and live alerts help you spot usage limits, compaction, and large sessions that have gone cold.

relayvora hooks install

Laptop to desktop.
You to your teammate.

Export a handoff or share it through the Git repository you already use. Bring uncommitted changes along when you need them. No extra account.

relayvora sync

Inside the tools
you’re already using.

Let MCP-capable agents fetch handoffs, save checkpoints, and check the inbox. Works with Cursor, Copilot, Windsurf, and other MCP clients.

relayvora mcp

04 / NO MAGIC NUMBERS

Smaller context.
Honest trade-offs.

Relay when you hit a limit, need another agent, or have a large, cold session. Don’t relay a small, warm session just to save money.

Read the benchmark

LARGE-SESSION BENCHMARKDIRECTIONAL, NOT DEFINITIVE

−60%

Input tokens

Compared with continuing the session

−71%

Context per call

164k → 47k tokens

And the cost?About even. $0.306 → $0.308

Claude Code / Opus, 1–2 runs per arm. Small-session relay cost was 73% higher. These are the repository’s published measurements, not a savings promise.

READY WHEN YOU ARE

Your next session
starts here.

No signup. No dashboard. Just your terminal.

Node.js 22.13+ & Git 2.31+
Windows, macOS, and Linux · Alpha software

Install Relayvora

npm install -g relayvora

Check your setup

relayvora doctor

Pass the baton

relayvora handoff --from claude --to codex --verify auto --confirm

Full quick-start guide

BEFORE YOU GO

A few good questions.

Does my code leave my machine?

Checkpoints stay local. Relayvora has no telemetry. The home screen checks npm for updates at most once a day; disable it with RELAYVORA_NO_UPDATE_CHECK=1. If you explicitly run and confirm sync or send, handoffs go to your own Git remote. Launching an agent uses that agent’s normal provider and data policies.

Which agents can I switch between?

Claude Code, Codex, and OpenCode have session adapters and direct CLI launching. Relayvora also finds Claude Code and Codex CLIs bundled with supported editor extensions. Other MCP-capable agents can fetch handoffs and save checkpoints through relayvora mcp.

Will switching agents save me money?

Not always. Small, warm sessions are usually cheaper to continue. The published large-session benchmark reduced tokens and context substantially, but cost was about even. Use Relayvora to keep moving after a limit, switch agents, or resume a large session with work still to do.

Is this actually open source?

Yes. Relayvora is MIT licensed. The CLI, adapters, benchmark harness, and this website live in the repository. Read the source, open an issue, or contribute an improvement.

Contributing guide ↗

Keep the work. Switch the agent.

New agent. Already up to speed.

Less “I think it worked.” More “here’s the evidence.”