gh-aw-firewall

You restrict HTTP and HTTPS egress by applying L7 domain whitelisting that enforces network isolation, ensuring AI agents can only reach explicitly approved external domains during execution. It uses iptables DOCKER-USER chains to apply firewall policies across all containers.

L7 domain whitelisting for sandboxed execution is an application-layer traffic control mechanism that prevents untrusted commands from reaching unauthorized external sites. It enforces network isolation by permitting only matching HTTP and HTTPS traffic patterns to approved domains.

To run Copilot or Claude CLI with controlled network access, execute the command through the firewall utility with an allow-domains flag. This restricts outbound traffic to only the specified domains, such as allowing github.com, while blocking all other external egress.

Yes, you can apply firewall policies across all Docker containers by using the iptables DOCKER-USER chain. This host-level enforcement ensures network isolation rules are applied container-wide, restricting HTTP and HTTPS egress traffic to only domain-whitelisted endpoints.

You generate Squid logs for debugging workflow connectivity by routing agent commands through the firewall, which uses Squid-based logging to record permitted traffic patterns. This provides statistics and logs that help diagnose network isolation issues and verify domain whitelisting behavior.

Yes, sandboxed execution with network isolation can optionally allow transparent access to host binaries like Python, Node, or Go through a chroot mechanism. This keeps network egress restricted while enabling the execution of necessary local tools.