Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.224 ·

Messages from other sessions can be held for your approval

Messages from a session with a mismatched permission mode are held and shown with an approve/deny dialog.

You'll notice New Features
JSON All of v2.1.224
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
New FeaturesKind: in v2.1.224,
What probably matters to youSection of the release
What

When another Claude Code session sends this one a message, it can now be held instead of delivered. Two new reasons for holding: the sender's permission mode does not match yours, and a sender that never stated its mode into a session that bypasses prompts. Held messages appear with an explanation and, where a permission handler is wired up, an approve/deny dialog with a preview. Approving, denying or letting it expire sends a status message back to the sender.

Details
  • Behaviour is controlled by the crossSessionInbound setting, resolved from policy, flag and user settings, then narrowed to the most restrictive of local and project settings.
  • With no explicit setting, a session that bypasses prompts defaults to holding messages and every other session defaults to accepting them. An unrecognized permission mode fails closed to hold.
  • Hold reasons recorded are explicit-setting, mode-unknown, mode-mismatch, no-mode-asserted and bypass-default; held, accepted and refused outcomes are all reported.
  • The sender-mode matching half is additionally behind the tengu_harbor_kite_mode_emit flag, which is off in this build.
  • The approval dialog is registered as a new notification type with its own title.
Evidence

A message from another session needs your approval, The sender did not attest its permission mode and this session bypasses prompts. Review it below, or set "crossSessionInbound" to "accept".

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_harbor_kite_mode_emit Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.224: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.224. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_harbor_kite_mode_emit, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_harbor_kite_mode_emit, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_harbor_kite_mode_emit, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_harbor_kite_mode_emit, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's release notes agreeAdded crossSessionInbound and dialogExpiry settings: cross-session messages sent to a session running with bypassed permissions are held for…
The name it cites is new in this buildNew in this build: tengu_harbor_kite_mode_emit

See this entry in the whole of v2.1.224 →

Feedback