Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.275 ·

Queued notifications now require a remote connection to deliver

Queued notification messages are relayed through Remote Control but get dropped with a warning if there's no remote transport to route them to

Group of 3 You'll notice Improvements
JSON All of v2.1.275
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
ImprovementsKind: in v2.1.275,
ImprovementsSection of the release

What

  • The Remote Control REPL bridge now relays queued notifications into the app during a bridge session, using the same handler as before.
  • An incoming queued_notification control message is now dropped (and not acknowledged) unless the session is using a remote transport, logging a warning and recording a new telemetry reason.
  • The warning text shown when a queued notification has nowhere to go was reworded from referencing "remote mode" to referencing a missing "ingress host".

Why

This ensures queued notifications are only delivered when there's an actual remote connection able to receive them, and makes the failure message clearer about why a notification was dropped.

See this entry in the whole of v2.1.275 →

Feedback