π Daily Copilot Token Consumption Report β 2026-04-01 #23864
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Daily Copilot Token Consumption Report. A newer discussion is available at Discussion #24071. |
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.
-
Executive Summary
Over the reporting period, 133 Copilot-powered workflow runs across 65 unique workflows consumed 94,734,697 tokens (~94.7M), completing 1,865 agent turns in 1,199 action minutes (~20 hours). Cost data is not available in this dataset (all
$0.00). Compared to the February 2026 peak (237.8M tokens, 378 runs), today's consumption is 60% lower, returning to early-January baseline levels β a healthy sign of workflow optimization.Key Highlights
Daily Syntax Error Quality Checkβ 11.4M tokens, 168 turns (failed with 1 error)Issue Monsterβ 20 runs, averaging 173K tokens/runAgent Container Smoke Testβ 10 runs at only 142K tokens avgresource_heavy_for_domain, 41model_downgrade_available, 68partially_reducibleassessments across all runsSmoke Update Cross-Repo PR(3 errors) andSmoke Create Cross-Repo PR(2 errors) are repeat offendersπ Token Usage & Historical Trends
Token consumption over the tracked history shows a clear peak in February 2026 (up to 237.8M tokens on 2026-02-11) followed by a sustained decline back to ~95M tokens today. Run count has similarly decreased from 378 to 133 β roughly 65% fewer runs than the peak period.
Historical Daily Totals
π Top 10 Workflows by Token Consumption
π Most Active Workflows
The most frequently-run workflows with token efficiency context:
π‘ Insights & Recommendations
High-Cost Workflows
Daily Syntax Error Quality Check β 11.4M tokens, 168 turns, failed
missing_tool_count: 1). Consider a model downgrade togpt-4.1-minifor syntax-oriented tasks.Contribution Check β 6.7M tokens across 6 runs (avg 1.1M/run)
resource_heavy_for_domain. At 34 avg turns per run this is high for a PR review workflow.Daily Community Attribution Updater β 4.8M tokens, 97 turns, single run
resource_heavy_for_domainwithpoor_agentic_control. 97 turns is very high for a maintenance task.Agentic Assessment Summary (All Runs)
partially_reducibleresource_heavy_for_domainmodel_downgrade_availablepoor_agentic_controloverkill_for_agenticTop optimization lever: Moving data-gathering from agentic turns to deterministic pre-steps (e.g., writing data to
/tmp/gh-aw/agent/in frontmatter) could eliminate up to 50% of token consumption across 68 runs.Workflows with Errors
The Smoke suite shows persistent failures in cross-repo PR workflows β these should be investigated as infrastructure issues rather than token optimization.
Per-Workflow Full Statistics (All 65 Workflows)
π Methodology & Data Quality
Methodology Notes
github/gh-aw(last 30 days)agent: copilot)$0.00)/tmp/gh-aw/repo-memory/default/memory/token-metrics/history.jsonlReferences: Β§23846022060
Beta Was this translation helpful? Give feedback.
All reactions