An account limit.
A controlled handoff.

Agent Relay supervises coding-agent conversations on your machine. When usage exhaustion is verified, it can move a Relay session to the next eligible profile while preserving one active owner.

Install with Homebrew How handoff works

Your provider tools. Isolated profiles. Explicit session ownership.

Runs locally
Claude Code + Codex
Isolated provider profiles
Fail-closed verification
One owner per session

AGENT RELAY / CLIOUTPUT EXCERPT

$ relay status --live

Agent Relay

Current
  claude-main · Claude
  Session 9cc4d728
  ✓ Checks passed

Automatic handoff
  ✓ Ready.

Configured fallback chain
  1. claude-backup  ✓ Checks passed
  2. codex-main     ✓ Checks passed

Representative v0.5.2 excerpt; example profiles and session ID. Readiness depends on local configuration and provider checks. Inspect the renderer ↗

01 / The handoff path

Continue the work.
Keep ownership explicit.

A Relay session tracks a conversation and its active profile. Choose your fallback order; Relay verifies when a handoff is allowed.

01
Start a managed conversation
Set up isolated profiles, choose their order, then launch Claude Code or Codex through Relay.
relay claudeorrelay codex
02
Supervise the active profile
Relay tracks the session owner and provider usage signals. Unknown or unverified usage does not trigger an automatic handoff.
Read the eligibility rules →
03
Hand off when verified
On verified exhaustion, Relay checks the next eligible profile, confirms the source has stopped, and verifies the target.
Or switch manually →

What continues?

Claude → Claude

Native continuation resumes the same Claude conversation under another profile.

Any handoff involving Codex

A new native session receives repository facts, git state, and bounded recent conversation context. Provider prompt caches are not transferred.

02 / Safety before availability

A handoff needs evidence.

Relay fails closed when usage, process identity, or target verification is uncertain. It does not infer exhaustion from vague percentages or bypass provider limits.

Architecture ↗Security model ↗

One active owner per Relay session: Ownership and process checks guard each transfer. Multiple sessions can share a project; Relay does not serialize file edits across them.
Provider-owned authentication: Claude and Codex use isolated profile directories. Relay never reads, copies, or routes your credentials.
Journaled, recoverable transfers: Handoffs record their state. Diagnostics and explicit recovery use that evidence to determine a safe next step.
Local supervision: No Relay-operated server. Provider communication stays with your installed Claude Code and Codex tools.

03 / Inspect and control