{"version":"2.1.299","anchor":"windows-sandbox-telemetry-steps-and-a-new-error","canonical_anchor":"windows-sandbox-telemetry-steps-and-a-new-error","heading":"Windows sandbox tracks four more setup steps and adds a new error","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/windows-sandbox-telemetry-steps-and-a-new-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Windows sandbox tracks four more setup steps and adds a new error\n\nThe Windows sandbox now records four more setup steps and has a new error for when its protection is not renewed\n\n**What**\n\nOn Windows, Claude Code can run commands inside a sandbox, which is a walled-off area that limits what those commands can reach on your computer. Claude Code now records four more steps of setting up that sandbox:\n\n- `exe_grant`\n\n- `git_identity`\n\n- `native_denies`\n\n- `parent_folder_grant`\n\nThere is also a new error, `SandboxProtectionNotRenewedError`, whose name points to the sandbox's protection not being renewed.\n\n**Why**\n\nThe Windows sandbox is still being built out, and these additions are part of that work. If you see `SandboxProtectionNotRenewedError` on Windows, it comes from the sandbox.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}