{"version":"2.1.305","anchor":"sandbox-refuses-commands-after-local-binding-setting-changes","canonical_anchor":"sandbox-refuses-commands-after-local-binding-setting-changes","heading":"Windows sandbox asks for a restart after the local-binding setting changes","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/sandbox-refuses-commands-after-local-binding-setting-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Windows sandbox asks for a restart after the local-binding setting changes\n\nOn Windows, if `sandbox.network.allowLocalBinding` changed since the session started, sandboxed commands are refused with a message to restart Claude Code\n\n**What**\n\nThe sandbox is a restricted area that limits what commands run by Claude Code can reach. `sandbox.network.allowLocalBinding` controls whether sandboxed commands may listen on local network addresses.\n\nOn Windows, if the sandbox was set up again with the other value of `sandbox.network.allowLocalBinding` after your session started, every sandboxed command is now refused. A new error (sandbox exit code 19, `wfp_loopback_mismatch`) tells you to restart Claude Code.\n\n**Why**\n\nOn Windows, changing this setting in the middle of a session now produces a clear instruction instead of a puzzling sandbox failure. Restart Claude Code after changing it.\n\n- Area: Sandbox\n- Names: `sandbox.network.allowLocalBinding`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}