Terminals, networking, and maintenance¶
Find the target environment in the list before opening its terminal, network settings, or deletion action. Verify the name before making changes.
Open the web terminal¶
Select the terminal action and wait until it shows a connected state before running commands. The terminal lets you inspect and operate that environment. A connected terminal proves the terminal channel is established; still validate execution through an agent task.
Change network access¶
Open network configuration. Existing settings such as name, compute specification, or disk may be read-only. Maintain the network-enabled tool list and domain allowlist as needed.
Identify the tool the task uses, such as pip for dependencies or git for a repository.
Enable network access for that tool.
Add necessary destinations as
domain:port, using service addresses approved for the task.Save and reopen settings to verify them.
Retry a small request to the target service and inspect the result.
Both the tool and destination must be allowed. Enabling only one can leave access blocked. Authentication errors also require valid target-service credentials; changing timeouts does not resolve them.
Delete an environment¶
Use the environment’s menu when it is no longer needed. Confirm its name and dependent tasks, and save files you need to retain elsewhere before deletion. Afterward, inspect the list and update any usage that still points to the removed environment.