Claude Code release notes: 2.1.232–2.1.236 connect sessions

Claude Code release notes: 2.1.232–2.1.236 connect sessions

Claude Code 2.1.232 makes it easier to send a message between two independent sessions. Version 2.1.236 adds a one-shot notice that arrives when the receiving session becomes idle. This is useful when several tasks run in parallel and one session needs an answer from another without someone watching the terminal.

Cross-session messaging means that one Claude Code session sends plain text to another session. It does not transfer conversation history or files.

Claude Code 2.1.232 turns an @ mention into an address

Type @ and the first letters of another live session's name. Pick the session from the list and write what it needs to know. Claude Code resolves the mention to that session and uses SendMessage for delivery.

If the recipient is working, it reads the message between tool calls. If the session is idle, the message starts a new turn. Version 2.1.232 also added Messages from your other sessions to /config, where incoming messages can be accepted, held for approval, or refused.

Sources: Claude Code 2.1.232 release notes. Claude Code documentation for cross-session messaging.

Claude Code 2.1.236 can notify you when a session becomes idle

notify_when_idle lets one session ask another session on the same machine to send a notice the next time it becomes idle. The notice is opt-in, sent once, and requires no polling.

This is useful when a test run, migration, or code review is running in another session. Work can continue in the session you are watching, and the notice arrives when the other session has reached an idle state.

Source: Claude Code 2.1.236 release notes.

Availability and limits

Cross-session messaging requires Claude Code 2.1.224 or later and works on macOS and Linux, including WSL 2. The @ mention requires 2.1.232, and the one-shot idle notice requires 2.1.236. The feature is unavailable on native Windows or through Amazon Bedrock, Claude Platform on AWS, Google Cloud's Agent Platform, or Microsoft Foundry.

A message is text, not shared permission. The receiving session's own rules and approval prompts still apply. The npm registry now lists 2.1.237 as current, so both changes are included in the latest release.

Sources: Claude Code documentation for availability and inbound controls. Current Claude Code version in the npm registry.

Try this prompt this week

Human step: Start or name two Claude Code sessions. In the session you are following, type @, select the other session, and then paste the prompt.

Ask @api-worker to send one notice the next time it becomes idle.
In the notice, summarize what is done, what is blocked,
and what this session needs to adapt.
Link the relevant branch or pull request if one exists.

A good response:

  • Arrives as one notice when the receiving session becomes idle.
  • Separates completed work from blockers and the next action.
  • Points to the correct branch or pull request when one exists.

FAQ

What is cross-session messaging in Claude Code?

It is plain-text messaging between independent Claude Code sessions. Conversation history and files are not transferred.

Which platforms support messaging between Claude Code sessions?

The feature works on macOS and Linux, including WSL 2. It is unavailable on native Windows or through Bedrock, Claude Platform on AWS, Google Cloud's Agent Platform, or Microsoft Foundry.

How do I control incoming messages?

Open /config and select Messages from your other sessions. You can accept messages, hold them for approval, or refuse them.

The Forge newsletter

Get new articles in your inbox

Pick the topics you care about. No noise, at most one email a week.

Get new articles in your inbox

We follow GDPR. Unsubscribe anytime.