{"version":"2.1.311","anchor":"windows-sandbox-localhost-guidance-reworded-for-managed-sett","canonical_anchor":"windows-sandbox-localhost-guidance-reworded-for-managed-sett","heading":"Clearer Windows sandbox advice about allowing local servers","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/windows-sandbox-localhost-guidance-reworded-for-managed-sett","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Clearer Windows sandbox advice about allowing local servers\n\nOn Windows, Claude now tells you that `allowLocalBinding` must go in managed settings your administrator controls when sandbox settings are locked\n\n**What**\n\nThe sandbox is the protective boundary that limits what commands Claude runs can reach. Its instructions to Claude on Windows now give more precise advice about the `allowLocalBinding` setting, which lets programs listen on a local network port.\n\n- When sandbox settings are locked by managed settings, Claude is told that `allowLocalBinding` goes in \"the managed settings, which their administrator controls\". Managed settings are settings an organisation applies centrally.\n\n- Otherwise, Claude is told that a project's own settings do not count for this on Windows.\n\nBefore this change, the advice named only the managed settings or a settings file.\n\n**Why**\n\nWhen Claude explains how to let a local server run inside the sandbox on Windows, it now points you to the right place. If your settings are locked, you know to ask your administrator instead of editing a file that will not help.\n\n- Area: Sandbox\n- Names: `allowLocalBinding`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}