Skip to main content

Security & network

Cloud agents run in isolated environments. This page covers the controls that keep those runs secure, the network access they require, and the domains your corporate firewall must allow.

Isolation

Each run executes in its own sandboxed environment with only the repositories, secrets, and permissions you grant. Runs don't share state with each other or with your local machine.

PropertyBehavior
FilesystemEphemeral — destroyed when the environment is cleaned up
Process spaceIsolated per run
SecretsInjected at runtime; not persisted in images
Git accessScoped to allowlisted repositories only
NetworkEgress controlled by org policy (deny by default)
Defense in depth

Isolation is one layer. Combine it with least-privilege repo access, secret injection (not prompts), and human review of PRs before merge.

Network egress

By default, restrict outbound network access to what the task needs. Allowlist specific domains (package registries, your APIs) rather than permitting unrestricted egress.

SettingRecommendation
EgressDeny by default; allowlist required domains
SecretsInject at runtime; never store in prompts or code
ReposGrant only those the automation requires
Private APIsAllowlist host + require mTLS or token auth at the API layer

Common allowlist entries

Add these domains when cloud agents need to install dependencies and reach 4RGE services:

CategoryDomainPurpose
4RGE — product4rged.aiMarketing and product surfaces
4RGE — authauth.4rged.aiSign-in and OAuth callbacks
4RGE — dashboarddashboard.4rged.aiOrg admin (transition host)
4RGE — agentsagents.4rged.aiAgents workspace (transition host)
4RGE — agents APIagents-api.4rged.aiRun orchestration, GitHub webhooks
4RGE — platform APIapi.4rged.aiPolicy, provisioning, desktop API
4RGE — registryregistry.4rged.aiPlugin and catalog registry
4RGE — docsdocs.4rged.aiDocumentation
4RGE — downloadsdownloads.4rged.aiCLI and desktop installers
Supabase*.supabase.coAuthentication and platform data
npmregistry.npmjs.orgNode package installs
PyPIpypi.org, files.pythonhosted.orgPython package installs
GitHubgithub.com, api.github.comClone, PR, webhook delivery
Private registries

If you use a private npm, PyPI, or Docker registry, add those hostnames explicitly. Test with a smoke run that only runs npm ci or pip install before delegating larger tasks.

Corporate desktop and CLI allowlist

Users on locked-down networks need the same domains for the desktop app, CLI, and browser apps — not just cloud run sandboxes:

  1. Allow 4RGE service domains

    Permit HTTPS to *.4rged.ai and your Supabase project URL (*.supabase.co).

  2. Allow GitHub if using integrations

    Permit github.com and api.github.com for OAuth and the GitHub App.

  3. Configure proxy trust

    If traffic passes through an HTTPS proxy, ensure the proxy presents a trusted certificate chain to the desktop app and CLI.

  4. Verify from each surface

    Test sign-in (auth), start a local agent run (desktop), and start a cloud run (agents API) from the same network segment.

Access control

ControlSet byScope
Repository allowlistOrg adminWhich repos cloud agents can clone
Model allowlistOrg adminModel control
Budget policyOrg adminUsage
Contract / capacityPlatform operatorConsole · Contracts
Automation managementAgent manager roleCreate and enable automations

Durable job queue

Cloud execution uses a separate x4rge_agent_jobs queue decoupled from browser streams. Each run gets one job row with status queued, claimed, running, completed, failed, cancelled, or dead_letter. Workers claim jobs with time-bounded leases; max_attempts defaults to 3 before a job moves to dead_letter. This design lets agents-api scale workers independently of the Agents workspace UI and gives Sentinel visibility into backlog and retry state alongside run status.

Secrets handling

  1. Use org secrets, not prompts

    Configure API keys and tokens in environment settings. Never paste credentials into task descriptions — they may appear in logs or audit exports.

  2. Rotate on departure

    When a team member with secret access leaves, rotate affected keys and review recent audit events for cloud runs that used them.

  3. Keep secrets out of git

    Ensure .env, credential files, and key material are in .gitignore. Cloud agents respect the same ignore rules as local agents.

Security review checklist

Before enabling cloud agents for a production repository:

  • Repository access limited to required repos only
  • Egress allowlist includes registries and APIs the setup commands need
  • Secrets injected via platform — none in prompts or committed files
  • Budget policy set with headroom alerts
  • Automations start in draft and are manually verified before enabled
  • PRs from cloud agents require human review before merge
Behind a corporate firewall?

If your organization proxies or filters traffic, allowlist the 4RGE service domains listed above so the desktop app, CLI, and cloud runs can authenticate and operate. Share this page with your network admin.

Agent security

Approvals, scoping, and org controls for all agent runs.

Setup

Configure environments without exposing secrets.

Troubleshooting

Diagnose sign-in, port, and integration issues on locked-down networks.