{"version":"2.1.307","anchor":"sandbox-check-command-shows-a-progress-note-and-a-deadline","canonical_anchor":"sandbox-check-command-shows-a-progress-note-and-a-deadline","heading":"Sandbox check now shows a note and stops waiting outside a terminal","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/sandbox-check-command-shows-a-progress-note-and-a-deadline","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Sandbox check now shows a note and stops waiting outside a terminal\n\nThe sandbox setup check prints a note in a terminal, and when run without one it now gives up about 150 seconds after start\n\n**What**\n\nA sandbox is the restricted space Claude Code runs commands in. Before it is used, Claude Code checks that it has been set up. That check now behaves differently depending on where Claude Code is running:\n\n- In an interactive terminal window: it prints a note to error output and waits with no time limit.\n\n- Anywhere else, such as a script or an automated job: it has a deadline of about 150 seconds after Claude Code started.\n\nBefore, there was no note and no deadline.\n\n**Why**\n\nRuns that nobody is watching can no longer hang forever on this check.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}