Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.274 ·

New sessionInboxPointers tracker for bridge/remote message delivery

A new sessionInboxPointers tracker records queued bridge messages, re-notifies unfetched attachments when idle, and taps into command lifecycle events.

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaRemote Controlwhat it touches
KindImprovementsin v2.1.274,
Group of 3 You'll notice

A new sessionInboxPointers tracker records queued bridge messages, re-notifies unfetched attachments when idle, and taps into command lifecycle events.

What

  • A new sessionInboxPointers tracker records queued messages: when a remote/bridge control message or a remote-origin user message is queued, it's registered via noteQueued with its origin, wake state, and id.
  • When the session goes idle, queued file/attachment ids that a remote bridge peer never fetched are now re-sent via renotifyUnfetched, both from the idle-nudge path and a new onIdleReported callback.
  • Session setup now also taps into command lifecycle events via this same tracker.

Why This makes message and attachment delivery to a remote/bridge peer (such as a companion device or connected session) more reliable, ensuring items that were queued but never picked up get another chance to be delivered instead of silently sitting unfetched.

Read from
Feature flag
tengu_bridge_inbox_pointer_boundary Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.274: on

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.274. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_bridge_inbox_pointer_boundary

See this entry in the whole of v2.1.274 →