---
type: analysis
slug: research-claude-code-sessions-can-message-each-other-as-a-shipped-anthropic-feature
title: "Claude Code sessions can message each other as a shipped Anthropic feature"
description: "Anthropic added cross-session messaging in Claude Code 2.1.224 on 7 August 2026. Independent sessions pass plain text through ListAgents and SendMessage; they do not share conversation history, files, or permission authority."
published_at: 2026-10-26T09:00:00.000Z
topics: ["claude","anthropic","claude_code","research"]
source_urls: ["https://github.com/anthropics/claude-code/releases/tag/v2.1.224","https://code.claude.com/docs/en/whats-new/2026-w32","https://code.claude.com/docs/en/cross-session-messaging","https://code.claude.com/docs/en/whats-new","https://code.claude.com/docs/en/agent-teams","https://9to5mac.com/2026/08/07/claude-code-now-lets-sessions-talk-to-each-other-on-macos/","https://code.claude.com/docs/en/agents","https://github.com/anthropics/claude-code/releases/tag/v2.1.225","https://github.com/anthropics/claude-code/releases/tag/v2.1.234","https://github.com/anthropics/claude-code/releases/tag/v2.1.239","https://github.com/anthropics/claude-code/releases/tag/v2.1.248","https://github.com/anthropics/claude-code/issues/84726","https://code.claude.com/docs/en/changelog","https://www.macrumors.com/2026/08/08/claude-code-adds-cross-session-messaging/"]
author: "Andrey Reshetnikov"
author_profile: https://newruntime.com/owner-profile.md
---
The newsroom flagged an X-only claim that Claude Code sessions can message each other. If that were a user hack or third-party glue, teams could not treat it as a supported coordination primitive, and security reviewers would have no documented controls. If it were real and on by default, every extra terminal would become a peer that can inject billed, model-visible text into other sessions on the same account.

The primary record is unambiguous. Anthropic shipped cross-session messaging in Claude Code v2.1.224 on 7 August 2026 and documented it as a first-party way for sessions the user already runs to pass findings, status, and decisions. It sits beside, and is not the same as, experimental agent teams. Independent outlets reported the launch the same day and the next morning. The original X post returned HTTP 403 in this session and is not used as a source.

## What we checked

- **Is this an official Claude Code feature, a third-party workflow, or a user hack?** confirmed. It is an official, default-on Claude Code feature. Anthropic’s Week 32 digest and the v2.1.224 GitHub release describe sessions messaging each other via ListAgents and SendMessage, and the product docs say messaging is on with nothing to enable once version and OS requirements are met. [3][2][1]
- **Is there an Anthropic docs or changelog URL?** confirmed. Yes. The product page is the cross-session messaging guide on code.claude.com, introduced in the Week 32 digest for 3–7 August 2026. The shipping changelog is the v2.1.224 GitHub release; later changes appear in subsequent tags and on the generated changelog page. [3][2][1][13]
- **Do sessions share conversation history or files, and can one session approve permissions or change another session’s configuration?** refuted. A cross-session message is plain text only, never the sender’s history or files. Anthropic documents that an incoming message cannot approve a permission prompt, change CLAUDE.md or other configuration, or run slash commands, which arrive as text. The receiving session’s own permission prompts still apply. [3][6][14]
- **Did the feature work the same way on Windows, across machines, and on third-party providers from the day it shipped?** partly confirmed. Same-machine messaging on macOS and Linux shipped in v2.1.224. Starting a conversation with a Remote Control session on another machine required v2.1.225 after a launch-day discovery deadlock. Native Windows was announced in the v2.1.239 notes, while current docs list v2.1.234 as the Windows floor. Same-machine messaging on Bedrock, Vertex, Foundry, and with flag fetching off requires v2.1.248. [1][8][10][11][3][12]

## What we found

- Anthropic launched the feature in Claude Code v2.1.224, tagged on GitHub at 2026-08-07T04:00:59Z. The Week 32 digest for 3–7 August 2026 and the release notes both say sessions can message each other: Claude discovers peers with ListAgents and sends with SendMessage, either when asked or on its own after a change that affects another session. Recipients show a Message from row that expands with Ctrl+O. /list-agents lists reachable sessions. Current docs say messaging is on with nothing to enable when the session meets version and OS requirements. [1][2][3][4]
- The channel is a text note, not shared memory. Docs state a message is text one Claude writes to another, never the sender’s conversation history or files; resume a session to move whole context. The same SendMessage tool also addresses subagents and agent-team teammates, but structured team protocol messages stay inside a team. Once delivered, a message counts toward usage like a prompt you type. The receiving Claude can reply except for one-way cross-machine sends and when messaging is turned off. [3][5]
- How a message travels depends on where the target runs. Same-machine delivery uses a per-session Unix domain socket on macOS and Linux, or a named pipe on native Windows, and never goes through Anthropic servers. Messages to another of your machines or to a cloud session travel through Anthropic servers over Remote Control and need a claude.ai sign-in as the session’s active authentication. A session in a container cannot reach the host; WSL 2 and native Windows on the same computer cannot reach each other. Sockets are restricted to the operating-system user. [3]
- Permission isolation is a documented product rule, not an informal hope. Claude Code tells the receiver the text came from another session, not from you. An incoming message cannot approve a permission prompt, change permission settings or CLAUDE.md, or execute a slash command; those strings arrive as plain text. The receiving session’s own prompts and rules still apply to anything the message asks for. Default inbound policy holds a message for approval when the two sessions’ permission-mode classes differ. Operators can set crossSessionInbound to accept, hold, or refuse, require isolatePeerMachines before any send leaves the machine, or deny SendMessage and ListAgents. Denying SendMessage also removes messaging to subagents and teammates. [3][5][6]
- This is not the experimental agent-teams stack. Agent teams stay off unless CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is set to 1. They use a lead, teammates, a shared task list, and JSON mailboxes under ~/.claude/teams/. Anthropic tells users to prefer cross-session messaging when they only need to pass findings between sessions they run themselves. The parallel-agents guide lists messaging as a supporting tool for those sessions, including ones dispatched from agent view, not as a fifth coordination style. [5][7]
- Availability widened after launch day. v2.1.224 was macOS and Linux. v2.1.225, published 8 August 2026, let SendMessage start a conversation with Remote Control sessions on other machines instead of only replying; a same-day GitHub issue had shown that ListAgents listed those sessions while SendMessage refused them as reply-only. v2.1.239, published 21 August 2026, says Windows cross-session messaging is now available. v2.1.248 added same-machine messaging on Bedrock, Vertex, and Foundry and when telemetry is disabled. Current docs still list native Windows at v2.1.234 or later, a floor the v2.1.234 notes do not announce as a Windows launch. MacRumors on 8 August 2026 still said the feature was unavailable on Windows, which matched the v2.1.224 shipping note. [1][8][9][10][11][12]

## What it means

Treat this as shipped product behavior, not a demo or a community recipe. If you run several Claude Code sessions on one machine at v2.1.224 or later, they can discover and text each other without a feature flag. Claude may send after a breaking change without being asked. Incoming text is untrusted relative to the user: it can still cause the receiver to act, it is billed as a prompt, and it is subject to that session’s permissions. For production fleets, set an explicit inbound policy. Unattended claude -p workers need crossSessionInbound set to accept if they must take messages without a human, because messages held under the bypass-permissions default expire (five minutes unless dialogExpiry is changed). Same-machine traffic stays local; cross-machine and cloud traffic hits Anthropic and needs Remote Control.

Do not confuse this with agent teams. If you only need status and findings between terminals you already opened, use messaging plus worktrees. If you need a lead, a shared task list, and structured protocol messages, enable teams knowing they are experimental and disabled by default. Organization admins who want no peer channel should deny SendMessage and ListAgents and set crossSessionInbound to refuse, knowing that the deny also stops subagent messaging. Pin Windows hosts to at least v2.1.239 until the docs and the Windows launch note agree, and pin third-party-provider hosts to v2.1.248 for same-machine delivery.

## Still open

- Current docs list native Windows at v2.1.234, but the GitHub notes first announce Windows availability in v2.1.239; which floor Anthropic intends is not reconciled in the pages opened here.
- How often Claude sends unprompted messages in real multi-session work, and whether the documented loop throttle is enough, is not measured in public primary sources.
- Whether Unix-socket ownership plus the optional messaging token is sufficient on shared hosts, especially when hooks and Bash can post to CLAUDE_CODE_MESSAGING_SOCKET, is not independently audited in the sources opened here.
- Cloud and self-hosted-runner sessions cannot use SendMessage to answer a message from another machine; the operational impact of that one-way path is not quantified.

## Sources

1. [v2.1.224 · anthropics/claude-code](https://github.com/anthropics/claude-code/releases/tag/v2.1.224) (primary)
2. [Week 32 · August 3–7, 2026 - Claude Code Docs](https://code.claude.com/docs/en/whats-new/2026-w32) (primary)
3. [Message your other Claude Code sessions](https://code.claude.com/docs/en/cross-session-messaging) (primary)
4. [What's new - Claude Code Docs](https://code.claude.com/docs/en/whats-new) (primary)
5. [Orchestrate teams of Claude Code sessions](https://code.claude.com/docs/en/agent-teams) (primary)
6. [Claude Code now lets sessions talk to each other on macOS](https://9to5mac.com/2026/08/07/claude-code-now-lets-sessions-talk-to-each-other-on-macos/)
7. [Run agents in parallel](https://code.claude.com/docs/en/agents) (primary)
8. [v2.1.225 · anthropics/claude-code](https://github.com/anthropics/claude-code/releases/tag/v2.1.225) (primary)
9. [v2.1.234 · anthropics/claude-code](https://github.com/anthropics/claude-code/releases/tag/v2.1.234) (primary)
10. [v2.1.239 · anthropics/claude-code](https://github.com/anthropics/claude-code/releases/tag/v2.1.239) (primary)
11. [v2.1.248 · anthropics/claude-code](https://github.com/anthropics/claude-code/releases/tag/v2.1.248) (primary)
12. [Cross-machine SendMessage cannot be initiated: bridge session IDs are computed but never surfaced](https://github.com/anthropics/claude-code/issues/84726)
13. [Claude Code changelog](https://code.claude.com/docs/en/changelog) (primary)
14. [Claude Code Adds Cross-Session Messaging on macOS](https://www.macrumors.com/2026/08/08/claude-code-adds-cross-session-messaging/)

Author: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Claude](https://newruntime.com/topics/claude.md): Explore the claude topic hub.
- topic hub: [Anthropic](https://newruntime.com/topics/anthropic.md): Explore the anthropic topic hub.
- topic hub: [Claude Code](https://newruntime.com/topics/claude-code.md): Explore the claude_code topic hub.
- collection: [Analysis](https://newruntime.com/analysis.json): Open the latest authorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)