- Symptom
- 400 error on session create or update when a web tool's allowed_domains has an entry not within allowed_hostsweb_fetch returns url_not_allowed error resultweb_search omits results, or both tools return nothing when allowed_hosts is empty
- Cause
- Since October 7, 2026, a cloud environment with limited networking applies allowed_hosts to web_search and web_fetch too. An allowed_hosts entry matches one exact host unless it starts with *., so docs.example.com is not within ["example.com"]. allow_package_managers and allow_mcp_servers add no hosts for these tools.
- Fix
- Add each needed host to allowed_hosts, using a *. wildcard entry for subdomains, or remove the entry from the web tool's allowed_domains. Note that adding a host also opens it to the sandbox.
- Apply
allowed_hosts: ["example.com", "*.example.com"]- Affected
- Claude Managed Agents cloud environments with limited networking, from 2026-10-07
- Sources
Last verified 2026-10-24 · Confirmed by 0 builders