Today we're releasing SendMessage tool for Claude Code, allowing it to message other Claude Code sessions directly (on any machine!). Here's a visualization Claude cooked up of all of my current sessions, connected and grouped by how recently they've sent each other messages.
We've found this super useful for organizing ad hoc teams, communicating dependencies, and self-organizing around deliverables.
Try it out today by updating Claude Code to the latest version and telling Claude to message another session (by name, via /rename!)
If you've used Agent Teams, this is the underlying mechanism, but no longer constrained to within a single team. It's ANY Claude Code session messaging ANY other Claude Code session, and it's no longer a research preview (sorry that took so long!). And yes, you can turn it off.
Excited to see what you all build with this!
Notes: remote control is required for cross-machine messaging. Windows support coming soon (sorry!), and it's not yet fully supported in certain constrained contexts, like HIPAA-compliant and 3P deployments (Bedrock, Vertex, etc.)
Today we're releasing SendMessage tool for Claude Code, allowing it to message other Claude Code sessions directly (on any machine!). Here's a visualization Claude cooked up of all of my current sessions, connected and grouped by how recently they've sent each other messages.We've found this super useful for organizing ad hoc teams, communicating dependencies, and self-organizing around deliverables.
Try it out today by updating Claude Code to the latest version and telling Claude to message another session (by name, via /rename!)If you've used Agent Teams, this is the underlying mechanism, but no longer constrained to within a single team. It's ANY Claude Code session messaging ANY other Claude Code session, and it's no longer a research preview (sorry that took so long!). And yes, you can turn it off.Excited to see what you all build with this!
Notes: remote control is required for cross-machine messaging. Windows support coming soon (sorry!), and it's not yet fully supported in certain constrained contexts, like HIPAA-compliant and 3P deployments (Bedrock, Vertex, etc.)
yes
Today we're releasing SendMessage tool for Claude Code, allowing it to message other Claude Code sessions directly (on any machine!). Here's a visualization Claude cooked up of all of my current sessions, connected and grouped by how recently they've sent each other messages. ... We've found this super useful for organizing ad hoc teams, communicating dependencies, and self-organizing around deliverables.
Try it out today by updating Claude Code to the latest version and telling Claude to message another session (by name, via /rename!) ... If you've used Agent Teams, this is the underlying mechanism, but no longer constrained to within a single team. It's ANY Claude Code session messaging ANY other Claude Code session, and it's no longer a research preview (sorry that took so long!). And yes, you can turn it off. ... Excited to see what you all build with this!
Notes: remote control is required for cross-machine messaging. Windows support coming soon (sorry!), and it's not yet fully supported in certain constrained contexts, like HIPAA-compliant and 3P deployments (Bedrock, Vertex, etc.)
Missing some Tweet in this thread? You can try to
Update
