Cloud environment network settings
Open “Agent execution target” → “New environment” to edit internet access settings.
The form currently supports editing a draft. “Create environment” is disabled. Selections are neither saved to the server nor applied to an execution environment. Closing the modal discards the draft.
A network policy specifies which internet destinations an environment can access. This is separate from repository permissions and settings for who can use the environment.
The form offers the access levels below. These descriptions explain what each option represents. Selecting an option in the current form does not change which connections are allowed or blocked.
| Option | Setting |
|---|---|
| None | Blocks internet access. |
| Trusted (recommended) | Allows downloading packages from verified sources. This is the default selection. |
| Full | Internet access without restrictions on destination domains. |
| Custom | Specifies destinations using a list of domains you enter. |
Selecting “Custom” shows “Allowed domains”. Enter one domain per line. Switching to another access level preserves your input while the modal remains open.
The list of trusted sources, handling of subdomains and wildcards, and runtime behavior for an empty custom list have not been determined. These network controls are not yet connected to the form.
Network secrets are intended to enable authenticated requests to external APIs without exposing secret values to sessions. “Values cannot be viewed after saving” describes the intended behavior for saved values.
Saving, injecting secrets into requests, and restricting access to saved values are not yet connected. “Manage” edits a draft within the modal. Reopening the editor displays the draft; closing the modal discards it. This feature cannot yet be used to store real API keys or tokens.
Destination domain matching, authentication header formats, updating and deleting values, and interaction with access levels have not been determined. Editing a network secret draft does not change allowed destinations or running sessions.
Enter environment variables as NAME=value, one per line. Wrap multiline values in quotes.
NODE_ENV=production
GIT_AUTHOR_NAME=Your Name
# Multiline values - wrap in quotes
CONFIG="key1=val1
key2=val2"Only enter settings that can be shown to users of this environment. Do not include secrets, API keys, passwords, or other credentials.
The current form only edits a text draft. It does not parse .env content, configure an execution environment, or share values with other users. “Apply” updates the draft within the modal. Closing the modal discards it.