You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Daily audit of all agentic workflow runs from the last 24 hours (2026-02-19 → 2026-02-20). This is the first audit in repo memory, so no historical comparison is available yet.
Audit Summary
Metric
Value
Period
Last 24 hours (up to 2026-02-20 05:46 UTC)
Runs Analyzed
22 (21 completed, 1 in-progress)
Workflows Active
13 distinct workflows
Success Rate
90.5% (19/21 completed)
Total Tokens
148.8M
Total Cost
$1.83
Total Turns
113
Issues Found
2 errors, 1 missing tool, 1 missing data
Workflow Health
The overall system is healthy at 90.5% success rate. Codex-powered workflows dominated the period with 10 runs, all successful. Two failures occurred — one on a Gemini smoke test and one on Issue Monster (Copilot engine).
Missing Tools
Tool Name
Request Count
Workflows Affected
Reason
GitHub MCP tools (list_issues, get_repository)
1
GitHub Remote MCP Authentication Test
MCP toolsets unavailable in runner — tools not loaded
The github-remote-mcp-auth-test workflow detected that GitHub remote MCP toolsets are not being loaded. This is a recurring infrastructure concern that caused a discussion to be created (#17101).
Failure on branch copilot/update-clear-git-credentials-script
Both failures did not produce token usage data, indicating they failed before or during agent startup rather than during execution. The Gemini engine failure is consistent with its experimental status.
Missing Data
Data Type
Workflow
Reason
Pull request number
Smoke Codex
github-context pull-request-number is empty in workflow_dispatch context
The Smoke Codex run (§22211585147) was triggered via workflow_dispatch but the PR number context was missing, preventing it from adding smoke test comments to the target PR.
Performance Metrics
Metric
Value
Total Token Usage
148.8M tokens
Total Cost
$1.8285 (all from Daily Documentation Updater, Claude)
367 requests to - (unknown/null domain) — These are requests that were blocked before domain resolution, likely internal Docker network traffic or malformed requests. High rate in CI Failure Doctor (88 blocked).
github.com:443 — 1 blocked (Changeset Generator) — The Changeset Generator attempted to reach GitHub directly rather than via the MCP proxy. This is expected behavior that the firewall correctly intercepted.
proxy.golang.org:443 — 2 blocked (CI Failure Doctor) — The CI Doctor attempted to fetch Go modules. These are correctly blocked as this domain is not in the allowlist.
The high block rate (49.1%) is largely due to the null domain entries, which are an artifact of Docker internal networking rather than actual blocked outbound attempts.
Affected Workflows
Workflow
Status
Issue
Issue Monster
Failure
Execution error, early termination
Smoke Gemini
Failure
Gemini engine failure on PR smoke test
GitHub Remote MCP Auth Test
Success (with warning)
Missing GitHub MCP tools
Smoke Codex
Success (with warning)
Missing PR number context data
Recommendations
Investigate Issue Monster failure: The workflow failed without consuming tokens, suggesting a pre-execution configuration or activation error. Review §22212076876 startup logs.
Track Gemini stability: The Smoke Gemini failure on PR branch copilot/update-clear-git-credentials-script may indicate Gemini engine is not yet stable for PR smoke tests. Monitor for recurrence.
Fix GitHub Remote MCP configuration: The github-remote-mcp-auth-test workflow continues to fail because GitHub MCP toolsets don't load. See Discussion #17101 for details and remediation steps.
Fix Smoke Codex context passing: When Smoke Codex is triggered via workflow_dispatch, it lacks PR context. Consider adding a workflow_dispatch input for explicit PR number, or improving context detection.
Add proxy.golang.org to allowlist for CI Doctor: If CI Failure Doctor legitimately needs Go module access, add proxy.golang.org to its allowed domains configuration.
Monitor high codex token usage: The two Smoke Codex runs consumed 95.9M tokens combined. Ensure this is expected behavior for the test suite scope.
Historical Context
This is the first audit entry in repo memory. Future audits will compare against this baseline to identify trends in:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Daily audit of all agentic workflow runs from the last 24 hours (2026-02-19 → 2026-02-20). This is the first audit in repo memory, so no historical comparison is available yet.
Audit Summary
Workflow Health
The overall system is healthy at 90.5% success rate. Codex-powered workflows dominated the period with 10 runs, all successful. Two failures occurred — one on a Gemini smoke test and one on Issue Monster (Copilot engine).
Missing Tools
GitHub MCP tools(list_issues, get_repository)The
github-remote-mcp-auth-testworkflow detected that GitHub remote MCP toolsets are not being loaded. This is a recurring infrastructure concern that caused a discussion to be created (#17101).Error Analysis
Failed Workflows
copilot/update-clear-git-credentials-scriptBoth failures did not produce token usage data, indicating they failed before or during agent startup rather than during execution. The Gemini engine failure is consistent with its experimental status.
Missing Data
github-context pull-request-numberis empty in workflow_dispatch contextThe Smoke Codex run (§22211585147) was triggered via
workflow_dispatchbut the PR number context was missing, preventing it from adding smoke test comments to the target PR.Performance Metrics
Token Usage by Agent Engine
Note: Codex token counts are raw context tokens and not directly comparable to Claude's — Codex has a very different pricing model.
Top Workflows by Token Usage
Firewall Analysis
Allowed Domains
api.anthropic.com:443— 37 requests (Daily Documentation Updater)api.githubcopilot.com:443— 196 requests (Copilot-powered workflows)api.openai.com:443— 146 requests (Codex-powered workflows)proxy.golang.org:443— 2 requests (Smoke Codex)storage.googleapis.com:443— 2 requests (Smoke Codex)Notable Blocked Traffic
-(unknown/null domain) — These are requests that were blocked before domain resolution, likely internal Docker network traffic or malformed requests. High rate in CI Failure Doctor (88 blocked).github.com:443— 1 blocked (Changeset Generator) — The Changeset Generator attempted to reach GitHub directly rather than via the MCP proxy. This is expected behavior that the firewall correctly intercepted.proxy.golang.org:443— 2 blocked (CI Failure Doctor) — The CI Doctor attempted to fetch Go modules. These are correctly blocked as this domain is not in the allowlist.The high block rate (49.1%) is largely due to the null domain entries, which are an artifact of Docker internal networking rather than actual blocked outbound attempts.
Affected Workflows
Recommendations
Investigate Issue Monster failure: The workflow failed without consuming tokens, suggesting a pre-execution configuration or activation error. Review §22212076876 startup logs.
Track Gemini stability: The Smoke Gemini failure on PR branch
copilot/update-clear-git-credentials-scriptmay indicate Gemini engine is not yet stable for PR smoke tests. Monitor for recurrence.Fix GitHub Remote MCP configuration: The
github-remote-mcp-auth-testworkflow continues to fail because GitHub MCP toolsets don't load. See Discussion #17101 for details and remediation steps.Fix Smoke Codex context passing: When Smoke Codex is triggered via
workflow_dispatch, it lacks PR context. Consider adding aworkflow_dispatchinput for explicit PR number, or improving context detection.Add
proxy.golang.orgto allowlist for CI Doctor: If CI Failure Doctor legitimately needs Go module access, addproxy.golang.orgto its allowed domains configuration.Monitor high codex token usage: The two Smoke Codex runs consumed 95.9M tokens combined. Ensure this is expected behavior for the test suite scope.
Historical Context
This is the first audit entry in repo memory. Future audits will compare against this baseline to identify trends in:
References:
Beta Was this translation helpful? Give feedback.
All reactions