{"version":"2.1.305","anchor":"cloud-worker-bash-command-can-run-through-the-bash-tool-gat","canonical_anchor":"cloud-worker-bash-command-can-run-through-the-bash-tool-gat","heading":"Cloud sessions can run shell commands as a turn Claude sees","tier":"soon","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/cloud-worker-bash-command-can-run-through-the-bash-tool-gat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Cloud sessions can run shell commands as a turn Claude sees\n\nA second mode lets cloud workers run a requested shell command through Claude's Bash tool, so Claude sees it and the folder carries over\n\n**What**\n\nIn a cloud session, Claude Code runs on a remote machine called a worker. A shell command can be sent to that worker directly. Before, such a command always ran once in a plain shell, and Claude never saw it.\n\nA second mode now exists behind a server-side setting. In that mode the worker runs the command through the Bash tool, which is the tool Claude uses to run shell commands, as a turn of its own:\n\n- Claude sees the command and its output.\n\n- The working folder carries over to later commands.\n\n- Some commands are refused and appear as a \"Not run\" row.\n\nThe default behaviour has not changed.\n\n**Why**\n\nCloud sessions could run `!` commands the way the terminal app does, with Claude aware of what was run.\n\n- Flag `tengu_cloud_session_shell`: Not enough to say (read for one account on one subscription tier against v2.1.305; this account: no value returned, anonymous baseline: no value returned, compiled default: off) 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- Tier: Nothing to try yet\n- Useful: 5\/5\n- Signal: 5\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}