published Aug 26, 2026, 9:07 AM · updated Aug 26, 2026, 9:29 PM
Workflow Failure
Workflow: Daily AW Cross-Repo Compile Check
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/32950417547
Warning
Missing Tools Reported: The agent reported missing tools during execution.
Missing Tools:
- gh CLI / GitHub REST API (authenticated search and repo metadata): GH_TOKEN in this run is invalid: `gh auth status` reports "The token in GH_TOKEN is invalid"; `gh api user` and `gh search code` both return HTTP 401 Bad Credentials. SBX_CRED_GITHUB_MODE=none in the environment indicates this sandbox was not issued live G
[Content truncated due to length]
Alternatives:
| Tool | Alternative |
|---|---|
| gh CLI / GitHub REST API (authenticated search and repo metadata) | Building the local gh-aw binary from source succeeded (make build, after redirecting GOPATH/GOCACHE/GOMODCACHE to a writable tmp dir) and `gh-aw --version` reports d846ab2, so tooling for compilation itself is ready once a repository list is available from a run with working GitHub API credentials. |
Warning
Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.
Reasons:
-
gh CLI GitHub API authentication is broken, blocking repository discovery
Daily AW cross-repo compilation run could not proceed past Phase 0.
Completed:
- Phase 0: built latest gh-aw from source (commit d846ab2) after redirecting GOPATH/GOCACHE/GOMODCACHE to a writable tmp directory (the default
/home/runner/gois root-owned and not writable by the workflow user).gh-aw --version-> "gh aw version d846ab2".
Blocked:
- Phase 1 (discover candidate repos):
ghCLI authentication is broken in this run.gh auth statusreports the GH_TOKEN is invalid, and bothgh api userandgh search code --filename '.lock.yml' ...return HTTP 401 Bad Credentials. A raw unauthenticated curl to the code-search endpoint also returns 401, confirming GitHub requires auth for code search with no anonymous fallback. Plaingit cloneover https to a public repo succeeded, so general network egress is fine — only GitHub API authentication is broken. - Because Phase 1 could not produce a candidate/ranked repository list, Phases 2-4 (per-repo clone/compile/fix, failure analysis, error clustering) could not run, and no repository data was collected.
Filed a missing_tool report for the auth issue. No cache-memory run artifacts beyond the build log were meaningful to persist since no repositories were discovered. Re-running this workflow once GH_TOKEN/gh auth is fixed for the runner should allow the full pipeline to execute.
This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.
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/32950417547
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 daily-aw-cross-repo-compile-check failure in https://github.com/github/gh-aw/actions/runs/32950417547
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:
safe-outputs:
report-failure-as-issue: falseGenerated from Daily AW Cross-Repo Compile Check · claude · 70.1 AIC · ◷
- expires on Aug 26, 2026, 9:07 PM UTC