Skip to content

[aw] CLI Flag Consistency Checker failed #2107

@github-actions

Description

@github-actions

Workflow Failure

Workflow: CLI Flag Consistency Checker
Branch: main
Run: https://github.com/github/gh-aw-firewall/actions/runs/24640133627

⚠️ Engine Failure: The copilot engine terminated unexpectedly.

Last agent output:

- 🔴 **High priority**: `--memory-limit` default is documented as `2g` in `usage.md` but the implementation default is `6g`. Also: `--gemini-api-target/base-path`, `--difc-proxy-host/ca-cert`, and `--config` are undocumented everywhere.
- 🟡 **Medium priority**: `--diagnostic-logs`, `--docker-host`, `--upstream-proxy` missing from both doc files; 6 flags present in `cli-reference.md` but absent from `usage.md`.
- 🟢 **Low priority**: `predownload` and `logs audit` subcommands not in `usage.md`; `--difc-proxy` predownload option not in `cli-reference.md`; AGENTS.md/CLAUDE.md examples inconsistently omit `--` separator.
**Coverage**: `cli-reference.md` is more complete (43/52 flags) while `usage.md` lags behind (37/52).
Changes   +0 -0
Duration  13m 57s
Tokens    ↑ 654.2k • ↓ 12.6k • 588.2k (cached)
[copilot-driver] 2026-04-19T22:15:56.554Z attempt 1: process exit event exitCode=0
[copilot-driver] 2026-04-19T22:15:56.555Z attempt 1: process closed exitCode=0 duration=13m 58s stdout=7373B stderr=90B hasOutput=true
[copilot-driver] 2026-04-19T22:15:56.555Z success on attempt 1: totalDuration=13m 58s

Action Required

Assign this issue to Copilot using the agentic-workflows sub-agent to automatically debug and fix the workflow failure.

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-firewall/actions/runs/24640133627
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

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: false

Generated from CLI Flag Consistency Checker ·

  • expires on Apr 26, 2026, 10:16 PM UTC

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions