Document GH_AW_AGENT_TOKEN in campaign getting started

[Copilot]

Campaign workflows that assign work to Copilot (via assignees: copilot or assign-to-agent safe outputs) require GH_AW_AGENT_TOKEN to be configured. The getting started guide only documented GH_AW_PROJECT_GITHUB_TOKEN.

Changes

• Add GH_AW_AGENT_TOKEN setup instructions in campaign getting started guide
• Clarify when this token is needed (for assigning work to Copilot)
• Link to agent assignment token reference documentation

The authentication section now documents both tokens users need to configure:

# For project access
gh aw secrets set GH_AW_PROJECT_GITHUB_TOKEN --value "YOUR_PROJECT_TOKEN"

# For assigning work to Copilot
gh aw secrets set GH_AW_AGENT_TOKEN --value "YOUR_AGENT_TOKEN"

Original prompt

In campaign docs getting started, also mention GH_AW_AGENT_TOKEN.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[mnkiefer]

@copilot Clarify that you need this when assinging work to Copilot.

[Copilot]

@copilot Clarify that you need this when assinging work to Copilot.

Updated the text to clarify this is specifically for "assigning work to Copilot" rather than generic "agents to issues". The change makes it clearer that this token is needed when using Copilot agent assignment in campaigns. (7b6f23b)

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• telemetry.astro.build
  • Triggering command: /opt/hostedtoolcache/node/24.13.0/x64/bin/node node /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)