Repository navigation
docs: Link to current hosted-agent egress ranges - #924
Conversation
Replace the static networking allowlist with the Admin Panel and Warp Factories web app settings destinations. Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
warp-agent-staging
Bot
added
factory:docs-factory
Add a firewall-policy example and apply the requested team networking wording. Co-Authored-By: Oz <oz-agent@warp.dev>
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![warp-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR replaces the hardcoded Warp-hosted agent egress CIDR list with links to the current in-product networking settings. The change keeps the default-egress and allowlisting context on the hosting page, and I did not find blocking correctness, security, or spec-alignment issues.
Concerns
- One wording suggestion: keep the traffic scope explicitly tied to Warp-hosted agents so readers do not apply hosted egress ranges to local or self-hosted agents.
Verdict
Found: 0 critical, 0 important, 1 suggestions
Approve with nits
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| * `44.253.165.189/32` | ||
| * `16.145.188.113/32` | ||
| * `16.145.133.251/32` | ||
| Warp-hosted agents have network egress enabled by default. If you need to allowlist traffic from Warp agents, such as in a firewall policy, get Warp's IP address ranges from the "Warp-hosted agent networking" settings for your team. Find it on your team's **Platform** page in the [Admin Panel](https://app.warp.dev/admin/) or on <a href={`${VARS.FACTORY_WEB_APP_URL}/settings`}>User settings in the {VARS.FACTORY_WEB_APP}</a>. |
There was a problem hiding this comment.
💡 [SUGGESTION] Keep the traffic scope tied to Warp-hosted agents; “Warp agents” could be read as including local or self-hosted agents, whose egress does not use these hosted ranges.
| Warp-hosted agents have network egress enabled by default. If you need to allowlist traffic from Warp agents, such as in a firewall policy, get Warp's IP address ranges from the "Warp-hosted agent networking" settings for your team. Find it on your team's **Platform** page in the [Admin Panel](https://app.warp.dev/admin/) or on <a href={`${VARS.FACTORY_WEB_APP_URL}/settings`}>User settings in the {VARS.FACTORY_WEB_APP}</a>. | |
| Warp-hosted agents have network egress enabled by default. If you need to allowlist traffic from Warp-hosted agents, such as in a firewall policy, get the IP address ranges from the "Warp-hosted agent networking" settings for your team. Find it on your team's **Platform** page in the [Admin Panel](https://app.warp.dev/admin/) or on <a href={`${VARS.FACTORY_WEB_APP_URL}/settings`}>User settings in the {VARS.FACTORY_WEB_APP}</a>. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This branch was successfully deployed
1 participant
Summary
Replace the hardcoded egress CIDRs with the current in-product ranges in the Admin Panel and Warp Factories web app. Keep the default-egress and allowlisting context on the existing hosting page; the two security pages contain no duplicate list and remain unchanged.
This is a factual/link correction, so no content design plan is required. The deletion-only pass retained only the context needed to find and allowlist the ranges.
Source evidence
Verified against
warpdotdev/warp-server@720075c9d97dd48b51d9768b7b649db881ecc2cc:/settingsrenders User settings and the networking section. This is not per-factory Settings (/:factoryId/settings). Both surfaces fetch/api/v1/networking/egress-ranges.Verification
npm run typecheck,npm run test:heading-vars,npm run build,npm run test:heading-tocs, andnpm run test:homepage-json-ld.feature-doc), changed-file UI-reference check, andgit diff --check.trunk checkandtrunk fmt(Trunk is not installed).Unverified claims
No unresolved source claims. Production availability is confirmed by the requester; authenticated production UI was not exercised. No VERIFY markers added.
Documentation risk
Risk: engineering-review-required
Rationale: Replaces static networking data with source-verified product UI destinations.
Source files consulted: warp-server/client/src/components/admin/team/platform/HostedAgentEgressCIDRs.tsx, warp-server/client/packages/factory/src/pages/UserSettings/HostedAgentNetworking.tsx (source revision and mounting routes above)
Requested engineering reviewers: bnavetta
Engineering review status: pending
Docs override: none
Co-Authored-By: Oz oz-agent@warp.dev
Computer-use screenshots
Networking section with full paragraph, hovering "User settings in the Warp Factories web app" link showing https://platform.warp.dev/settings in status bar