Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.265 ·

Sessions gain a control-only connection mode

Sessions can now connect in a controlOnly mode that subscribes to control messages without the full event stream

Group of 4 Under the hood No documentation found Internal Changes
JSON All of v2.1.265
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release

Unclear What effect controlOnly: true has on an opened session, or when it is set, is not described in the finding.

What

  • Sessions and their control/event channel gained a controlOnly mode, threaded through from session-open callers down to the low-level session-open call (defaulting to unset/false).
  • SessionsV2Client appends control_only=1 to the session events stream URL when configured with controlOnly, letting a connection subscribe to control messages only, without the full event stream.
  • When a session is opened via attach, the emitted "opened" payload conditionally includes controlOnly: true.

Why

This lets a client connect to a session just to receive control messages, without also receiving the full event stream, which is more efficient when only control signaling is needed.

Read from
Names in the bundlecontrolOnly
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat effect `controlOnly: true` has on an opened session, or when it is set, is not described in the finding.

See this entry in the whole of v2.1.265 →

Feedback