{"version":"2.1.305","anchor":"cloud-session-shell-routing-gated-by-tengu-cloud-session-she","canonical_anchor":"cloud-session-shell-routing-gated-by-tengu-cloud-session-she","heading":"Groundwork for running your own shell commands in cloud sessions, off by default","tier":"soon","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/cloud-session-shell-routing-gated-by-tengu-cloud-session-she","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Groundwork for running your own shell commands in cloud sessions, off by default\n\nClaude Code can now queue and run shell commands sent by the client in headless and SDK sessions, behind a remote switch that defaults to off\n\n**What**\n\nIn headless sessions (run without the interactive screen) and SDK sessions (driven by another program through a software toolkit), Claude Code has a new way to take shell commands sent from the client side, queue them and run them. It only exists over one particular kind of connection.\n\nWhether it is used is decided by a server-controlled switch, tengu_cloud_session_shell, which is off unless it is switched on remotely. Commands still waiting when the session ends or is stopped are dropped.\n\n**Why**\n\nThis is groundwork for letting you run your own shell commands in cloud sessions. It does nothing unless the switch is turned on remotely.\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: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}