English static mirror for SEO/GEO · AI-assisted translation · Read Chinese original

Claude Code v2.1.224 Adds Cross-Session Messaging: From Single-Session CLI to Multi-Session Collaboration

Forum topic · 小凯 · 2026-08-08

Summary

Anthropic announced Cross-Session Messaging for Claude Code v2.1.224, letting one terminal session ask Claude to send a Claude-drafted text summary to another independently managed session. The feature uses two new built-in tools: ListAgents (via /list-agents) to enumerate reachable sessions and SendMessage to deliver messages. It is peer-to-peer messaging between user-managed sessions, not context or history duplication, and distinct from Sub-agents/Agent Teams, with which it does not interoperate. Availability is limited to macOS and Linux (including WSL 2); native Windows, AWS Bedrock, Google Cloud Vertex AI, and Microsoft Foundry deployments are not yet supported. Messages are plain text only—no files, session history, or tool results—and SendMessage cannot approve permissions or modify settings; bypassPermissions still requires manual approval. Pricing is unchanged, though message tokens count toward usage. The move positions Claude Code on both sides of multi-agent collaboration (internal sub-agents plus user-orchestrated sessions), pressuring Cursor, Codeium/Windsurf, and GitHub Copilot, whose approaches focus on background or model-derived agents.

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 sessions
  • SendMessage — delivers the message
  • Key boundaries

  • 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. SendMessage cannot approve permissions or change settings; bypassPermissions mode 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 SendMessage tool, 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.
  • 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.

    Sources (by authority)

  • 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
  • Still unclear

  • 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
Bottom line: this is a turning point in Claude Code's evolution from a single-session CLI tool to a multi-session collaboration platform. Agents messaging each other isn't new (Sub-agents already do it), but making it a user-perspective peer-to-peer feature—"let two Claudes I manage talk to each other"—is a shift in product positioning that puts direct pressure on the multi-agent roadmaps of Cursor, Codeium, and Windsurf.

Tags

#claude-code#anthropic#cross-session-messaging#ai-coding-agents#multi-agent-collaboration#developer-tools#cursor#windsurf

This page is an English static mirror generated for search and AI citation. It may be a full translation or structured summary of the Chinese original. Canonical interactive discussion lives on the Chinese page: https://zhichai.net/topic/178603064