Project Relay v0.3.1 — Directory privacy policy

This update adds a public privacy policy for the Claude directory submission and documents the existing security tests for reviewers. Coordination behavior and separate project conversations are unchanged.

Install in Claude Code:

/plugin marketplace add MuhammadFarhantahirvoltic/project-relay
/plugin install project-relay@project-relay-marketplace
/project-relay:setup

Existing users can update with /plugin update project-relay@project-relay-marketplace and reload plugins.

The community marketplace is public. Official Claude directory publication requires separate submission and review.

Project Relay v0.3.0 — Claude Code plugin

Install Project Relay directly in Claude Code:

/plugin marketplace add MuhammadFarhantahirvoltic/project-relay
/plugin install project-relay@project-relay-marketplace
/project-relay:setup

Give Claude Code, DeepSeek harnesses, Antigravity, and other MCP hosts a shared inbox, notes, tasks, and handoffs. Run setup separately in each repository; project conversations stay isolated.

• Three skills: setup, inbox, and coordination.
• Seventeen project-scoped MCP tools.
• Explicit enrollment, no automatic repository scanning or model calls.
• Readable bundled runtime and locked dependencies. Node.js 22.13+ and npm required.
• 28 passing tests, strict Claude plugin validation, and successful installation/MCP connectivity in an isolated Claude Code 2.1.284 profile.

See the plugin guide for other hosts, custom state directories, and multiple windows/worktrees.

The plugin is available through Project Relay's community marketplace. Anthropic's official directory requires separate submission and review. The release targets Claude Code; cross-editor local coordination in Claude web chat or Cowork is not claimed.

The attached .tgz is the standalone Node.js CLI package. Plugin users install from the GitHub marketplace above. Existing protocol 1.0 identities remain compatible.

Project Relay v0.2.0 — Multiple projects, separate conversations

Project Relay now makes it straightforward to run the same agents across multiple projects while keeping a separate conversation for every repository.

What's new

• project-relay projects lists enrolled projects, their UUIDs, roots, and active identity counts.
• config --agent ID --projects UUID,UUID generates separate MCP connections for an explicit selection of projects.
• Complete UUIDs in compact config keys prevent one project's entry overwriting another when short prefixes match.
• Missing, revoked, mismatched, invalid, or duplicate project selections fail instead of producing a partial config.
• A multi-project setup guide covers separate editor sessions, global MCP settings, shared HTTP routing, and event cursors.

Install and connect

Requires Node.js 22.13+.

npm install -g https://github.com/MuhammadFarhantahirvoltic/project-relay/releases/download/v0.2.0/project-relay-0.2.0.tgz
project-relay init --project /path/to/project-a
project-relay init --project /path/to/project-b
project-relay projects

Use each project's generated MCP fragment in its corresponding agent session. For global host settings, replace the UUID placeholders with values from projects:

project-relay config --agent gemini-antigravity --projects PROJECT_A_UUID,PROJECT_B_UUID --format antigravity

Every connection remains bound to one project. There is no cross-project messaging or global active-project switch. The same agent IDs, note keys, task titles, and relative paths can exist independently in multiple projects sharing one SQLite database and HTTP broker.

Verification

All 25 tests and the three-process demo pass in CI on macOS and Linux with Node 22 and 24. New tests run six MCP processes across two projects concurrently and check isolation across messages, receipts, replies, notes, tasks, handoffs, file claims, events, presence, and revocation. CLI tests enroll three projects and verify explicit config selection.

The packed v0.2.0 release was installed over v0.1.0 in a fresh environment containing two projects. Existing identities, config paths, and saved inbox messages survived the upgrade and remained separate. Tests use scripted clients; live vendor model sessions are not claimed.

Upgrading

No database or identity migration is required. Older v0.1 server entries still work. Newly generated entries use relay- plus the complete UUID without hyphens. When replacing configuration, remove the older Project Relay entry for the same project and preserve unrelated MCP servers to avoid duplicate connections.

Project Relay Protocol remains 1.0. This is a single-machine implementation for a trusted OS user; file claims are advisory, and hosts still control model execution and inbox checks.

Source change · Interactive demo

Project Relay v0.1.0 — Your agents. One conversation.

Project Relay gives agents in different coding tools a shared project inbox, notes, task ownership, and handoffs through MCP.

Try the release

Requires Node.js 22.13+.

npm install -g https://github.com/MuhammadFarhantahirvoltic/project-relay/releases/download/v0.1.0/project-relay-0.1.0.tgz
project-relay demo
project-relay init --project /absolute/path/to/your/repository

The included demo connects three independent MCP processes and exercises shared notes, a rejected overlapping file claim, task handoff, and a result broadcast. Clients are scripted; no model API is called.

Included

• Project Relay Protocol 1.0 and 17 tools over MCP stdio, MCP HTTP, JSON HTTP, and CLI.
• SQLite persistence, scoped credentials, per-recipient acknowledgements, and expiring ownership leases.
• Configuration fragments for Claude Code, VS Code, Antigravity, and generic MCP hosts.
• A Python adapter for custom harnesses, integration documentation, and a responsive interactive replay.

Verification and scope

All 20 local tests pass, including independent MCP subprocesses, HTTP authentication and isolation, concurrency, reconnection, and the Python adapter. Installation of the packed release, its executable demo, and three-identity setup were checked in a fresh temporary directory. Remote CI results are available on the repository's Actions page.

This initial release runs on one machine under a trusted OS user. File claims are advisory. Automatic wakeup of idle editors and live sessions with each vendor's models remain host integration work.

Interactive demo · Integration guide · Protocol

The prebuilt package and SHA-256 checksum are attached below. MIT licensed.