10 optimisations most developers miss — including why the Copilot Coding Agent beats Agent Mode Chat every time
Most developers hit their monthly limit in the first week. Here’s what’s actually happening under the hood — and how to work smarter before it happens to you.
Photo by Resume Genius on Unsplash
Before diving in, it helps to understand what GitHub Copilot actually counts as a premium request, because most developers don’t find out until it’s too late.
Inline code completions on paid plans are unlimited and cost nothing. What drains your monthly allowance is everything else — Copilot Chat, Agent Mode, Copilot Code Review, Copilot CLI, and the Copilot Coding Agent.
Each model also carries a multiplier. Some models are included free on paid plans. Once your allowance is gone, premium features are locked for the rest of the billing cycle.
Knowing that, here’s how to make every request count.
1. Name your functions like they’re instructions
Inline autocomplete is unlimited on paid plans and costs nothing from your premium allowance. The more precisely you name a function, the more accurately Copilot completes the body without any Chat involved. This is your primary tool, not a fallback.
2. Write your intent as a comment above the cursor
A detailed comment placed directly before your cursor is treated by Copilot as an instruction. You get the same outcome as a Chat message at zero premium cost. Use this for any logic you would otherwise describe to Copilot in conversation.
3. Cycle through alternatives with Alt+] before opening Chat
When the first inline suggestion misses, most developers immediately reach for Chat. Before doing that, cycle through alternative suggestions. The second or third option is often exactly what’s needed — and one saved Chat message multiplies across a full day of work.
4. Disable Agent Mode when you’re not actively using it
Agent Mode runs in the background and silently runs even when you’re not directing it. GitHub’s official documentation explicitly flags this as a common cause of unexpected quota drain. Disable it in your repository settings when it isn’t part of your current workflow.
5. Use the Copilot Coding Agent for complex tasks instead of Agent Mode Chat
This is one of the least-known optimisations available. The Copilot Coding Agent — the one that creates and modifies pull requests asynchronously — counts as one premium request per full session regardless of how much work it does. Agent Mode Chat charges one premium request per message, multiplied by the model rate. For any task involving multiple files or significant implementation work, the Coding Agent is dramatically more efficient.
6. Start a new Chat thread when switching topics
As a conversation grows, all prior messages remain in context and contribute to token consumption. GitHub’s documentation specifically calls this out as a driver of elevated usage. When you move to a new task or a different area of your codebase, start a fresh thread rather than continuing an existing one.
7. Understand the model multiplier before choosing one
Before switching to a powerful model, weigh whether the capability gain justifies the cost. For most day-to-day work, it doesn’t.
8. Use auto model selection for a built-in discount
When you enable auto model selection in Copilot Chat in VS Code, GitHub applies a 10% multiplier discount across all premium model usage. It requires no change to your workflow and the saving compounds quietly across a full month.
9. Use #file references instead of @workspace
@workspace scans your entire codebase on every message, consuming more than most questions require. Using #file:yourfile.ts targets exactly the context Copilot needs, which produces more focused answers with less back-and-forth and fewer requests spent getting there.
10. Set a budget alert before your allowance runs out
GitHub lets you configure alerts at 75%, 90%, and 100% of any spending threshold you define. Setting a low or zero spending budget with alerts enabled means you get notified well before premium features are cut off — without risking unexpected charges. Check your current usage anytime at github.com/settings/billing or through the Copilot icon in your IDE status bar.
The Principle Underneath All of It
Every tip here points back to the same question worth asking before you open Chat: is there a way to get this through autocomplete instead?
Reference — https://docs.github.com/en/copilot
Most of the time, there is. And building that habit is what separates developers who hit the wall in week one from those who reach month end with room to spare.
Top comments (0)