[cli-tools-test] Audit command fails to download artifacts for some workflow runs

[github-actions]

Problem Description

The gh aw audit command reports "No artifacts found" for some workflow runs, preventing detailed analysis of failed workflows. This affects the ability to debug and investigate workflow failures.

Command/Tool

• Tool: audit (via agentic-workflows MCP server)
• Command: agenticworkflows-audit run_id_or_url: 21876660976

Steps to Reproduce

1. Use the agentic-workflows MCP tool to audit a failed workflow run:

   agenticworkflows-audit run_id_or_url: 21876660976
   ```
   
   

2. Observe the output shows "No artifacts found"

3. Subsequent operations fail with "no such file or directory" errors:

   open /tmp/gh-aw/aw-mcp/logs/run-21876660976: no such file or directory
   

Expected Behavior

The audit command should:

• Download workflow artifacts successfully
• Create the logs directory structure
• Enable detailed analysis of the workflow run
• Provide actionable diagnostics for failed runs

Actual Behavior

• Audit reports "No artifacts found for run 21876660976"
• Log directory /tmp/gh-aw/aw-mcp/logs/run-21876660976 is not created
• Cannot save run summary cache
• Failure analysis is limited to job-level information from GitHub API

Environment

• Repository: github/gh-aw
• Run ID: 21876773883 (testing workflow)
• Target Run ID: 21876660976 (failed Security Guard Agent workflow)
• Date: 2026-02-10
• Workflow: Security Guard Agent 🛡️ (failed with conclusion: failure)

Impact

• Severity: HIGH
• Frequency: Intermittent - affects some failed runs
• Workaround: None - cannot audit runs without artifacts

Logs/Diagnostics

Audit output excerpt:

cli:audit Downloading artifacts for run 21876660976 +496ms
cli:logs_download Downloading run artifacts: run_id=21876660976, output_dir=/tmp/gh-aw/aw-mcp/logs/run-21876660976 +854ms
cli:audit No artifacts found for run 21876660976 +423ms
cli:logs_metrics No aw_info.json found at /tmp/gh-aw/aw-mcp/logs/run-21876660976/aw_info.json: stat /tmp/gh-aw/aw-mcp/logs/run-21876660976/aw_info.json: no such file or directory +4µs
cli:logs_cache Failed to write run summary to disk: open /tmp/gh-aw/aw-mcp/logs/run-21876660976/run_summary.json: no such file or directory +150µs

Comparison with successful audit (run 21874291152):

• ✅ Successfully loaded cached run summary
• ✅ Log directory created
• ✅ Metrics extracted

Additional Context

This issue appears to affect certain types of workflow runs, possibly:

• Runs that failed early (before artifact upload)
• Runs with permission issues during artifact creation
• Very recent runs where artifacts aren't yet available

The audit command should handle these cases gracefully and either:

1. Download job logs via GitHub Actions API as fallback
2. Provide clear messaging about why artifacts are unavailable
3. Suggest manual investigation steps

Suggested Fix

Enhance the logs download logic to:

1. Check if artifacts exist before attempting download
2. Fall back to downloading raw job logs via API if artifacts unavailable
3. Create log directory structure even when artifacts are missing
4. Provide clear error messages explaining the limitation

AI generated by Daily CLI Tools Exploratory Tester

• expires on Feb 17, 2026, 6:18 PM UTC