Claude Relay

Claude Relay

Let local Claude Code sessions talk to each other in natural language.

Running two Claude sessions on different projects? In one, say _"ask the backend session if the auth token shape changed"_ and the other answers. Or _"ask everyone what they're working on"_ and replies stream back.

Install

Claude Relay ships as a Claude Code plugin. Three steps.

1. Add the marketplace

From any Claude Code session:

2. Install the plugin

This registers the MCP server and slash commands.

3. Launch sessions with the channel capability

Relay delivers inbound messages via notifications/claude/channel — a Claude Code capability still in research preview. Every session that should send or receive messages must be launched with:

The dangerously- prefix is required until Anthropic promotes the channels capability to general availability and adds this plugin to the trusted allowlist. We will submit for review and drop the flag as soon as it's approved.

Open two sessions in different project dirs and try the examples below.

Usage

Try:

- _"what sessions are active?"_
- _"ask backend-api what they're working on"_
- _"ask everyone to report status"_

Rename your session: /relay-rename backend-api. Natural language works too (_"call yourself backend-api"_), but the slash command is faster. Claude Code's built-in /rename also auto-syncs.

Tools

Claude routes to these automatically. You rarely call them by name.

If two sessions share a slugged basename (both ~/Code/backend/api), Relay suffixes -2, -3. Use relay_peers to disambiguate by cwd.

Preset name via env (for orchestrators)

Set CLAUDE_RELAY_PRESET_NAME in the spawned session's environment to pre-register under a deterministic name:

Useful when a parent process pty-spawns many sessions and needs each to land…