← ClaudeAtlas

cloud-sessionslisted

Working preferences and hard constraints for Claude Code Web (the browser and cloud environment at claude.ai/code, as opposed to the local CLI). Consult this whenever a session runs in that environment and something behaves differently from local — outbound network going through the egress proxy, GitHub access, installing tools, adding or scoping repositories, setting environment variables or secrets, a plugin or a repo's adopted conventions not being loaded, or a command that can't run in the sandbox and should be delegated to CI. Always-on preferences; they complement a repo's own CLAUDE.md rather than overriding it.
flungo/claude-plugins · ★ 0 · DevOps & Infrastructure · score 58
Install: claude install-skill flungo/claude-plugins
# Claude Code Web How a session should 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 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. Everything here describes Claude Code Web as it behaves for **anyone**. What *one particular* environment has been configured with — the hosts its owner added to the allowlist, the environment variables it sets, its setup script — is deliberately **not** recorded here, because it differs per environment and per user. If a companion skill records that for the environment you're in, it is the place for those specifics; otherwise, treat the harness's system prompt as the only description of them. ## 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*: befor