Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial

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

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaRemote Controlwhat it touches
KindInternal Changesin v2.1.280,
Group of 2 Under the hood No documentation found

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

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