Two Claude Code sessions can now exchange messages directly — one can ask the other what it changed, and get a structured answer back. Claude Devs flagged the capability this week.
The mechanism is a session-bridge skill that exposes /bridge commands inside Claude Code:
/bridge connect <id>— links two running sessions by ID/bridge ask "<question>"— sends a query to the connected session and returns its response/bridge status— checks whether the other session is live and connected
A concrete example from Shreyas Patil’s demo: one session working on a library asks another “What breaking changes did you make?” and receives a structured list — login() renamed to authenticate(), getUser() to getCurrentUser(), return type changes included.
This is different from Claude Code’s existing session-sharing feature, which lets humans view a conversation via link. Session-bridge is session-to-session: no human in the loop on the receiving end.
The use case is multi-agent coordination. If you’re running one Claude Code session on a frontend and another on a backend, the frontend session can query the backend session’s state directly instead of you manually copying context between terminals.
NOTE
Session-bridge is a community-built skill, not an Anthropic product feature. Both sessions must be running and connected to the same bridge channel.
The session-bridge skill works today — run /bridge connect in both sessions after installing the skill to link them.