Claude Code Inter Session

English · 中文

inter-session

Agent-to-agent messaging for Claude Code sessions on the same machine. Each
Claude Code session connects to a local WebSocket bus and can send messages
to other connected sessions; incoming messages are delivered to the
receiving agent as prompts and acted on as instructions by default.
One session can drive another.

Implemented as a Claude Code plugin monitor (a session-long background
task): ms-level delivery latency, no active polling, no 30-minute expiry,
and no token or performance cost when there are no messages.
Does NOT require claude.ai login. No configuration needed.

Localhost only and Unix-only (macOS, Linux, WSL2) for now.

How does this compare to subagents and agent teams?

Claude Code already has two concurrency primitives:
subagents (the Agent
tool — spawn a worker inside your session for a focused subtask) and
agent teams (a team of
independent CC sessions launched together for one task). inter-session
is a different axis: it connects the long-lived Claude Code sessions
you've already opened across terminals and projects, so they can
message each other.

Use a subagent when you need a quick, focused worker that returns
a summary. Your main conversation stays clean.

Use an agent team when teammates need to share findings, challenge
each other, and coordinate inside one task — best for parallel research
with competing hypotheses, parallel code review, and feature work where
each teammate owns a separate piece.

Use inter-session when you have multiple Claude Code sessions
running for unrelated long-lived work and want one to drive another —
e.g. delegating a bug fix from one project's session to another's;
running iterative loops where each side's context grows in value
across many rounds; or letting two sessions with…