CodeRelay

Your agents can work as a team.

CodeRelay hands work between teammates' coding agents. Define who owns each part of the repo, agree on a contract, and send the task to the right person. Their agent returns a summary, branch, and commit for you to integrate.

Download for WindowsTry the local demo

Also for macOS (Apple silicon, Intel) and Linux (x64, arm64 AppImage). Or install from a terminal:

macOS and Linux: curl -fsSL https://site-olive-two-79.vercel.app/install.sh | bash
Windows PowerShell: irm https://site-olive-two-79.vercel.app/install.ps1 | iex

Builds are unsigned, so Windows may ask you to confirm before the installer runs. macOS blocks unsigned apps downloaded in a browser, so the terminal installer is the easiest way to install there. Open source under the MIT license. Bring your existing agent provider and subscription.

CodeRelay / invoice-appAlice → Bob → Alice
  1. 09:41aliceownsapps/web/**
  2. 09:42bobownsapps/api/**
  3. 09:44aliceproposesAdd dueAt to the invoices APIContract: contracts/invoices.md · pinned Git commit
  4. 09:47bobacceptsAgreed contract → local agent thread
  5. 10:12bobreturnsAPI change ready to integrateCompletion summary + branch + commit
An example handoff, from shared contract to completed work. Illustrative, not a live activity feed.

See a handoff between teammates

Bob's agent hands the backend work to Alice while it builds the frontend. Watch both sides in 68 seconds.

A real two-teammate session, with on-screen explanations. Open the video full-size.

From “I need an API” to a change you can integrate

  1. 1

    Declare your areas

    List the paths you own, such as apps/api/**, so agents can route work to you. They can also name a teammate explicitly.

  2. 2

    Agree on the contract

    Push a spec or shared schema and pin the task to its Git commit. Both teammates agree on that version before acceptance.

  3. 3

    Accept into your own agent thread

    Accept the task in chat or the Team hub to start a local agent thread working from the agreed contract.

  4. 4

    Review the result and integrate it

    Fetch the returned branch and commit, review the summary and changes, then integrate. Reopen the task if it needs another pass.

You choose when work starts. Tasks normally wait for your acceptance. Optional automatic tasks let trusted teammates start eligible contract work, with a limit of three attempts and one automatic task in progress at a time. Read about automatic tasks.

Shared context. Your own agents.

A self-hosted hub connects your team. Each teammate's environment connects out to it and keeps running its own agents. If the hub goes offline, local agent work continues.

In your environment

  • Your coding agentsWork with Codex, Claude Code, Cursor, Grok, OpenCode, or Antigravity.
  • Code and worktreesContract files and completed changes travel through your Git remote. Teammates fetch the referenced commits.
  • Provider credentialsEach teammate authenticates their own providers and uses their own subscriptions.
  • Agent conversationsFull transcripts stay in your environment; the hub shares coordination updates.

Across the team

  • Presence and ownershipSee who's online, whether their agents are running, and which repository areas they own.
  • Progress and file claimsShare checkpoint summaries, branches, and paths touched. Claim paths to signal where an agent is working.
  • Interface changesKeep track of changes to routes, schemas, and types that other work depends on.
  • Tasks, contracts, and resultsExchange suggestions and notes, agree on pinned contract references, and return completed work.

Available where you work. Open the Team hub from the sidebar or command palette on web and desktop, or from Settings on mobile. Agents can coordinate through the team MCP tools. Read the Team hub guide.

Try both sides of a handoff

The local demo starts a hub and separate Alice and Bob sessions, already joined to a team. No Docker needed.

Start the local demo

On macOS or Linux, with Node.js 24 and Git installed, one command downloads the source and installs Vite+ (vp) if you need it. Install and authenticate a supported agent provider before starting agent work. Read the installation steps.

curl -fsSL https://site-olive-two-79.vercel.app/install.sh | bash -s -- --source
cd ~/CodeRelay
vp run dev:team

Prefer not to use Git? Download the latest source as a zip, unzip it, and run vp i then vp run dev:team inside the folder.

Give Alice and Bob a task

Open their labeled pairing URLs from the terminal. Set each teammate's owned paths under Your areas, then ask Alice's agent to propose work in Bob's area with a pushed contract.

Review and accept in Bob's session. When the work is complete, return to Alice to review the summary, branch, and commit.

Both demo sessions share the selected project's files. Press Ctrl+C in the launcher terminal to stop the demo.

Run CodeRelay from this checkout. The application currently retains some upstream names and package identifiers. These instructions launch CodeRelay's Team hub workflow.

Connect your teammates

Ready to work across machines? Self-host a hub, connect your team's Git repository, and invite your teammates. Share it over Tailscale or an address your team can reach.

Set up a team hubRead the Team hub guide