Claude Code Now Supports Direct Messaging Between Concurrent Sessions

Claude Code ships cross-session messaging, documented in the official release notes at code.claude.com. Sessions can now send messages to other running Claude Code instances, enabling multi-agent coordination without manual handoffs.

The practical shift: workflows that previously required a developer to copy context from one session and paste it into another can now run autonomously. A session handling code review can flag issues directly to a session running tests. A session scaffolding a feature branch can notify a parallel session responsible for documentation. The developer stays out of the message path.

For solo founders running Claude Code as a force multiplier, this reduces the orchestration tax. Keeping multiple sessions productive historically meant context-switching and manually synchronizing state. Cross-session messaging delegates that synchronization to the sessions themselves.

For senior engineers building agentic pipelines, the capability unlocks tighter feedback loops between specialized agents. Rather than designing a single monolithic session to handle an entire task graph, you can decompose work into focused sessions and wire them together through direct messaging. Each session maintains a narrower context window load while still participating in a coordinated workflow.

The documentation covers how to address a specific session and how messages are received within an active session's context. Session identity and addressability are the core primitives the feature exposes.

This follows the broader pattern Anthropic is building with Claude Code: moving from a single-agent coding assistant toward infrastructure that supports multi-agent software development natively in the terminal. Cross-session messaging is an infrastructure primitive, not a feature with a UI. Engineers who think in systems will find direct use for it immediately.

Source