Tools now say whether they can run on a remote device; Bash says yes but nothing ships.
Remote-execution descriptors exist and Bash declares support, but the schema extension returns an empty object.
What's wrong with this entry?
Every tool now carries a remote-execution descriptor, defaulting to unsupported. Bash declares support and names three inputs it refuses when running remotely: dangerouslyDisableSandbox, run_in_background and _simulatedSedEdit. No user-facing flag turns any of this on, and the schema extension Bash spreads in returns an empty object, so no new options actually ship.
- The descriptor is stripped out before tools are advertised to MCP clients.
- Separately, IDE diff tabs are suppressed for tool calls marked as running for remote execution.
remoteExecution: { supported: !0, refusedInputFields: DRi }
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.
-
v2.1.246
Read, Write and Edit now declare remote execution support
Both mention execution
-
v2.1.246
Edit and Write check admission before writing on remote-driven calls
Both mention execution
-
v2.1.246
Remote-driven file reads get their own admission and re-verification path
Both mention execution