Agentic workflows no longer need a personal access token
Quick Answer
GitHub Agentic Workflows now utilize the built-in GITHUB_TOKEN, removing the need for personal access tokens (PATs) and enhancing security.
Quick Take
This change allows organizations to directly bill AI credits consumed by workflows, streamlining cost management without user-level inference budgets. Users must enable specific Copilot policies and ensure they are on the latest Agentic Workflows CLI version.
Key Points
- No need for personal access tokens (PATs) in GitHub Agentic Workflows.
- AI credits consumed are billed directly to the organization.
- Enable 'Allow use of Copilot CLI billed to the organization' policy for this feature.
- User-level inference budgets do not apply when billing to the organization.
- Cost management tools help monitor and cap token usage.
Source Excerpt
You can now use GitHub Agentic Workflows with GitHub Actions’s built-in GITHUB_TOKEN. This means that you no longer need to create and store a personal access token (PAT), eliminating the…
Want this in your inbox every morning?
Daily brief at your local 8am — bilingual EN/中文, free.
More from GitHub Copilot Changelog
See more →
GitHub Copilot for JetBrains adds improved OpenTelemetry configuration and model management
The latest GitHub Copilot for JetBrains update enhances workflow control with OpenTelemetry configuration, improved model management, and support for servers in Claude agent flows, facilitating better observability and cost control for enterprise users.
