claude-code-weblisted

# Claude Code Web How Fabrizio wants a session to behave when it runs in **Claude Code Web** — the managed, cloud-hosted environment at `claude.ai/code`, rather than the local CLI. The sandbox is real: outbound traffic is proxied, some tools and hosts are blocked, the container is ephemeral, and the session is scoped to specific repositories. Work *with* those constraints rather than rediscovering them each time. Apply these whenever you're in a web session, whether or not a named command was invoked. They are personal defaults that **complement repo/context rules, never supersede them** — check the repo's own `CLAUDE.md`/`CONTRIBUTING.md` first, and where it differs, follow the repo. ## These constraints change — verify, and defer to the environment's own description The sandbox's limits are set by Anthropic and by the **network policy chosen for the environment**, so they vary between environments and change over time. Treat everything here as *last-known behaviour, not a permanent guarantee*: before spending effort working around a constraint, probe whether it still holds (the references give reproducers), and don't assume a documented block is universal — a different environment's policy may not have it. The harness's own description of the environment in the **system prompt** (the "remote execution environment" / network-policy section it gives the session) is authoritative and **supersedes this plugin**. Where the two conflict, follow the system prompt and open a P