project relayv0.2
OPEN SOURCE · LOCAL FIRST · MIT LICENSE

Your agents.
One conversation.

Claude in VS Code. DeepSeek in your harness. Gemini in Antigravity.
Give them a shared project inbox, memory, and a way to hand off work.

Connect your agents See the handoff

Runs on your machine. No model API key needed for the demo.

THREE AGENTS. ONE SHARED PROJECT.

Scripted replay · real MCP test
project / health-endpointLOCAL
CReady

Claude

VS Code

Waiting for project context
DReady

DeepSeek

Custom harness

Waiting for project context
GReady

Gemini

Antigravity

Waiting for project context
PROJECT RELAY MCP + HTTP
00 / 05

Different tools. Shared context.

Play a replay of the included three-process protocol demo.

This is an illustrative replay of a passing protocol demo, not live model output. Run project-relay demo to verify the real MCP exchange locally.

LESS COORDINATION WORK

Stop being the
copy-paste between agents.

Keep your tools and models. Give them a small, shared place to coordinate.

01

A durable shared inbox

Ask a peer, broadcast a result, and acknowledge what was handled. Unread messages survive reconnects.

02

Ownership before edits

Claim a task and its files. Atomic claims flag overlaps, and expiring leases let peers recover interrupted work.

03

Context that carries over

Keep API contracts and decisions in shared notes. Hand off with branch, file, and test context in one transaction.

FROM ZERO TO THREE PEERS

Try the handoff.
Then bring your agents.

Node.js 22.13+ · macOS / Linux
Python is optional for custom harnesses.

1. Install the prebuilt GitHub release
npm install -g https://github.com/MuhammadFarhantahirvoltic/project-relay/releases/download/v0.2.0/project-relay-0.2.0.tgz
2. Run the protocol demo
project-relay demo

Three independent processes. No model calls.

3. Connect your project
project-relay init --project /path/to/repo

Generates a separate MCP config for each agent.

Merge each generated config into its host's MCP settings. Agents check their inbox at task boundaries. Read the integration guide

Small protocol.
Clear boundaries.

Your host stays in control. Relay does not invoke models, execute peer messages, deploy code, or wake idle editors automatically.

File claims coordinate; they do not lock your editor. Use separate worktrees when useful. Peers still follow the user's permissions.

Multiple projects, separate conversations. Run one local relay for many repositories. Each keeps its own inbox, notes, tasks, and file claims. Set up multiple projects ↗

BUILT IN THE OPEN

Which harness should
we connect next?

Bring an adapter, a reproducible bug, or a real workflow.

Join the discussion