{"version":"2.1.305","anchor":"unattended-serving-sandbox-check-reports-a-reason-and-logs-o","canonical_anchor":"unattended-serving-sandbox-check-reports-a-reason-and-logs-o","heading":"Sandbox check for unattended serving now logs why it failed","tier":"notice","area":"Unattended Serving","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/unattended-serving-sandbox-check-reports-a-reason-and-logs-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Sandbox check for unattended serving now logs why it failed\n\nIf the command sandbox can't be checked for unattended serving, Claude Code now logs a warning and reports sandbox_failed_to_start\n\n**What**\n\nBefore serving unattended, Claude Code checks whether commands are confined by the sandbox, the restricted area that limits what commands can reach. If the sandbox cannot be asked, that check used to fail silently. It now logs the warning \"unattended-serving consent: command sandbox could not be asked, taken as not confining\" and reports the reason `sandbox_failed_to_start`. Commands are still treated as not confined.\n\n**Why**\n\nWhen unattended serving is refused because the sandbox did not start, the log now says so, which makes the cause easier to find.\n\n- Area: Unattended Serving\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}