On this page

Know the unit

GitHub defines a request as an interaction with Copilot, but premium request consumption depends on the feature and model. Chat, CLI prompts, and code review can follow different rules. GitHub's current documentation is the right place to verify the multiplier attached to a feature.

This is especially important for automated review. A workflow that runs on every pull request may consume a meaningful share of the monthly pool without appearing in your editor history.

Track personal and team usage

Individuals can use GitHub's billing and Copilot usage views. Organizations can retrieve premium request usage through GitHub's billing APIs and group it by model or SKU. That creates a reliable source for budgets and team reports.

On a Mac, Super Notchy can surface the Copilot quota reading using the GitHub CLI session already on the machine. It is a convenient headline view, while GitHub remains the detailed billing source.

Keep your usage visible while you work. Get Super Notchy for $39 ↗

Prevent quiet overuse

Review which workflows call premium models, which model multipliers are active, and whether every automated review still earns its cost. Set alerts before the end of the month rather than waiting for a blocked request.

The best metric is not requests alone. Pair usage with accepted suggestions, merged changes, or review findings so the team can see which Copilot work is useful.

Sources and further reading