{"slug": "agentic-workflows-no-longer-need-a-personal-access-token", "title": "Agentic workflows no longer need a personal access token", "summary": "GitHub announced that Agentic Workflows can now use the built-in `GITHUB_TOKEN` from GitHub Actions, eliminating the need to create and store personal access tokens (PATs). The change reduces operational and security risks associated with managing long-lived PATs for automations at scale. When using the Actions token in an organization-owned repository, AI credits consumed by the agentic workflow are billed directly to the organization.", "body_md": "# Agentic workflows no longer need a personal access token\n\nYou can now use GitHub Agentic Workflows with GitHub Actions’s built-in `GITHUB_TOKEN`\n\n.\n\nThis means that you no longer need to create and store a personal access token (PAT), eliminating the operational and security risks of managing long-lived PATs for automations at scale.\n\nWhen you use the Actions token in an agentic workflow running in an organization-owned repository, AI credits consumed by your agentic workflow are billed directly to the organization.\n\n[Configuring organization billing for Copilot CLI in GitHub Agentic Workflows](#configuring-organization-billing-for-copilot-cli-in-github-agentic-workflows)\n\nIn order to use this feature, you must enable the “Allow use of Copilot CLI billed to the organization” Copilot policy. This is enabled by default if you have the existing “Copilot CLI” policy enabled.\n\nOnce enabled, you can configure agentic workflows to bill directly to the organization by adding `copilot-requests: write`\n\nto the `permissions`\n\nsection in the frontmatter of your agentic workflow markdown file, then compiling and pushing your updated lockfile.\n\nNote: You must be on the latest version of the Agentic Workflows CLI. Use\n\n`$ gh extension upgrade aw`\n\nto upgrade.\n\n[Controlling cost while billing to your organization](#controlling-cost-while-billing-to-your-organization)\n\nUser-level inference budgets are not considered when billing directly to the organization, because the cost is not attributed to a user. There are multiple ways to manage spend when using this billing method:\n\n- Configure\n[cost centers](https://docs.github.com/billing/concepts/cost-centers)for the relevant organizations. Cost centers allow cost attribution to groups of organizations, and budgets can be applied to cost centers. - Use the\n[cost management tools](https://gh.io/gh-aw-cost)in GitHub Agentic Workflows to monitor, manage, and cap token usage per agentic workflow run.\n\nTo learn more, see the [GitHub Agentic Workflows documentation about authentication](https://gh.io/gh-aw-authentication).\n\nThis feature is available for all Copilot plans: Copilot Free, Copilot Pro, Copilot Pro+, Copilot Business, and Copilot Enterprise.", "url": "https://wpnews.pro/news/agentic-workflows-no-longer-need-a-personal-access-token", "canonical_source": "https://github.blog/changelog/2026-06-11-agentic-workflows-no-longer-need-a-personal-access-token", "published_at": "2026-06-11 15:55:49+00:00", "updated_at": "2026-06-11 18:18:40.168317+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "ai-products", "ai-infrastructure", "generative-ai"], "entities": ["GitHub", "GitHub Actions", "GitHub Agentic Workflows", "Copilot CLI"], "alternates": {"html": "https://wpnews.pro/news/agentic-workflows-no-longer-need-a-personal-access-token", "markdown": "https://wpnews.pro/news/agentic-workflows-no-longer-need-a-personal-access-token.md", "text": "https://wpnews.pro/news/agentic-workflows-no-longer-need-a-personal-access-token.txt", "jsonld": "https://wpnews.pro/news/agentic-workflows-no-longer-need-a-personal-access-token.jsonld"}}