# Claude Code Now Lets Sessions Message Each Other

URL: https://technosports.co.in/claude-code-now-let-sessions-message-each-other/  
Published: 2026-08-08  
Updated: 2026-08-08  
Author: Raunak Saha

Anyone running multiple Claude Code sessions at once — one per git worktree, one per microservice, one left running overnight — knows the tax: you become the relay, manually copying context from one terminal to another. Anthropic just eliminated that step entirely.

## What Changed

Rolled out on **August 7, 2026**, Claude Code sessions on macOS or Linux can now **message each other directly**, without going through Anthropic’s servers when running on the same machine. Two new tools make it work: **ListAgents**, which discovers other active sessions you can reach, and **SendMessage**, which delivers text to a specific one by name.

A session that receives a message shows it as a labeled card with a link back to the sender, so context never gets lost in the shuffle. For readers tracking how AI coding tools are evolving, this fits a broader pattern we’ve covered in our [AI and developer tools](https://technosports.co.in/category/technology/ai/) coverage.

> New in Claude Code: your sessions can now message each other.  
>   
> Instead of having to re-explain yourself in another session, you can now tell Claude to do it. It sends a summary (not your history or files), and the other session picks it up mid-task. [pic.twitter.com/PtNsfXeQXP](https://t.co/PtNsfXeQXP)
>
> — ClaudeDevs (@ClaudeDevs) [August 7, 2026](https://x.com/ClaudeDevs/status/2085817074816070014?ref_src=twsrc%5Etfw)

## How It Actually Works

| Detail | Information |
| --- | --- |
| Release date | August 7, 2026 |
| Supported OS | macOS, Linux |
| Required version | Claude Code v2.1.224 or later |
| Discovery command | ListAgents (or /list-agents, alias /peers) |
| Messaging command | SendMessage |
| What’s shared | Plain text summary only |
| What’s NOT shared | Conversation history, files, permissions |

Crucially, a message is deliberately thin — it’s text one Claude session writes for another, addressed by name, with a reply path attached. It can’t approve permission requests or change another session’s settings on its own. If you need to hand over full context rather than a summary, resuming the session remains the tool for that job.

## Why Developers Are Excited

The use cases write themselves: one session discovers a breaking API change while working on the backend and warns the frontend session before it wastes time debugging a symptom. Another session waiting on an answer gets it relayed automatically instead of sitting idle. Developers have praised it for cutting friction in parallel workflows — with one only half-joking that it helps AI sessions “plan their escape” by coordinating amongst themselves.

For the official technical rundown, Anthropic’s own [Claude Code documentation](https://docs.claude.com/en/docs/claude-code/overview) covers the full feature set alongside other recent additions like self-hosted runners.

## How to Get It

Update to the latest release by running:

```
claude update
```

---

This pulls v2.1.224 or later, unlocking cross-session messaging alongside Anthropic’s other recent Claude Code improvements. Keep following our [AI tools coverage](https://technosports.co.in/category/technology/ai/) as agentic coding features continue to mature.