{"version":"2.1.227","anchor":"cloud-sessions-can-run-shell-commands-on-your-own-machine","canonical_anchor":"cloud-sessions-can-run-shell-commands-on-your-own-machine","heading":"Cloud sessions can run shell commands on your own machine","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/cloud-sessions-can-run-shell-commands-on-your-own-machine","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Cloud sessions can run shell commands on your own machine\n\nA cloud session can run shell commands on your own machine, off unless a server flag enables it.\n\n**What**\n\nA new tool called `device_bash` lets a session running in the cloud execute a shell command on the machine where Claude Code is running, inside its OS sandbox, and return the output. It takes `command` plus an optional `timeout_ms`. It is off unless the remote-config flag `tengu_violin_wood` turns on the device bridge, and it still refuses without a server-asserted session and a bound device id.\n\n**Details**\n\n- registered alongside the existing device-info probe on the same bridge; the bridge itself starts only behind an async remote-config check that falls back to off on error\n- the tool description tells the model explicitly that this is the local device, not the cloud container\n- a per-device-connection concurrency cap limits how many commands can run at once\n- commands run with sandboxing, protection against changing the working directory, and credential scrubbing of the environment\n\n**Evidence**\n\n`Run a shell command on the user's local machine (the device running Claude Code), inside Claude Code's OS sandbox.`\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.227; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Names: `device_bash`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}