Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.239 Home All releases olderv2.1.238 v2.1.240newer
Claude Code v2.1.239

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

Not switched on
Useful1 Signal5
Remote Execution

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

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

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: on

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

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.239 →