{"version":"2.1.305","anchor":"windows-sandbox-loopback-mode-must-match-what-was-verified","canonical_anchor":"windows-sandbox-loopback-mode-must-match-what-was-verified","heading":"Windows sandbox reports an error when the local network setting doesn't match","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/windows-sandbox-loopback-mode-must-match-what-was-verified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Windows sandbox reports an error when the local network setting doesn't match\n\nOn Windows, Claude Code has a new sandbox error for when `network.allowLocalBinding` disagrees with the loopback mode set up at the start\n\n**Unclear.** It is not clear when Claude Code actually shows this error to a user.\n\n**What**\n\nThe sandbox is the walled-off space Claude Code can run commands in, which limits what those commands can reach. Loopback means network connections a program makes to your own computer, such as a local development server. The `network.allowLocalBinding` setting asks for that kind of connection to be allowed.\n\nOn Windows, the sandbox checks its loopback mode once, when it starts up. Claude Code now has an error message for the case where `network.allowLocalBinding` asks for a different mode than the one that was checked. The message says:\n\n- The Windows loopback mode is fixed by the install.\n\n- It cannot change for one command or through `updateConfig()`.\n\n- To change it, reset the sandbox and start it up again (`reset()` then `initialize()`).\n\n**Why**\n\nOn Windows, the loopback mode cannot be switched on the fly. Changing `network.allowLocalBinding` partway through will hit an error instead of quietly taking effect.\n\n- Area: Sandbox\n- Names: `network.allowLocalBinding`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}