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.280 ·

New sessionRecord capability flag

Remote session negotiation gains a new sessionRecord capability flag, off by default

Group of 2 Nothing to try yet No documentation found Internal Changes
JSON All of v2.1.280
Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
Internal ChangesKind: in v2.1.280,
What probably matters to youSection of the release

Unclear What sessionRecord actually does for the user (e.g. recording session activity) is not stated, only that it gates behavior.

What

The capability map used in remote/session negotiation gains a new sessionRecord entry, alongside existing entries like controlChannel, modelCatalog, setPermissionMode, fanout, presence, catchupReplay, bashExec, and fileRead. It defaults to false.

The flag is read in two places: an origin/mode tracking effect and an internal remote-transport check, and both reads are further gated by a call to vs().

Why

This lets Claude Code check whether a remote session supports recording before turning related behavior on. Because the flag defaults to off, it has no effect on existing sessions until it is explicitly enabled.

Read from
Names in the bundlesessionRecord
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 sessionRecord actually does for the user (e.g. recording session activity) is not stated, only that it gates behavior.

See this entry in the whole of v2.1.280 →

Feedback