[audit-workflows] Agentic Workflow Audit — 2026-06-12 (copilot-sdk tool-lockout day 6 + NEW chroot/Node failure) #38952
Closed
Replies: 2 comments
-
|
Smoke bot grunt. Run 27447675349 poke cave wall. Latest talk still alive. 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.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #39155. |
Beta Was this translation helpful? Give feedback.
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.
-
Agentic Workflow Audit — 2026-06-12
Window: 2026-06-12 15:08–21:41Z (~6.5h, partial day — the
logsMCP tool timed out at 120s on continuation, so this audit is built from 120 locally-downloaded run directories, richer than the 34-run JSON the tool finished summarizing). Overall ~90.0% success; prod-main 93.2%. Production health is solid — but the same copilot-sdk-driver tool-permission-lockout that has dominated for nearly a week struck 4 prod-main runs again, and a new chroot/Node.js failure appeared.Summary
web-fetch,close_discussion)Critical Issues
1. 🔴 copilot-sdk-driver tool-permission-lockout — DOMINANT, day 6 (recurrence 6)
Four prod-main copilot runs hard-failed on
guard.tool_denials_exceeded 5/5, classified as "missing tool/permission" and not retried:27424904625git checkout -b ...(wasted 6.18M tok / 1061 AIC)27427030417read(.changeset/*.md),git show27428819181awk ...over*.go27437733590git status,read(workflow *.md)These are routine read-only / branch-setup commands the workflows legitimately need. Notably, claude runs (DeepReport, Failure Investigator) hit the same denials but tolerated/recovered — the hard-abort is specific to the copilot-sdk-driver path. This is the single highest-value prod-main reliability fix.
2. 🔴 NEW: Node.js not available inside AWF chroot
Daily Issues Report Generator(copilot, prod-main, run27425935620) aborted at entrypoint:[entrypoint][ERROR] Copilot CLI requires Node.js, but 'node' is not available inside AWF chroot.Agent never started. Also
[WARN] Failed to transfer .../safeoutputs ownership to chroot user. Picked up by[aw] Failure Investigator. Likely a regression from the active chroot/binaries-source-path refactor (branchcopilot/emit-chroot-binaries-source-pathwas running across the window).PR / branch failures (all by-design smoke-probe noise)
gemini-3.1-flash-tts-previewhas no AI-credits pricing →unknown_model_ai_credits. RECUR day 2, gemini engine 0/2 again.transient API error. Retrying...loop. RECUR day 2.create_issue #38943,set_issue_type, comments all OK), yet the safe_outputs job reddened each time. Smoke emits many output types; one rejected item reds the whole job (safe-output-partial-failure-intolerance). The smoke report itself flags product gaps: GitHub MCP review tool unavailable,mcpscripts-ghunavailable,create_discussionmissing label/temp-id support.items:[]) but downstream skipped and the run was tolerated/green. Low impact.Trend Charts
Workflow Health (30 days)
Success rate has held in a stable 84–96% band for two weeks; today's ~90% (prod-main 93.2%) is squarely mid-range and healthy. The persistent failure tail is not random — it's the same copilot-sdk-driver lockout class recurring daily, so the band won't tighten until that allow-list/guard fix lands.
Token Usage (30 days)
Daily tokens swing widely (15M–69M) driven by which heavy aggregators run; today's ~127M reflects a busier full-fleet window. The 7-day moving average smooths to a steady ~35–45M baseline — no runaway growth, but note 6.18M of today's tokens were burned then thrown away by the Daily Agent of the Day lockout.
Top token consumers
Good news: Daily Ambient Context Optimizer stayed under the ~1000 AIC / 25M-token cap this window — no 429 credit-cap abort (recurred 06-09/06-10).
Recommendations
nodeinside the AWF chroot: bind-mount the setup-node/nvm path into/hostand onto PATH, or bundle node into the chroot image; add a pre-flightnode --versioncheck so it fails fast with a clear message. Verify before the chroot/binaries-source-path work merges.gemini-3.1-flash-tts-previewto the api-proxy AI-credits pricing table or setapiProxy.defaultAiCreditsPricingso unknown gemini models degrade gracefully.close_discussionsafe-output: Daily Project Performance Summary Generator legitimately needs a way to close prior daily discussions ([daily performance] Daily Performance Summary - 2026-06-11 #38730, [daily performance] Daily Performance Summary - 2026-06-10 #38441) — currently no such tool.Context
audit-history.jsonl,metrics-summary.json,known-issues.json(sdk-driver→rec6, +chroot-node NEW),anomalies.json,recommendations.json(validated, 54 KB < 60 KB limit).Beta Was this translation helpful? Give feedback.
All reactions