Use the network frontmatter field to control which domains an AI engine can reach during a workflow run. All traffic is enforced by the Agent Workflow Firewall (AWF).

# Shorthand — use default infrastructure domains only
network: defaults

# Custom — allow defaults plus package registries for a Node.js project
network:
  allowed:
    - defaults
    - node

# Custom — allow specific external APIs
network:
  allowed:
    - defaults
    - api.example.com
    - "*.trusted-partner.com"

# No network access
network:
  allowed: []

Each entry in network.allowed must be one of:

⚠️ Bare shorthands like npm, pypi, or localhost are NOT valid unless they are listed in the ecosystem identifiers table below. Use ecosystem identifiers (node, python) or explicit FQDNs (registry.npmjs.org, pypi.org) instead.

These keywords expand to curated lists of domains maintained by gh-aw:

These values look like they might work but are not valid ecosystem identifiers and will be passed through as literal domain names (and will almost certainly not match any real host):

• Wildcard * requires a dot prefix: *.example.com is valid; bare * is blocked (and rejected outright in strict mode).
• Protocol prefix is not supported: https://api.example.com is not a valid entry — omit the scheme and write api.example.com.
• Subdomains must be explicit: github.com does not cover api.github.com; use *.github.com or add both entries.

When a workflow builds, tests, or installs packages, always add the matching ecosystem alongside defaults:

⚠️ network: defaults alone is never sufficient for code workflows — defaults covers basic infrastructure (certificate authorities, Ubuntu verification) but cannot reach package registries. Always add the language ecosystem identifier.

network:
  allowed:
    - defaults
    - github

network:
  allowed:
    - defaults
    - node

network:
  allowed:
    - defaults
    - node
    - python

network:
  allowed:
    - defaults
    - api.myservice.com
    - "*.myservice.com"

network:
  allowed: []