{"version":"2.1.285","anchor":"sandbox-network-allowlist-no-longer-hardcodes-package-regist","canonical_anchor":"sandbox-network-allowlist-no-longer-hardcodes-package-regist","heading":"Sandbox package registry defaults now come from a shared list","tier":"internal","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/sandbox-network-allowlist-no-longer-hardcodes-package-regist","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Sandbox package registry defaults now come from a shared list\n\nThe sandbox's default allowed package registries, such as registry.npmjs.org and pypi.org, now come from a shared list\n\n**Unclear.** It is not clear which hosts the shared list contains.\n\n**What**\n\nThe sandbox limits which websites commands run by Claude can reach. Its default allowance for package registries, such as `registry.npmjs.org`, `jsr.io`, `pypi.org` and `proxy.golang.org`, used to be written out in place. It now comes from a shared list.\n\n**Why**\n\nThe hosts allowed by default may differ from before. If a package install inside the sandbox starts failing to connect, check which registries are allowed.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}