{"version":"2.1.265","anchor":"sandboxed-windows-exec-refusal-error-object-changed-shape","canonical_anchor":"sandboxed-windows-exec-refusal-error-object-changed-shape","heading":"sandboxed Windows exec refusal error object changed shape","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/sandboxed-windows-exec-refusal-error-object-changed-shape","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### sandboxed Windows exec refusal error object changed shape\n\nWindows sandbox command refusals now throw a different internal error object\n\n**Unclear.** What practical difference the new error object shape makes, if any, is not stated.\n\n**What**\n\nWhen Claude Code's sandbox (a restricted execution environment) refuses to run a command on Windows because of policy, it now throws a `cre` error built from the command string, instead of the previous `Vte` error object.\n\n**Why**\n\nThis is an internal implementation detail of how the refusal is represented in code. It doesn't change what happens visibly when a Windows sandbox policy blocks a command, but code that inspected the old error shape would need to account for the new one.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}