docs/enterprise/outbound-access.json. CI guards that file with node scripts/check-outbound-access.mjs; this page is the published human-readable summary.
Minimum hosted desktop allowlist
For a practical OpenWork Cloud desktop install, allow TCP 443 to these hosts:- GitHub release downloads redirect away from
github.com. Allowrelease-assets.githubusercontent.com, which is the current verified GitHub release-asset host, andobjects.githubusercontent.com, which is kept for older clients and rollback paths. registry.npmjs.orgis used when packaged desktop builds startnpx -y openwork-ui-mcp. If it is blocked, the desktop can still open, but UI-control MCP is unavailable.models.openworklabs.comis the default OpenCode model catalog. SetOPENCODE_MODELS_URLto an approved internal mirror if the public catalog is blocked.
Desktop and local runtime destinations
code.claude.com and schemas.agentskills.io appear in source or schema metadata. They are findable in the manifest, but OpenWork does not fetch them for normal runtime behavior.
Den runtime destinations
Approve Den separately from desktop clients. A self-hosted Den behind VPN or inside Kubernetes uses the server network, not the user’s laptop network.
Google Workspace hostnames in the manifest are
accounts.google.com, oauth2.googleapis.com, www.googleapis.com, gmail.googleapis.com, and chat.googleapis.com.
Deployment and image-pull destinations
For fully isolated deployments, also mirror installer artifacts, npm packages used by
npx, and the model catalog. See Air-gapped deployment and Installer delivery.
Opt-in provider and connection hostnames
These hosts are only needed when the corresponding feature, provider, connection, or import path is enabled:
The JSON manifest remains the ownership point for exact host metadata, requirement level, override name, and blocked effect. Use this page for review conversations and the JSON file for automation.