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

Claude Code v2.1.234 ·

Notices passed between sessions, shipped dark

One session could inject a coordination notice into another, but three separate gates keep it dark.

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.234
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
SessionsArea: what it touches
In DevelopmentKind: in v2.1.234,
What probably matters to youSection of the release

A session_notice inbound message needs a remote env var, tengu_polished_lagoon, and a helper compiled to return false.

What

A new inbound session_notice message would let one session inject a coordination notice into another as a turn element. Nothing can trigger it in this build: it needs the remote-session environment variable, the tengu_polished_lagoon flag (off unless the server says otherwise), and a helper compiled to always return false.

Details
  • Payloads are schema-validated for uuid, notice class and originating session id; oversize content is trimmed down to a byte budget with a visible truncation marker, and hooks get a pass at it.
  • It is dropped with a warning on any transport that is not the remote one, and only accepted while permission mode is auto; otherwise it is left for redelivery.
  • Redelivery is deduped through a new pending-delivery list in app state, and the ack is only sent once persistence is confirmed.
  • Telemetry ccr_session_notices records not_remote_transport, malformed_payload, flag_disabled, mode_not_auto_will_retry and queue_cap_will_retry.
Evidence

ccr_session_notices, [session-notices] session_notice on a non-RemoteIO transport \u2014 dropping without ack, \u2026[session_notice content truncated by the CLI:

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

Read from
Names in the bundletengu_polished_lagoon
What has happened since
Flag reading moved The flag server now returns on for tengu_polished_lagoon, 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_polished_lagoon, 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
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_polished_lagoon

See this entry in the whole of v2.1.234 →

Feedback