π Daily Copilot Token Consumption Report β 2026-03-23 #22415
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Daily Copilot Token Consumption Report. A newer discussion is available at Discussion #22661. |
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 current reporting period, 44 Copilot-powered agentic workflows consumed 97,580,594 tokens across 113 workflow runs with 1,926 agent turns total. No cost data is available in this period's logs. The average token consumption was 863,545 tokens per run, reflecting a mix of lightweight triage workflows and intensive deep-analysis agents.
Key Highlights
π Token Usage & Run Count Trends
Daily token consumption visualized against workflow run counts. Today's run (2026-03-23) represents 97.6M tokens across 113 runs β a significant volume driven by high-turn deep-analysis workflows alongside frequent Issue Monster executions.
β‘ Token Efficiency: Avg Tokens per Run
Average tokens per run over time. High single-run agents (Code Simplifier, Dead Code Removal, Glossary Maintainer) significantly inflate this metric. Excluding single-run deep agents, the average drops to ~450K tokens/run, consistent with multi-turn analytical workflows.
π Top Workflows by Token Consumption
Top 10 Most Token-Intensive Workflows
All 44 Workflows β Complete Statistics
π‘ Insights & Recommendations
High-Token Single-Run Agents (Top Concern)
Four workflows consumed 3β9M tokens in a single run due to extremely high turn counts (73β105 turns):
Code Simplifier β 8.97M tokens, 105 turns, 18.1m duration
Dead Code Removal Agent β 6.08M tokens, 80 turns, 21.5m duration
push) instead of full scan.Glossary Maintainer β 6.97M tokens, 73 turns, 14.1m
GitHub Remote MCP Authentication Test β 3.29M tokens, 85 turns
High-Volume Recurring Workflows
Optimization Opportunities
max_turnslimit of 40β50 per runEstimated total savings potential: ~28β38M tokens per similar period
Efficiency Insights
Historical Trend Comparison
Key observations:
Methodology & Data Quality
Methodology
/tmp/gh-aw/copilot-logs.json)memory/token-metrics/history.jsonl)4.5m,33.0s) converted to seconds for averagingData Quality Notes
token_usagefield (excluded from per-workflow token totals): includes the current in-progress report run and Documentation Noob Testerin_progressat time of data collection (Daily Copilot Token Consumption Report itself)Recommendations Summary
References:
Beta Was this translation helpful? Give feedback.
All reactions