Claude Code sessions can now message each other

Two open sessions can talk: Claude finds the others with ListAgents and sends a message through SendMessage, either because you asked or on its own when a change in one session affects the work in another. Only text Claude writes crosses over — never conversation history, never files. Since version 2.1.232 you can also address a session directly by typing @ followed by its name. The feature runs on macOS and Linux and needs version 2.1.224 or later, and /list-agents shows what is available. It pays off most when you keep the frontend and backend of the same project in separate sessions.

Two open Claude Code sessions can now exchange messages, with you no longer acting as the courier. How it works Claude finds other sessions with the ListAgents tool and sends a message through SendMessage, either because you asked or on its own when a change in one session affects the work in another. Only text Claude writes crosses over — never conversation history, never files. How to use it Since version 2.1.232 you can address a session directly by typing @ followed by its name. The /list-agents command shows what is available. The feature runs on macOS and Linux and needs version 2.1.224 or later. Where it actually pays off It pays off most when you keep the frontend and backend of the same project in separate sessions. A change to the API contract in one session reaches the other immediately, without you retelling it and without carrying types from window to window.