[aw] Issue Monster failed to assign agent
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Inspect .github/workflows/issue-monster.md and the failed workflow run to trace the Issue Monster agent-assignment step. Review the stated GH_AW_AGENT_TOKEN requirements and Copilot assignment configuration, then verify the workflow can assign the listed issues without authentication errors.
Written by the indexing model from the issue text.
Description
Workflow Failure
Workflow: Issue Monster
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/35618122008
[!WARNING]
Agent Assignment Failed: Failed to assign agent to issues or pull requests.
Assignment Errors:
- Issue #57728 (agent: copilot): Bad credentials - https://docs.github.com/rest
- Issue #61166 (agent: copilot): Bad credentials - https://docs.github.com/rest
- Issue #62132 (agent: copilot): Bad credentials - https://docs.github.com/rest
To resolve this, verify the token and Copilot assignment configuration:
- Set
GH_AW_AGENT_TOKENto a fine-grained PAT with metadata: read and actions, contents, issues, and pull requests: write, or use a classic PAT withrepo - Do not use a GitHub App installation token for Copilot assignment; the API rejects it
- Ensure the token owner can access the repository and assign users to issues
- Verify Copilot coding agent is enabled for this repository and organization policy allows bot assignments
- Docs: https://github.github.com/gh-aw/reference/copilot-cloud-agent/#authentication
- API reference: https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/use-cloud-agent-via-the-api#using-the-issues-api
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/github/gh-aw/actions/runs/35618122008
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
- Start your agent
- Load the
agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md - Type
debug the agentic workflow issue-monster failure in https://github.com/github/gh-aw/actions/runs/35618122008
[!TIP]
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter:safe-outputs: report-failure-as-issue: false
Generated from Issue Monster · pi · 8.33 AIC · ◷
- expires on Sep 22, 2026, 3:37 AM UTC
- Dominant language
- Go
- Stars
- 5.3k
- Forks
- 568
- Avg merge
- 4h 28m
- Merged PRs (30d)
- 660
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/gh-aw
-
automation code-quality cookie improvement quick-win task-mining
Difficulty 2/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
automation code-quality cookie improvement quick-win task-mining
Difficulty 2/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automation code-quality cookie improvement quick-win task-mining
Difficulty 2/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
Similar issues
-
self-host checker: E021 bound check reads an untyped literal at i32, not the type the call bindsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
JakeChampion/lang#11055 ·
Maintainers usually reply within 1 day
-
priority: low status: ready for dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hyperledger-labs/fabric-smart-client#2033 ·
Maintainers usually reply within 1 day
-
agent-butler-finding agent-research bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
jordansmall/spindrift#4249 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
acceptance-tests phase-coding schema-coverage testing triaged
Difficulty 2/5 1-2 days Newbie friendliness 84/100
elastic/terraform-provider-elasticstack#5053 ·
Maintainers usually reply within 1 day