GitHub Removes PAT Requirement for Agentic Workflows

GitHub has rolled out a crucial update for its Agentic Workflows, removing the dependency on Personal Access Tokens (PATs) and instead enabling the use of GitHub Actions' inherent `GITHUB_TOKEN` for authentication. This move is a significant step towards bolstering the security posture of automated processes within GitHub. Previously, developers often had to create, store, and regularly rotate PATs, which presented both an operational burden and a potential security vulnerability, especially if these tokens had broad permissions and long lifespans. The transition to `GITHUB_TOKEN` offers a more secure alternative. This token is intrinsically short-lived, automatically generated for each workflow run, and its permissions are strictly defined within the workflow file itself. This default scoping minimizes the blast radius in case of a compromised workflow, making agentic automation much safer for production environments. Developers can configure this by adding `copilot-requests: Write` to the permissions section of their agentic workflow's markdown file, then recompiling and pushing the updated lockfile. Agentic Workflows are designed to automate reasoning-based tasks, such as issue triage, analysis of CI failures, and documentation updates, by using coding agents within GitHub Actions. These workflows are defined using natural language in Markdown files, which GitHub then compiles into standard Actions YAML. They benefit from existing runner groups and policy constraints, and agents typically run with read-only permissions by default, with safe outputs applied via separate jobs using scoped write tokens. Beyond the security enhancements, this update also brings changes to how AI usage is tracked and billed. When an agentic workflow runs in an organization-owned repository using the Actions token, AI credits are now billed directly to the organization. This shift facilitates better cost management and attribution, allowing organizations to monitor, cap, and attribute token usage per workflow run. To enable this, organizations need to activate the “Allow use of Copilot CLI billed to the organization” policy, which is often on by default if the existing Copilot CLI policy is already enabled. This feature is available across all Copilot plans, from Copilot Free to Copilot Enterprise.