Agent Network

Agent sandboxes run commands and work with files for Sentra. Their outbound network settings control which websites and APIs those commands can reach. Organization admins manage these settings in Agent → Settings → Network on web and desktop.

Changes apply to all agent sandboxes in your organization. Browser access and connected integrations have separate controls, and public inbound access to sandboxes stays disabled.

Choose an access mode

Restricted mode includes pypi.org, files.pythonhosted.org, and registry.npmjs.org. These remain available when the custom domain list is empty.

Only users with an active organization admin role can change sandbox network access. Managers and other members should ask an organization admin. Sentra can explain the settings in chat, but it cannot change them for you.

You can ask Sentra whether your organization uses restricted or allow-all access and whether sandbox terminations are pending. This lookup reads the saved configuration; it does not verify that a particular sandbox can reach a destination.

Add an approved domain

For example, to let a sandbox call the Stripe API while keeping access restricted:

1. Open Agent → Settings → Network and keep Allow all outbound internet access off.
2. Select Add domain.
3. Enter api.stripe.com in Domain, and optionally enter Stripe API in Name.
4. Read the risk notice, then select I understand, allow it.

Enter a hostname, without https://, a path, or a port. A rule allows access across that hostname, not just to one page. Use *.example.com to allow subdomains of a specific domain. Broad wildcards such as *, *.com, *.co.uk, and *.github.io are not accepted. IP addresses and certain shared hosting or data collection domains also cannot be added. Internationalized domain names must use their ASCII punycode form.

Only approve destinations your organization trusts. An approved destination can receive data from a sandbox; allowing it does not grant permission to share private data or provide credentials for its API.

Admins and Sentra operators use the same saved domain list, so entries added by an operator also appear here.

Remove a domain

Turn off allow-all before editing the saved domain list. Select the trash icon beside the domain, then confirm Remove domain. This removes the saved entry and attempts to update running sandboxes. It does not delete workspace files.

Removing one entry does not block a destination that another rule still permits, such as a wildcard, or that allow-all permits. Existing sandboxes and connections can also retain access, as described below.

Allow all outbound internet access

1. Turn on Allow all outbound internet access.
2. Read the risk notice and select the acknowledgement checkbox.
3. Confirm Enable access.

Allow-all opens outbound access to any website or API, including destinations that cannot be added in restricted mode. External content or malicious instructions can cause unintended data sharing. Public inbound access stays disabled.

Your approved domains remain saved. To return to restricted access, turn the switch off and confirm Restore restrictions. This stops existing sandboxes, interrupts active commands, and deletes unpublished workspace files. Already published artifacts remain available.

If Sentra asks you to update before reviewing the risk notice, update the desktop app or use the current web app.

When changes take effect

Domain changes and enabling allow-all are saved first, then applied to running sandboxes on a best-effort basis. Paused sandboxes stay asleep until used. Each tool operation reconnects and retries the current policy; failed or overlapping updates can leave old access and existing connections in place.

Turning off allow-all saves restricted mode and terminates existing sandboxes, including paused ones. The next operation uses a fresh restricted workspace. If a termination cannot be confirmed, the dashboard keeps a warning after a page refresh and offers Retry termination. Tools cannot reuse a workspace awaiting termination. Retry affects only those unfinished terminations; it does not stop new workspaces.

Do not treat revocation as complete while termination remains pending. There is no guaranteed completion deadline during a provider outage. After a request timeout, reload the page to check the saved setting and pending count. A connection failure alone does not prove that the allowlist blocked a domain; the destination may be unavailable or require separate authentication.