Repository navigation
[detection-analysis] Detection Analysis Report — 2026-10-17 #69797
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #70034. |
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.
Summary
aw_info.json, meaning theagentjob never ran far enough to emit it; out of scope for this report's detection rules)gh-aw-detection: false): 60 (12.4%)Warning
One workflow (
Smoke Copilot) hasgh-aw-detection: falsewith run volume above the misconfiguration threshold.Comparison Chart
detection: false)Regular runs are almost entirely engine smoke/conformance tests (
Smoke Copilot,Smoke Claude Routed,Smoke Codex,Smoke Cursor, etc.) that intentionally opt out of detection since they exercise raw engine plumbing rather than untrusted content — this explains most of the lower success rate and token usage in that group, not a defect in the detection feature itself.Misconfigured Workflows
Smoke Copilotgh-aw-detection: falsewith >3 runs in window.github/workflows/smoke-copilot.mdsetsfeatures.gh-aw-detection: falseexplicitly. This appears to be a deliberate choice for a build/pass-rate smoke test, but it exceeds the high-volume threshold this check flags on. Confirm the opt-out is intentional; if so, no action needed beyond documenting why, otherwise remove the override so detection runs by default. Example run: §38987143187.No runs matched the "detection job itself failed while enabled" rule (rule 2), and no workflow alternated between enabled/disabled within the window (rule 3).
One adjacent observation (not flagged, informational only): run §38992703035 (
Smoke Copilot, detection explicitly disabled) shows itsdetectionjob withconclusion: failure. Inspection shows this job still executes unconditionally (gated internally by adetection_guardstep) even when the feature is disabled, and here the failure traces to a shared infrastructure step, "Download container images," which failed identically in theagentjob in the same run — a transient infra issue, not a detection-logic defect.View All Run Metrics
Workflows with more than one run in the window (28 of 188 distinct workflows seen):
The remaining 160 workflows each had exactly 1 run in the window: 120 succeeded, 40 failed/other (75% success rate), spread across
copilot,codex,claude,pi,aider,goose,agy,cursor,opencode,crush,deepseek-harness, andgeminiengines. None of these single-run workflows meet the >3-runs-in-window threshold used for misconfiguration rule 1.View Historical Trend
Based on 19 accumulated daily snapshots in cache-memory (7 unique calendar days after de-duplication), showing regular vs. detection-enabled run counts per day with a shaded band for detection success rate.
Recommendations
Smoke Copilot. It explicitly setsgh-aw-detection: falsein.github/workflows/smoke-copilot.mdand runs frequently enough (5×/24h) to trip the high-volume misconfiguration threshold. If this is a deliberate smoke-test scoping decision (likely, given its purpose), no code change is needed — just confirm. If not intentional, drop the override.References:
Smoke Copilot, example of the flagged misconfigurationSmoke Copilot, informational: detection job failed due to shared infra issue while detection was disabledSmoke Copilot, latest run in window with the samegh-aw-detection: falsesettingAll reactions