What
Sandbox domain and injectHosts entries are now normalized and checked for bracketed IPv6 spellings, ports and canonical form. Entries with unreliable spellings still work, but enforcement becomes conservative: it denies at least what any readable interpretation denies, and allow rules never widen.
Details
- Problem entries are collected and surfaced as doctor issues rather than failing startup.
Evidence
Sandbox network domain entries have unreliable spellings
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundledomaininjectHosts
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up domain, on Configure cloud environments.
Sessions in this environment can now reach `api.example.com`, any subdomain of `internal.example.com`, and `registry.example.com`, and no other domains through the session's network. [GitHub traffic](#github-proxy), [MCP connector traffic]…cloud-environments see the edit
Added since
A small documentation edit on Customize Claude Tag touched a line naming domain after this was published.
The Configure page also shows the channel's resolved access. Its **Tools and access** tab lists the channel's resolved connections and any allowed domains. Members can see those lists but not change them there. The same tab's **Plugins** c…claude-tag/admins/customize see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Customize Claude Tag touched a line naming domain after this was published.