Commercial software intelligenceEvidence checked · 8 September 2026
SkuTrace

Commercial product change, preserved as evidence.

SK-2026-136 · Licensing models & usage

Copilot CLI adds built-in GITHUB_TOKEN authentication in GitHub Actions

GitHub Actions workflows can authenticate Copilot CLI with the built-in GITHUB_TOKEN when organisation policy and copilot-requests: write are enabled; AI credits bill directly to the organisation.

Organisation-billed route available

Commercial transition

Previous stateCopilot CLI automation in GitHub Actions required a separately created and stored personal access token.
→
New stateEligible organisation-owned repositories can use the workflow GITHUB_TOKEN with copilot-requests: write and bill consumed AI credits directly to the organisation.

Who is affected

GitHub organisations running Copilot CLI from Actions workflows and the administrators governing their AI-credit spend.

Action required

Enable the organisation policy deliberately, grant only copilot-requests: write, use a recent CLI version and govern spend with cost centres, dashboards and session limits.

Evidence boundary

User-level budgets do not apply to this organisation-billed route. The organisation policy, repository ownership, workflow permission and current CLI prerequisites remain mandatory.

Timeline

  1. Authentication route released

    GitHub documented built-in token authentication and direct organisation AI-credit billing for eligible Actions workflows.

Official sources