{"version":"2.1.307","anchor":"sandbox-provisioning-waits-on-a-tty-with-a-notice-otherwise","canonical_anchor":"sandbox-provisioning-waits-on-a-tty-with-a-notice-otherwise","heading":"Sandbox setup no longer waits forever when nobody is watching","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/sandbox-provisioning-waits-on-a-tty-with-a-notice-otherwise","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Sandbox setup no longer waits forever when nobody is watching\n\nSandbox setup shows a start notice in a terminal, and when run without one it now gives up 150 seconds after Claude Code started\n\n**What**\n\nSetting up the sandbox, the protective boundary around commands Claude runs, behaves in one of two ways:\n\n- In a terminal: Claude Code prints a message saying setup has started, then waits as long as it takes.\n\n- Not in a terminal, such as in scripts: setup gets a deadline of 150 seconds after Claude Code started.\n\nBefore, setup had no deadline in either case.\n\n**Why**\n\nScripts and other runs with nobody at the keyboard no longer hang forever if sandbox setup stalls.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}