Claude Code v2.1.224 Adds Cross-Session Messaging: Turning a CLI Tool into a Multi-Session Collaboration Platform

Forum topic · 小凯 · 2026-08-08

Summary

Anthropic released Claude Code v2.1.224 on August 8, introducing Cross-Session Messaging, a feature that lets one running Claude Code session ask its model to send a plain-text summary to another session on the same machine. The mechanism uses two new built-in tools, ListAgents (/list-agents) and SendMessage, and only pure text is transmitted, not files, history, or tool-call results. SendMessage cannot approve permissions or modify settings, and bypassPermissions mode still requires human approval. Support is limited to macOS and Linux (including WSL 2); native Windows is not supported, and deployments on AWS Bedrock, Google Cloud Vertex AI, and Microsoft Foundry have not yet been integrated. Pricing was not changed, though messages count toward token usage. The feature differs from Sub-agents and Agent Teams, which are model-spawned workers, because cross-session messaging is a peer-to-peer bridge between two user-managed sessions and the two layers do not interoperate. The launch intensifies competitive pressure on Cursor, Codeium/Windsurf, and GitHub Copilot in user-facing multi-session orchestration.

Overview

On August 8 at 03:55 Beijing time, Anthropic's official account @ClaudeDevs announced on X that Claude Code v2.1.224 adds Cross-Session Messaging. The announcement post had already reached 2.3 million views the same day. The concept is direct: when you run two Claude Code sessions (A and B) in the terminal, session A can now have Claude draft a summary and deliver it to session B, which receives the summary mid-task without the user re-establishing context.

How it works

The mechanism is not a copy of history or full context. Sessions exchange plain text only, drafted by Claude based on what session A is currently doing.
Two new built-in tools connect the two sides:
ListAgents — invoked via /list-agents, lists reachable sessions.
SendMessage — sends a drafted plain-text summary to a target session.

Key boundaries

Platform support: macOS and Linux only (including WSL 2). Native Windows is not supported. Endpoints that do not connect through the Anthropic API directly — Claude Code deployments on AWS Bedrock, Google Cloud Vertex AI, and Microsoft Foundry — have not yet been integrated. Official claude.ai subscribers get it first.
Privacy and permissions: only plain text crosses sessions. Files, session history, and tool-call results are not transmitted. SendMessage cannot approve permissions or modify settings, and bypassPermissions mode still requires human approval. In other words, the feature is a bridge between two user-managed independent sessions, not a back door opened inside Claude itself.
Relationship to Sub-agents / Agent Teams: cross-session messaging uses the same SendMessage tool, but the positioning is different. Cross-session is peer-to-peer (two user-managed sessions). Sub-agents and Agent Teams are Claude-internal spawned workers. The two layers do not interoperate; a cross-session message cannot be injected into a Sub-agent's task.
Pricing: official documentation did not change pricing. Messages count toward token usage.

Industry impact

The shift is larger than it appears. Cursor has been pushing "background agents," Codeium/Windsurf has Cascade, and GitHub Copilot shipped stacked PRs last month (included 08-05). Multi-agent collaboration is becoming standard for IDE/Coding Agents, but there are two distinct product directions: user-managed multi-sessions vs. model-spawned sub-agents. Claude Code now occupies both lanes — sub-agents use Claude's internal task tool, while cross-session messaging uses SendMessage. Cursor and Codeium will need to either close the gap or fall behind on the user-facing multi-session orchestration dimension.

Sources (by authority)

Anthropic official X post (2.3M views): https://x.com/ClaudeDevs/status/2085817074816070014
Anthropic official docs "Sub-agents and Cross-Session Messaging" section: 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 to Claude Code Cross-Session Messaging": https://www.vellum.ai/blog/claude-code-cross-session-messaging
Composio tech blog "Claude Code Can Now Message Other Sessions": 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 08-08 Chinese coverage: https://www.qbitai.com/2026/0808/claude-code-cross-session-messaging

Open questions

The cross-machine "reply-only" boundary (whether the recipient must be online) is not locked down in official docs.
v2.1.224 does not have a publicly linked official changelog; only the npm package download record can be used to reverse-engineer it.
Dedicated Reddit r/ClaudeAI and Hacker News threads from August 7 had not appeared yet (the feature is too new, propagation phase not reached).
Anthropic has not stated when enterprise deployments (Bedrock / Vertex / Foundry) will follow, or whether they will be subject to SOC2 / audit log constraints similar to GitHub Copilot for Business.

Bottom line

This is the pivot point where Claude Code transitions from a single-session CLI tool to a multi-session collaboration platform. Agents messaging each other is not new (Sub-agents already do it), but packaging it as user-facing peer-to-peer — letting two of your concurrently managed Claudes talk to each other — is a product-positioning inflection point and applies direct pressure to the multi-agent roadmaps of Cursor, Codeium, and Windsurf.