docs(site): update network isolation to reflect AWF strict topology#1618
Merged
jamesadevine merged 1 commit intoJul 21, 2026
Merged
Conversation
- Replace stale 'Squid proxy and Docker containers' description with accurate rootless strict-topology description matching PR #1534 - Add note about --network-isolation flag and --topology-attach awmg-mcpg - Remove host.docker.internal from the Default Allowed Domains table (it is deliberately absent under strict topology; agent has no host route) - Update Default Allowed Domains intro to explain host.docker.internal omission - Remove 'MCP-specific' from the combined-hosts summary line Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jamesadevine
approved these changes
Jul 21, 2026
jamesadevine
marked this pull request as ready for review
July 21, 2026 19:22
jamesadevine
deleted the
docs/network-strict-topology-update-7d0263c5f7208a81
branch
July 21, 2026 19:22
github-actions Bot
added a commit
that referenced
this pull request
Jul 22, 2026
targets.mdx described AWF as 'Squid proxy + Docker'; audit.mdx labelled firewall logs as 'AWF Squid proxy logs' in two places. PR #1618 updated network.mdx to reflect the strict rootless topology but these two pages were not updated at the same time. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
network.mdxreference page still described AWF as using "Squid proxy and Docker containers" — the legacy architecture. PR feat(compile): adopt AWF strict network isolation #1534 (merged 2026-07-21) migrated to AWF strict rootless topology, but the human-facing docs weren't updated.host.docker.internalwas listed as an always-allowed domain, but under strict topology the agent has no route to the build-agent host and that entry is deliberately absent fromCORE_ALLOWED_HOSTS.Changes
site/src/content/docs/reference/network.mdx--network-isolationflag and--topology-attach awmg-mcpg(MCPG reaches agent via AWF's internal network; Detection runs without MCPG attachment).host.docker.internalrow from the Default Allowed Domains table.host.docker.internalis deliberately absent.Accuracy checks
--topology-attach awmg-mcpgverified againstrun_agent_stepinsrc/compile/agentic_pipeline.rs(lines 2775–2793).host.docker.internalabsence verified againstdocs/network.mdline 15: "deliberately not on this list".CORE_ALLOWED_HOSTSinsrc/allowed_hosts.rsconfirmed: nohost.docker.internalentry.Validation
cd site && npm run build:astro— 38 pages built, all internal links valid.Created by the docs-writer workflow.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
cdn.playwright.devSee Network Configuration for more information.