Claude Code Sessions Now Message Each Other

Two Claude Code terminals can now exchange notes without you copy-pasting between them. Here's what cross-session messaging actually does and when to use it.

claude-codesessionsagentsmulti-sessionautomation
↻ Updated 2026-11-18EAEvgenii ArsentevEvgenii Arsentev · PhD

Reviewed for accuracy by Evgenii Arsentev, PhD · 2026-11-18

Have you ever found yourself in a situation where you have two Claude Code instances running at the same time (one for backend code and another for frontend code), and something goes wrong in one instance due to changes made in the other? You would probably need to pause your work, copy the relevant data, move to another window, paste it, describe what happened, etc. From version 2.1.224 onwards, Claude can do all these things automatically! Just tell one instance about the changes made in another, and Claude will take care of the rest.

Hi, I’m Evgeny, and I must admit that I didn’t believe this feature would be useful until I realized how much time I waste being a postman between different Claude Code instances. So now I simply ask Claude to do the job!

What is cross-session messaging in Claude Code?

Claude can pass messages between different sessions using cross-session messaging. A message is a snippet of text written by Claude, which is delivered to another instance of Claude. This isn’t a record of past conversations or file transfers — it’s just a bit of text that one Claude sends to another. When the recipient Claude receives the message, it responds accordingly based on the situation. If the message is applicable, the recipient Claude will change its behavior; otherwise, it will continue as usual. It’s like Claude writing a post-it note to itself in another terminal.

When is this actually useful?

I frequently find myself in these scenarios: 1) when changing something (e.g., renaming a variable or table) in session A, Claude lets session B know that it will break things, so session A doesn’t need to explain again; 2) I’m running a time-consuming migration/test in session B and tell session A to notify me once it’s finished (instead of me having to monitor session B); 3) I’m working on the same code in two different terminals and ask session A to give me an overview of its changes, so session B can quickly understand them without needing to read through the diffs. These examples show how you can use Claude during your workflow without planning ahead.

How do you ask one session to message another?

No configuration needed! Just mention in your session where you want the information sent and to whom. Then have Claude look up the session containing the info with the /list-agents command (or use this command yourself to view a list of agents). Once Claude knows which session to send it to, he'll write a message with the details.

Ask Claude to send a message to your other session
Tell the session working on the payments API that users.name is now users.display_name

Claude writes the actual message itself — you just tell it what to communicate and to whom. Run /list-agents to see which sessions Claude can currently reach and what they're named.

From v2.1.232 onwards, you can quickly reference a session by typing @ in your command line interface and then entering the initial characters of the session name. Use the typeahead suggestions to select your desired session. When you do this, Claude Code will send a message to that specific session (@api-worker), instead of sending a message to all your other sessions.

Does Claude decide on its own, or do you have to ask every time?

Both! Claude will automatically share messages if it thinks they’re relevant to the other session (e.g., if you rename a function being used by the other session). It can also automatically respond to messages received from other sessions. Or, you can ask Claude to share messages by saying “share this with the other session.” Don’t worry, Claude won’t share your history or files with other sessions; it will only share text.

What does an incoming message look like?

A ‘Message from’ line appears on your conversation when someone sends a message. You can view the entire message by pressing Ctrl + O to open the expanded view. When you’re idle, Claude Code will respond to the message like a new turn (just like if you had typed a response). While you’re in the middle of something, messages will be inserted after tools are called but before the next tool is called. After being sent, the message will count towards your usage limit and the recipient Claude may respond back!

ℹWhat travels across sessions — and what doesn't

A message is text Claude writes for the other session. Your conversation history, open files, and context window content stay private to your session and never cross over. To move a whole conversation, use /resume instead.

Can sessions on different machines message each other?

Yep, you can interact with other instances running on other computers or Claude Code on the Web if you have Remote Control enabled. Inter-machine messaging happens over Anthropic’s servers (not just local sockets). To start a conversation, you need v2.1.225 or newer. Older versions will only be able to respond to the first message received. By default, Docker container instances cannot communicate with non-container instances (because they don’t share the same filesystem), but instances within the same container can.

Requirements and availability

Cross-session messaging is available on macOS, Linux, and Windows. You need Claude Code v2.1.224 or higher on macOS/Linux/WSL 2, or v2.1.234 or higher on native Windows (run claude update to upgrade). Once your sessions are up to date, cross-session messaging will be enabled automatically. If you’re using Claude Code via Amazon Bedrock, Google Cloud’s Agent Platform, or Microsoft Foundry, you will also need Claude Code v2.1.248 or higher for messaging between sessions on the same machine.

Psst! Did you know you’ve been playing the role of a messenger boy between different instances of yourself? Well now you don’t have to anymore — open another terminal window this week and let Claude help you get things done with another instance of yourself!

Free course

Stop reading about AI — start building with it

The free Claude Code course: your first site, tool or game — no coding. No upsells, no cross-sells — nothing to buy here.

Start free →
EAEvgenii Arsentev

Author

Evgenii Arsentev

PhD · Founder & CEO, Dad4Kids

Reading is a good start

Want to actually build this?

Guides explain. The free course transforms — personalized, gamified, and built to get you shipping fast.

Start the free course →