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
HomeReleasesv2.1.281entry #639

Claude Code v2.1.281 ·

Remote session requests carry a modeStamp, and serve-only clients stay silent on unsupported requests

Permission-request metadata and served remote channel requests now include a modeStamp, and control-only clients no longer answer unsupported requests with errors

Group of 2 Under the hood Internal Changes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release

Unclear The finding does not say what modeStamp records or what a reader would use it for.

What

Work on remote sessions, where Claude Code is driven from another machine or program, added a modeStamp marker and changed how some clients reply.

  • Metadata attached to permission requests from hook callbacks now records modeStamp: "present" when remote_tool_gate is caller_reauthored, otherwise "other". It is recorded even without device attestation; before, the metadata was empty in that case.
  • Requests served over a remote session channel now carry modeStamp.
  • Clients configured as controlOnly now leave requests they do not support unanswered. Before, they always replied with an 'Unsupported control request subtype' error.

Why

For people hosting remote sessions, a serve-only client no longer sends error replies to requests it was never meant to handle. The modeStamp field mainly supports reporting for the remote-tools work.

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 doubtThe finding does not say what `modeStamp` records or what a reader would use it for.

See this entry in the whole of v2.1.281 →

Feedback