Anthropic has updated Claude Code with a notable quality-of-life improvement: cross-session messaging. Now, separate coding sessions running in different Terminal windows can talk to each other directly, eliminating the need to manually copy and paste context between them.
The feature arrived in Claude Code version 2.1.224, which shipped on Friday for both macOS and Linux. While the update covers both platforms, the ability to link sessions is especially seamless on macOS, where multiple Terminal instances are a common part of many developers’ workflows.
What Is Cross-Session Messaging in Claude Code?
In previous versions, if you had two Claude Code sessions running—perhaps one debugging a backend service and another updating a frontend dependency—sharing information meant manually copying error logs, IDs, or query results from one window and pasting them into the other. That friction broke focus and slowed down complex multi-step tasks.
With cross-session messaging, those sessions can now send text directly to one another. A session can warn a peer when a recent change breaks something it depends on, or pass along an answer that another session is waiting on. The goal is to keep developers in their flow without juggling clipboard contents across multiple terminals.
How It Works: ListAgents and SendMessage
Two new tools power this functionality: ListAgents and SendMessage.
· ListAgents scans the local machine to discover other active Claude Code sessions running on the same Mac or Linux system. It returns a list of available sessions that can receive messages.
· SendMessage delivers a text payload from the current session to a target session identified by ListAgents.
When a session receives a message, Claude Code displays it as a labeled card within the interface. The card includes a direct link back to the sender, so you can quickly jump to the originating session if you need more context or want to continue the conversation there.
Anthropic’s documentation clarifies that only plain text passes between sessions. No conversation history, files, or permissions are transferred along with the message. This keeps the feature lightweight and focused on communication rather than state sharing.
Practical Use Cases for Developers
The most immediate benefit is coordination during parallel work. For example, if you are running a session that continuously watches for test failures and another session that applies fixes, the test-watcher can ping the fixer when a particular error clears or when a new regression appears.
Another common scenario involves dependency chains. Suppose Session A is building a library that Session B consumes. If Session A introduces a breaking change, it can proactively warn Session B before the change is finalized, giving you a chance to adjust the dependent code in real time.
For pair debugging, one session might track down a stack trace while another prepares the environment to reproduce it. Passing the exact error message or a specific variable value via SendMessage eliminates re-typing and reduces the risk of transcription errors.
Security and Permission Boundaries
Anthropic designed this feature with clear security boundaries. An incoming message cannot approve a permission request, alter a session’s settings, or execute any action on its own. It is purely a notification or data carrier.
Because only text passes between sessions, sensitive files, environment variables, and access tokens remain isolated. Each session retains its own permissions and context. The sender cannot request elevated privileges or make changes on the receiver’s behalf—it simply delivers a string that you, the developer, can then act upon manually.
This design means you can use cross-session messaging without worrying about one session accidentally compromising another. The labeled card UI also makes it obvious when a message arrives and where it originated, so you always know which peer is communicating with you.
Getting Started with Claude Code 2.1.224
If you are already using Claude Code, updating to version 2.1.224 is straightforward. The release is available for macOS and Linux. After updating, you can test the feature by opening two Terminal windows, starting a Claude Code session in each, and using ListAgents to confirm they can see each other.
From there, try a simple workflow: have one session generate a complex query result and use SendMessage to deliver it to the other. You will notice the labeled card appear almost instantly, with the sender’s link attached for easy navigation.
For teams that rely on Claude Code for infrastructure-as-code, CI/CD troubleshooting, or multi-service development, this feature can reduce the cognitive overhead of switching between windows. It does not replace a full collaborative environment, but it solves a specific pain point that has annoyed developers since the early days of terminal-based assistants.
Cross-session messaging in Claude Code is a small but thoughtful addition that shows Anthropic paying attention to real developer friction. By allowing sessions to exchange text directly, the company removes a repetitive manual step and makes multi-terminal work feel more cohesive.
The feature is available now in Claude Code 2.1.224 for macOS and Linux. If you have been copying context between windows, give it a try—you might find that your debugging and development sessions flow more smoothly when they can talk to each other.
