githubnext / githubnext/gh-aw-cao
[aw] PR Sous Chef hit Copilot organization billing error
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
### Workflow Failure
**Workflow:** [PR Sous Chef](https://github.com/githubnext/gh-aw-cao/blob/main/.github/workflows/pr-sous-chef.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-cao/actions/runs/35070165834
> [!WARNING]
> **Copilot organization billing is unavailable**: The workflow uses `permissions.copilot-requests: write`, but GitHub Copilot rejected the built-in `GITHUB_TOKEN`.
To resolve this:
1. Ask an organization owner to check **Organization settings → Copilot → Policies → Copilot CLI** and enable **Allow use of Copilot CLI billed to the organization**.
2. If organization billing is unavailable, use individual billing instead: set `permissions.copilot-requests: none`, configure a `COPILOT_GITHUB_TOKEN` repository secret with a fine-grained personal access token from a user with an active Copilot subscription, and recompile the workflow.
See [Copilot billing](https://github.github.com/gh-aw/reference/billing/) for complete setup instructions.
> [!WARNING]
> **Engine Failure**: The `copilot` engine terminated unexpectedly.
**Last agent output:**
```
Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
Changes +6 -4
Duration 12m 29s
Tokens ↑ 11.3m (11.2m cached) • ↓ 44.3k
Resume copilot --resume=de8a8258-2904-4a61-b107-284523e4058b
Authentication failed with provider at http://172.30.0.30:10002 (HTTP 403).
Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
Changes +0 -0
Duration 0s
Resume copilot --resume=886c3434-f6bc-43e6-a6e6-5d4c6b79e0a1
```
### Action Required
**Assign this issue to an agent** to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
````
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/githubnext/gh-aw-cao/actions/runs/35070165834
````
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.
- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow pr-sous-chef failure in https://github.com/githubnext/gh-aw-cao/actions/runs/35070165834`
> [!TIP]
>
> Stop reporting this workflow as a failure
>
> To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>
> Generated from [PR Sous Chef](https://github.com/githubnext/gh-aw-cao/actions/runs/35070165834) · copilot · 300.1 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-id%3A+pr-sous-chef%22&type=issues)
> - [x] expires on Sep 17, 2026, 8:06 AM UTC
Contributor guide
Research direction
Start with .github/workflows/pr-sous-chef.md and the failed run linked in the issue. Check the workflow's Copilot permissions and the organization's Copilot CLI billing policy, then review the provider authentication settings described in the run output. Done means the workflow can run successfully without the billing or authentication errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100