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

Claude Code v2.1.239 ·

Remote tool execution is complete but hard-disabled in this build

Remote device execution is fully built but hard-disabled; no tool can be sent to a device.

Nothing to try yet In Development
JSON All of v2.1.239
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
Remote ExecutionArea: what it touches
In DevelopmentKind: in v2.1.239,
What probably matters to youSection of the release

The model-facing device field exists on remote-capable tools but its gate returns false unconditionally.

What

Tools can now declare that they support running on a remote device, and the Bash tool declares it along with a list of input fields it refuses in that mode. The model-facing half is an input field named device on remote-capable tools, added only when a gate passes. That gate is a function that returns false unconditionally in this build, so the field is stripped from every tool schema and no tool can be sent to a device.

Details
  • All other tools get a frozen default of unsupported.
  • A forRemoteExecution flag threads through the permission pipeline: it forces bypass-permissions and accept-edits off, skips sandbox auto-allow, skips sed simulation, skips IDE diff tabs, and makes the request classify as a remote-agent request.
  • Because the gate short-circuits, the server flag tengu_violin_wood behind it is never consulted; the field is deleted both from the API tool list and from the MCP server's tools/list.
  • A sibling stub also returns false and feeds a legacy Bash withholding switch and a device_bash_withheld telemetry field.
  • None of this existed in v2.1.238.
Evidence

refusedInputFields

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

Read from
Feature flag
tengu_violin_wood Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.239: off

Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_violin_wood, 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_violin_wood, 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 →

See this entry in the whole of v2.1.239 →

Feedback