{"version":"2.1.239","anchor":"tools-can-declare-whether-they-run-remotely-bash-is-the-firs","canonical_anchor":"tools-can-declare-whether-they-run-remotely-bash-is-the-firs","heading":"Tools can declare whether they run remotely; Bash is the first, and it is scaffolding","tier":"soon","area":"Remote Execution","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/tools-can-declare-whether-they-run-remotely-bash-is-the-firs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Tools can declare whether they run remotely; Bash is the first, and it is scaffolding\n\nTools now say whether they can run on a remote device; Bash says yes but nothing ships.\n\n**What**\n\nEvery 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.\n\n**Details**\n\n- The descriptor is stripped out before tools are advertised to MCP clients.\n- Separately, IDE diff tabs are suppressed for tool calls marked as running for remote execution.\n\n**Evidence**\n\n`remoteExecution: { supported: !0, refusedInputFields: DRi }`\n\n- Area: Remote Execution\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}