{"version":"2.1.305","anchor":"remote-sessions-bash-commands-now-run-locally-when-the","canonical_anchor":"remote-sessions-bash-commands-now-run-locally-when-the","heading":"'!' shell commands can now run in remote sessions that support them","tier":"use","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/remote-sessions-bash-commands-now-run-locally-when-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### '!' shell commands can now run in remote sessions that support them\n\nIn a remote session that supports it, a '!' shell command can now run, with limits on output and a 10 minute timeout\n\n**Unclear.** It is not clear which kinds of remote session support running '!' commands.\n\n**What**\n\nTyping `!` before a line in Claude Code runs it directly as a shell command. In a remote session, meaning one running on another machine, this always used to be refused with a message that '!' commands aren't available in cloud sessions yet.\n\nWhen the remote session supports running shell commands, a `!` command can now run. The command runs under `\/bin\/sh`, or PowerShell on Windows, and its output is capped. The result notes when the command ended early:\n\n- `[interrupted]` when it was stopped\n\n- `[timed out after 10 minutes]` when it ran too long\n\n- `[stopped: the command printed more than 100 MB]` when it printed too much\n\nWhen the remote session does not support it, the refusal now reads \"'!' commands aren't available in a session on another machine\". Cloud sessions keep the existing message. A command sent for a different folder than the one the session is now in is not run, and you are told to ask Claude to run it instead.\n\n**Why**\n\nShell `!` commands may start working in some remote or attached sessions where they were always refused before.\n\n- Area: Sessions\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}