On August 8 at 3:55 AM Beijing time, Anthropic's official @ClaudeDevs account on X announced that Claude Code v2.1.224 introduces Cross-Session Messaging. The announcement post reached 2.3 million views the same day.
The concept is simple: if you are running two Claude Code sessions, A and B, in your terminal, session A can now ask Claude to relay a message to B, and B receives that summary in the middle of its own task—no need to re-explain what A was doing.
How it works
The mechanism does not copy history or duplicate the entire context. Only plain text travels between sessions, and the text is drafted by Claude itself: it reads what session A has been doing and writes a summary to send over. Two new built-in tools handle the plumbing:
ListAgents(also available as/list-agents) — lists reachable sessionsSendMessage— delivers the message- Platform support: macOS and Linux only (WSL 2 included); native Windows is not supported. Deployments via AWS Bedrock, Google Cloud Vertex AI, and Microsoft Foundry are not yet connected—this is initially for official claude.ai subscribers.
- Privacy: messages carry plain text only—no files, no session history, no tool-call results.
SendMessagecannot approve permissions or change settings;bypassPermissionsmode still enforces manual approval. In other words, this is a bridge between two user-managed sessions, not a backdoor for Claude internally. - Relation to Sub-agents / Agent Teams: it uses the same
SendMessagetool, but the positioning is entirely different. Cross-session messaging is peer-to-peer (two sessions the user manages independently), while Sub-agents / Agent Teams are workers derived by Claude internally. The two layers do not interoperate—cross-session messages cannot be injected into Sub-agent tasks. - Pricing: official docs leave pricing untouched; messages simply count toward token usage.
- Anthropic official X post (2.3M views): https://x.com/ClaudeDevs/status/2085817074816070014
- Anthropic docs, "Sub-agents and cross-session messaging": https://docs.claude.com/en/docs/claude-code/sub-agents (301-redirected to docs.claude.com/en/docs/claude-code/agents)
- Vellum AI engineering blog, complete guide: https://www.vellum.ai/blog/claude-code-cross-session-messaging
- Composio technical blog: https://composio.dev/blog/claude-code-cross-session-messaging
- The Daily AI briefing, 08-07 follow-up: https://www.thedailyai.co/p/claude-code-can-now-message-other-sessions
- QbitAI Chinese coverage, 08-08: https://www.qbitai.com/2026/0808/claude-code-cross-session-messaging
- The cross-machine "reply-only" boundary (whether you can reply to the other session, and whether it must be online) is not pinned down in official docs
- No public official changelog link for v2.1.224; only npm package download records can be reverse-engineered
- Dedicated discussion threads on Reddit r/ClaudeAI and Hacker News from August 7 had not yet appeared (the feature is too new)
- When enterprise editions (Bedrock / Vertex / Foundry) will follow, and whether they will be subject to SOC2 / audit-log requirements like GitHub Copilot for Business, Anthropic has not said
Key boundaries
Why it matters
The competitive implications go beyond the surface. Cursor has been pushing background agents, Codeium/Windsurf is building Cascade, and GitHub Copilot shipped stacked PRs (added on 08-05). Multi-agent collaboration is now standard across IDEs and coding agents, but "user-managed multi-session" and "model-derived sub-agents" are two distinct product directions. Claude Code now occupies both: sub-agents via its task tool, cross-session messaging via SendMessage. Cursor and Codeium must catch up or fall behind on the user-perspective multi-session orchestration dimension.