Every Code Cloud environment has its own internet policy. By default, a task can reach a built-in list of package registries and operating-system mirrors, plus any domain you add. You can narrow that to your own list, open it to everything, or switch the internet off.
Risks of agent internet access
The more a task can reach, the more it is exposed to prompt injection, leaking code or secrets, malware or vulnerable dependencies, and content under restrictive licenses. Allow only the domains the work needs, and read the output and work log.
Prompt injection happens when the agent follows instructions hidden in something it fetched, such as an issue that tells it to send a commit to an outside server. Point cloud tasks only at sources you trust.
Set internet access for an environment
Open Settings > Coding > Code Cloud, choose an environment, and find the Allow ZeroTwo to access the internet switch. Turning it off blocks all outbound traffic, including to hosts that your secrets are tied to. With it on, Allow domains picks the policy:
- Package managers is the default. It allows common registries and mirrors for npm, PyPI, Rust, Go, Maven, Gradle, Debian and Ubuntu, plus GitHub release hosts.
- Custom domains only allows just the domains you list.
- All (unrestricted) removes the limit.
Additional allowed domains
With Package managers or Custom domains only, add extra destinations under Additional allowed domains. Each entry is a hostname such as api.example.com, a wildcard such as *.example.com, an IP address or an IPv4 CIDR range. Leave out the scheme, path and port. Hostname rules cover HTTP and HTTPS traffic only; other protocols need an IP or CIDR entry.
An environment holds at most 100 distinct domains, counting the domains attached to its secrets.
Domains the agent suggests
During setup, ZeroTwo may propose domains the project needs. A review card, ZeroTwo suggests allowing these domains, lets you accept or dismiss them. Nothing is allowed until you accept.
Setup versus tasks
While a machine is being prepared, to clone repositories and run the install script, the policy also lets GitHub hosts through. A running task is held to the policy you chose, plus the destinations of the secrets you have supplied values for. There is no setting that limits outbound requests by HTTP method.