Environment "Network access: Full" setting not applied to session containers — outbound HTTPS still blocked (403 at gateway)

Status Closed — not planned
Reported on v2.1.272
Maintainer reply None cached
Activity 1 comment · opened Sep 15, 2026 · closed Sep 20, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Environment network access set to Full, but outbound HTTPS is still blocked with 403 at the gateway for non-allowlisted hosts.

What Should Happen?

Summary

Setting an environment's Network access to Full in the claude.ai environment settings does not appear to propagate to the actual container/proxy gateway that enforces egress for sessions running in that environment. New sessions started well after the setting was changed still have outbound HTTPS blocked to arbitrary hosts.

Environment

  • Environment ID: env_017ZYVkKgEvUF2qiz6boWwXv
  • Environment name: "デフォルト" (Default)
  • Kind: anthropic_cloud
  • Network access setting: confirmed set to Full in the environment settings UI

Timeline

  1. ~2026-09-10: Network access for this environment changed to Full in settings (per notes from a prior session in this environment).
  2. A separate/earlier session's container (created 2026-09-11, reused since) still gets 403s on outbound HTTPS to non-allowlisted hosts.
  3. 2026-09-15: A brand-new session (session_019pNTfjQxktC8GnKyWcL7Zh) was started in the same environment, well after the setting change, to check whether a fresh container would pick up the Full policy.
  4. The new session still gets the same 403s.

Steps to reproduce

  1. In an anthropic_cloud environment, set Network access to Full.
  2. Start a new Claude Code on the web/cloud session in that environment.
  3. From the session, run:

Error Messages/Logs

Steps to Reproduce

  1. In an anthropic_cloud environment, set Network access to Full.
  2. Start a new Claude Code on the web/cloud session in that environment.
  3. Run: curl -sS -o /dev/null -w "%{http_code}\n" --max-time 12 https://commons.wikimedia.org
  4. Run: curl -sS "$HTTPS_PROXY/__agentproxy/status"

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.272

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

Running in a claude.ai/code cloud session (remote container), not a local terminal.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗