Skip to content

docs(site): update network isolation to reflect AWF strict topology#1618

Merged
jamesadevine merged 1 commit into
mainfrom
docs/network-strict-topology-update-7d0263c5f7208a81
Jul 21, 2026
Merged

docs(site): update network isolation to reflect AWF strict topology#1618
jamesadevine merged 1 commit into
mainfrom
docs/network-strict-topology-update-7d0263c5f7208a81

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

  • The network.mdx reference 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.internal was 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 from CORE_ALLOWED_HOSTS.

Changes

  • site/src/content/docs/reference/network.mdx
    • Replaced stale "Squid proxy and Docker containers" intro with accurate rootless strict-topology description.
    • Added note about --network-isolation flag and --topology-attach awmg-mcpg (MCPG reaches agent via AWF's internal network; Detection runs without MCPG attachment).
    • Removed host.docker.internal row from the Default Allowed Domains table.
    • Updated Default Allowed Domains intro paragraph to explain that host.docker.internal is deliberately absent.
    • Removed stale "MCP-specific" category from the combined-hosts summary line.

Accuracy checks

  • Strict topology and --topology-attach awmg-mcpg verified against run_agent_step in src/compile/agentic_pipeline.rs (lines 2775–2793).
  • host.docker.internal absence verified against docs/network.md line 15: "deliberately not on this list".
  • CORE_ALLOWED_HOSTS in src/allowed_hosts.rs confirmed: no host.docker.internal entry.

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.dev

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "cdn.playwright.dev"

See Network Configuration for more information.

Generated by Docs Writer · 79.2 AIC · ⌖ 12.2 AIC · ⊞ 7.7K ·

- 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
jamesadevine marked this pull request as ready for review July 21, 2026 19:22
@jamesadevine
jamesadevine merged commit 158f305 into main Jul 21, 2026
3 of 5 checks passed
@jamesadevine
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant