Repository navigation
[audit-workflows] Agentic Workflow Audit — 2026-05-23 (last 24h) — Success rate collapsed to 41.6% on two new harness/CLI bugs #34309
Closed
Replies: 2 comments
|
💥 KAPOW! 🦸 The Smoke Test Claude Agent has WHOOSHED through this discussion! 🌪️ ZZZAP! All systems nominal — Run 26349624985 is GO! 🚀✨ The agent leaps away in a single bound! 💨 Warning Firewall blocked 6 domainsThe following domains were blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "safebrowsingohttpgateway.googleapis.com"
- "www.google.com"See Network Configuration for more information.
|
0 replies
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #34537. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Overview
Daily audit of 77 runs across the last 24 hours surfaced two new critical issues that together drove the success rate from 75.6% (yesterday) to 41.6% — the worst of the past week. The agents themselves were largely fine; 24 of 43 failures are a pure harness bug where copilot-harness can't write
$GITHUB_OUTPUTafter the agent succeeds, and 14 more are caused by ananthropic-betaheader that the CAPI/proxy started rejecting.Summary
Critical issues (new today)
1. Harness ENOENT on
$GITHUB_OUTPUT— 24 false-failuresSymptom:
unexpected error: ENOENT: no such file or directory, open '/home/runner/work/_temp/_runner_file_commands/set_output_<uuid>'The copilot-harness reports the agent succeeded (
success on attempt 1,exitCode=0), then tries to write step outputs and fails because the runner's_runner_file_commandsdirectory is not visible from inside the AWF chroot. The job then exits1and the workflow is marked failed — even though the agent did its job.agent-stdio.log.success.Workflows most affected (pure-harness count): PR Sous Chef (6), PR Code Quality Reviewer (5), Matt Pocock Skills Reviewer (4), Test Quality Sentinel (4), Smoke CI (3), Auto-Triage Issues, Chaos PR Bundle Fuzzer, Issue Monster, Linter Miner, Daily Secrets, GEO Optimizer, PR Triage, PR Description Updater, Contribution Check, Daily Testify, Daily Safe Output Integrator, Daily Model Inventory.
2. Copilot CLI 1.0.48 sends a rejected
anthropic-beta: context-1m-2025-08-07header — 14 failuresSymptom:
CAPIError: 400 Unexpected value(s) 'context-1m-2025-08-07' for the 'anthropic-beta' header. Please consult our documentation at docs.anthropic.com or try again without the header.Copilot CLI v1.0.48 (
copilot/pkg/linux-x64/1.0.48/app.js) attaches the Claude 1M-context beta header on every model call. CAPI/proxy returns 400. The CLI retries twice and then gives up; the harness retries up to 4 times.Recurring issues
Codex engine still failing — model
gpt-5.5invalid (3 of 4 today)Yesterday's planned fix did not land. AI Moderator (×2) and Daily Cache Strategy Analyzer all returned
400 Bad Requestformodel=gpt-5.5via(172.30.0.30/redacted) (the AWF api-proxy). SameModelProviderInfo { name: "OpenAI AWF proxy" }` configuration as 05-21.Smoke CI cancellations — 3 of 11 today
Runs
26341182074,26340502327,26338770313all cancelled around 2m wall. This is the 5th consecutive day with this pattern.PR Sous Chef execution drift
Turns vary 6 to 52 across 10 runs (avg 20.8). Today's headline failure rate is 60% but all 6 failures are ENOENT — the prompt drift remains a slow-burn issue but is not today's main cause.
Firewall — 594 blocked of 3933 (15%) requests
Nearly all blocks (593) go to the
(unknown)bucket — almost certainly raw-IP egress or pre-DNS calls. Auto-Triage Issues had the highest workflow-level block rate at 32% (10/31).New low-severity findings
exit 127becausenodeis not on the AWF chrootPATH. Need to bind-mount the setup-node install directory.max_turns=20with permission denials ongit commit(ADR file) andgit fetch(PR head branch). $1.35 burned per attempt. Either grant those bash patterns, raise turn cap, or move the ADR commit to a post-step.deployment_statusruns cancelled at 1.0s — likely a pre_activation skip-if rule rejecting them.Top-cost runs
Trend charts
Workflow Health (7-day)
Today's success rate (41.6%) is a sharp cliff after a multi-day slide (92.8 → 88.9 → 85.9 → 75.6 → 41.6). The two new bugs above are the proximate cause; the underlying decline trend is older, mostly Codex.
Token Usage & Cost (7-day)
Tokens (46.2M) and cost ($24.61) are up ~25% from yesterday because the workflow volume nearly doubled (77 vs 41 runs). Per-run cost held steady at ~$0.32. Daily Safe Output Tool Optimizer fell from $8.54 → $5.55 — recovery from yesterday's anomaly.
Recommendations (priority order)
$GITHUB_OUTPUT— bind-mount/home/runner/work/_temp/_runner_file_commandsinto the AWF chroot, or have copilot-harness emit step outputs via a different channel. This single fix would recover ~24 false failures/day.anthropic-beta: context-1m-2025-08-07— at the api-proxy, or downgrade copilot CLI to a version without the beta header, or extend CAPI allow-list. Recovers ~14 failures/day.gpt-5.5does not exist on the proxy. Yesterday's planned fix did not land. Affects 3-4 codex workflows/day./opt/hostedtoolcache/node).git commit/git fetchbash patterns or move ADR write to a deterministic post-step.noopearlier (5th day of cancellations).References
All reactions