Command-line interface for analyzing GitHub Copilot token usage from local session files. Works anywhere Copilot Chat stores its session data.
# Run directly with npx (no install required)
npx copilot-token-tracker-cli stats
# Or install globally
npm install -g copilot-token-tracker-cli
copilot-token-tracker statsShow discovered session files, sessions, chat turns, and token counts.
copilot-token-tracker stats
copilot-token-tracker stats --verbose # Show per-folder breakdownShow token usage broken down by time period.
copilot-token-tracker usage
copilot-token-tracker usage --models # Show per-model breakdown
copilot-token-tracker usage --cost # Show estimated costShow environmental impact of your Copilot usage (CO₂ emissions, water usage, tree equivalents).
copilot-token-tracker environmental
copilot-token-tracker env # Short aliasShow your Copilot Fluency Score across multiple categories (Prompt Engineering, Context Engineering, Agentic, Tool Usage, Customization, Team Collaboration).
copilot-token-tracker fluency
copilot-token-tracker fluency --tips # Show improvement tips, if there are anyShow all locations searched for session files, whether each path exists, and per-location stats (files, sessions, chat turns, tokens).
copilot-token-tracker diagnosticsThe CLI scans the same session files that the Copilot Token Tracker VS Code extension uses:
- VS Code (Stable, Insiders, Exploration) workspace and global storage
- VSCodium and Cursor editor sessions
- VS Code Remote / Codespaces sessions
- Copilot CLI agent mode sessions
- OpenCode sessions (JSON and SQLite)
# From the repository root
npm run cli:build # Build the CLI
npm run cli:stats # Run stats command
npm run cli:usage # Run usage command
npm run cli:environmental # Run environmental command
npm run cli:fluency # Run fluency command
npm run cli:diagnostics # Run diagnostics command
npm run cli -- --help # Run any CLI command- Node.js 18 or later
- GitHub Copilot Chat session files on the local machine
MIT - See LICENSE for details.


