githubnext / githubnext/ado-aw
[aw] Issue Triage failed
- Dominant language
- Rust
- Stars
- 23
- Forks
- 8
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 22
Description
### Workflow Failure
**Workflow:** [Issue Triage](https://github.com/githubnext/ado-aw/blob/main/.github/workflows/issue-triage.md)
**Branch:** main
**Run:** https://github.com/githubnext/ado-aw/actions/runs/34823752004
> [!WARNING]
> **Engine Failure**: The `copilot` engine terminated unexpectedly.
**Last agent output:**
```
└ Permission denied and could not request permission from user
● Test true command (shell)
│ true
└ 1 line…
✗ Try safeoutputs with quoted args (shell)
│ 'safeoutputs' '--help'
└ Permission denied and could not request permission from user
● Search for copilot config directories (shell)
│ find / -maxdepth 4 -iname "*.copilot*" 2>/dev/null; ls -la /home/runner/.copilot/ 2>&1
└ 14 lines…
```
### 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/ado-aw/actions/runs/34823752004
````
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 issue-triage failure in https://github.com/githubnext/ado-aw/actions/runs/34823752004`
> [!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 [Issue Triage](https://github.com/githubnext/ado-aw/actions/runs/34823752004) · 174.3 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fado-aw+is%3Aissue+%22gh-aw-workflow-id%3A+issue-triage%22&type=issues)
> - [x] expires on Sep 21, 2026, 8:52 AM UTC
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with .github/workflows/issue-triage.md, the linked workflow run, and the debugging guidance in debug.md or the agentic-workflows skill. Reproduce or inspect the permission-denied failures around shell and safeoutputs, then rerun the Issue Triage workflow to confirm the agent completes without the reported engine failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100