Home / Guides / Copilot Rate Limits
GitHub Copilot Rate Limits Explained
Everything you need to know about GitHub Copilot rate limits - Free vs Pro vs Business quotas, the premium request multiplier, and how to avoid silently degraded autocomplete.
Last updated April 2026 · By Soren Starck
What Are GitHub Copilot Rate Limits?
GitHub Copilot enforces two distinct limits depending on your plan. The Free plan caps monthly chat and completion counts. Pro, Pro+, and Business plans remove that cap on the base model but introduce a separate premium request quota for any call routed through a premium model.
The Three Tiers at a Glance
| Plan | Base completions | Chat / month | Premium requests |
|---|---|---|---|
| Free | 2,000 / month | 50 | - |
| Pro | Unlimited | Unlimited (base) | 300 |
| Pro+ | Unlimited | Unlimited (base) | 1,500 |
| Business / Enterprise | Unlimited | Unlimited (base) | 300 – 1,000+ per seat |
Once your premium quota is gone, Copilot doesn't error out. It quietly falls back to the base model. Your autocomplete just feels worse and you have no idea why.
The Premium Request Multiplier
Not every premium request costs the same. GitHub applies a multiplier per model and per task type:
| Model / Task | Approx multiplier | Notes |
|---|---|---|
| Base model | 0x | Free, doesn't touch premium quota |
| Claude Sonnet 4 | 1x | Standard premium |
| GPT-4.1 / GPT-4o | 1x | Standard premium |
| Claude Opus / o1 | 5x – 10x | Heavy reasoning models |
| Agent / multi-step | 2x – 10x | One ask, many model calls |
On Pro (300 premium requests/month), a single agent task on Opus can burn 50+ requests. Two of those a week and your quota is gone before you notice.
What Happens When You Hit the Limit
- Silent degradation - Copilot routes your request to the base model without telling you
- No popup - no native UI signal that you're out of premium
- No ETA - the dashboard doesn't show your billing-cycle reset clearly
- Lost productivity - Opus-quality answers become base-model answers mid-debug
SessionWatcherCopilot fades silently.
SessionWatcher shows the burn.
Native macOS menu bar app. Track Claude and Codex usage, costs, and rate limits in real-time.
“Fast, simple, and does exactly what it should. Definitely worth it.”
@nicojerome on GitHub
macOS 14+. $2.99 one-time purchase.
How to Monitor Copilot Rate Limits
SessionWatcher for Copilot is a native macOS menu bar app for exactly this. It tracks:
- Premium request count against your plan's monthly cap
- Burn rate - premium requests per day, projected to month-end
- Model breakdown - which premium models are eating your quota
- Billing-cycle countdown - exact day/time of quota refresh
- macOS notifications - at 80% and 95% so you can pace
Tips for Managing Your Premium Quota
- Reserve Opus / o1 for hard problems - they're 5x–10x more expensive than Sonnet or GPT-4.1.
- Use the base model for routine autocomplete - it doesn't touch your premium quota at all.
- Track burn rate, not just totals - 100 requests on day 5 means trouble by day 10.
- Time agent runs deliberately - multi-step agent tasks are the biggest quota eaters.
- Set notifications - SessionWatcher pings you before silent fallback kicks in.
Frequently Asked Questions
What are GitHub Copilot rate limits?
Free plans cap at 50 chats and 2,000 completions/month. Pro caps premium model requests at 300/month, Pro+ at 1,500. Models use a 1x–10x multiplier per request.
How long until my Copilot quota resets?
Quota resets on your billing date, not the calendar month. SessionWatcher tracks the exact countdown for you.
How do I avoid hitting Copilot rate limits?
Monitor in real time with SessionWatcher ($2.99 one-time). It shows current usage, projected burn rate, and notifies you at 80% so you can pace your premium-model work.