Claude Code Sessions Can Now Talk to Each Other
While everyone else ships swarm orchestration platforms, Anthropic shipped the humble version: your Claude Code sessions can now leave each other notes. Version 2.1.224, out August 7 on macOS and Linux, lets one running session deliver a message to another session on the same account.
The design is more interesting than the headline. You don't compose the message — you tell Claude what the other session needs to know, and Claude writes a summary and delivers it. It sends the summary, not your conversation history or files, and the receiving session picks it up mid-task without stopping. Messages between sessions on the same machine stay local and never touch Anthropic's servers. And an incoming message can't approve a permission request or change the receiving session's settings — a small line in the docs that shows someone thought about what happens when agents start instructing each other.
The use cases are the everyday frictions of running multiple sessions: one session changes an API that another session is building against, and the second one gets warned before you notice the breakage. One session settles a question another is blocked on, and the answer travels across without you replaying context by hand. Anyone who runs three terminals of Claude Code side by side has been doing this manually with copy-paste; now the agents do it themselves.
The contrast with the rest of the market is the story. The past month gave us tmux-based agent crews, git-worktree swarms, and multi-agent frameworks with control planes. Anthropic's answer to multi-agent coordination is a point release where agents pass notes. No orchestrator, no DAG, no new vocabulary — just sessions that can talk. Sometimes the primitive is the product.
Windows isn't supported at launch. Docs: code.claude.com/docs/en/cross-session-messaging
← Back to all articles
The design is more interesting than the headline. You don't compose the message — you tell Claude what the other session needs to know, and Claude writes a summary and delivers it. It sends the summary, not your conversation history or files, and the receiving session picks it up mid-task without stopping. Messages between sessions on the same machine stay local and never touch Anthropic's servers. And an incoming message can't approve a permission request or change the receiving session's settings — a small line in the docs that shows someone thought about what happens when agents start instructing each other.
The use cases are the everyday frictions of running multiple sessions: one session changes an API that another session is building against, and the second one gets warned before you notice the breakage. One session settles a question another is blocked on, and the answer travels across without you replaying context by hand. Anyone who runs three terminals of Claude Code side by side has been doing this manually with copy-paste; now the agents do it themselves.
The contrast with the rest of the market is the story. The past month gave us tmux-based agent crews, git-worktree swarms, and multi-agent frameworks with control planes. Anthropic's answer to multi-agent coordination is a point release where agents pass notes. No orchestrator, no DAG, no new vocabulary — just sessions that can talk. Sometimes the primitive is the product.
Windows isn't supported at launch. Docs: code.claude.com/docs/en/cross-session-messaging
Comments