{"version":"2.1.300","anchor":"sandbox-vm-stay-reason-added-to-startup-state","canonical_anchor":"sandbox-vm-stay-reason-added-to-startup-state","heading":"Startup now carries a reason for the sandbox virtual machine to stay","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/sandbox-vm-stay-reason-added-to-startup-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Startup now carries a reason for the sandbox virtual machine to stay\n\nClaude Code's startup state now passes along a reason for keeping a sandbox virtual machine running, with no visible effect yet\n\n**Unclear.** What sets this reason and what it changes for a session is not stated.\n\n**What**\n\nClaude Code's startup now passes a new value into the interactive session: a reason for a sandbox virtual machine to stay running. A sandbox is a walled-off space where commands run apart from the rest of your computer.\n\n**Why**\n\nThis suggests work on a sandbox feature that runs in a virtual machine. Nothing visible changes yet.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}