QWE AI Academy The most common question new users ask isn’t what does GitHub Copilot do – it’s which plan should I actually pay for, and is the free tier enough to learn on? The honest answer changed twice in the last month. Start there.
Why most GitHub Copilot guides are already out of date
If you found a tutorial written before April 2026, it probably tells you to click “Subscribe to Pro” and get coding. That advice doesn’t work right now. GitHub’s official plans page confirms that as of April 20, 2026, new sign-ups for Copilot Pro, Copilot Pro+, and student plans are temporarily paused. Free tier or waiting – those are your options today.
The bigger shift hits June 1. All Copilot plans move to usage-based billing, where 1 AI Credit = $0.01 USD, and Chat, agent mode, code review, and CLI usage all draw from a monthly credit pool. The flat “unlimited assistant for $10” mental model disappears for those features, even though the price tag stays the same. Worth sitting with that for a second – it changes how you budget your sessions, not just your invoice.
Is this a problem? For most casual users, probably not. For anyone running multi-file agent sessions daily, the math shifts fast. That’s the real question to answer before June 1.
What the free tier actually gives you
2,000 completions and 50 chat requests per month (GitHub’s pricing page, as of 2026). The completions are generous. The 50 chats? One debugging session on a gnarly function can burn through 10 or more in my experience – so treat that number as your real constraint.
Code completions stay unmetered even after June. GitHub’s billing docs confirm that code completions and next edit suggestions are not billed in AI credits and remain unlimited on paid plans. So the inline gray-text autocomplete while you type? Unaffected. Only Chat, agent mode, code review, and CLI commands pull from the credit pool.
Getting started in VS Code (the actual sequence)
Skip the marketing walkthrough. Here’s what you actually do:
- Sign in to GitHub from VS Code’s Accounts menu in the Activity Bar.
- Install the GitHub Copilot extension from the Marketplace – it bundles Chat automatically.
- Start typing a function. Wait for gray ghost text. Tab accepts, Esc dismisses.
- Open the Chat panel for anything needing back-and-forth: explanations, refactors, multi-file changes.
- Create a
.github/copilot-instructions.mdfile in your project root. According to VS Code’s Copilot docs, these instructions apply automatically to all chat interactions in that repo.
That last step is the single biggest advantage most beginners skip. Five lines – “use TypeScript strict mode, prefer named exports, no default exports” – and every suggestion Copilot makes in that repo quietly improves without you touching a prompt.
Agent mode and the CLI: where things get interesting
Copilot in 2026 isn’t the completion-only tool from two years ago. The Copilot CLI brings agentic capabilities into the terminal – install via npm, authenticate with your GitHub account, and run prompts to generate code without leaving the command line.
# Illustrative usage - actual syntax may vary
npm install -g @github/copilot-cli
copilot
# > Explain this repo
# > Add a /categories endpoint following existing patterns
The CLI’s real trick: delegating work to Copilot’s cloud agent. Per GitHub’s blog, it preserves context, creates a new branch, opens a draft pull request, and makes changes in the background before asking for your review. That’s why billing had to change – a 20-minute background agent session burns far more compute than 10 autocompletes.
Three limits the docs don’t shout about
This is where most tutorials stop. Don’t.
| Constraint | What happens | Workaround |
|---|---|---|
| Weekly token cap | Model picker locks | Keep working via Auto model selection until the week resets |
| Mobile-store subscription | Can’t buy extra credits | Cancel and resubscribe at github.com |
| Pro tier model access | Opus models removed from Pro | Upgrade to Pro+ if you need Opus 4.7 specifically |
The weekly cap is the sneaky one. Turns out it’s not a hard cutoff – GitHub’s individual plan changes post explains it caps total token consumption during the week to control costs from parallelized long-trajectory agent runs. Hit the cap with premium requests still in your account? You keep working, but model choice locks to Auto until the reset. No GPT-5, no Claude – just whatever Auto picks.
The mobile billing trap is meaner. GitHub’s billing docs state the option to purchase additional premium requests is unavailable to anyone who subscribed via GitHub Mobile on iOS or Android. Signed up on your phone during a free trial and now want to top up? You can’t – not until you cancel and re-subscribe through the web.
Annual plan holders, read this before June 1. Per GitHub’s billing announcement, annual Pro and Pro+ subscribers stay on request-based pricing until renewal – but model multipliers increase June 1 for annual subscribers. In some usage patterns, that means annual subscribers pay more per request than someone who switched to monthly before the cutover.
A real test: the 50-chat ceiling
A junior dev tried to refactor a 400-line Express route file on the free tier. Ask Copilot to explain it. Ask it to suggest a split. Generate the new files. Review them. That sequence ate 17 chat requests – a third of the monthly free allowance on a single task.
Free isn’t bad. It’s a tasting menu. Do that kind of work twice a week and you hit 50 by day three. At that point: upgrade, wait, or know that extra premium requests cost $0.04 USD each (GitHub billing docs) – at 10 agent-heavy sessions a day, check your usage dashboard before the bill lands.
FAQ
Is the GitHub Copilot Free plan enough to learn on?
Yes, for a couple of weeks. Completions are generous. Chat is what runs out.
What changes for me on June 1, 2026?
Monthly Pro and Pro+ subscribers migrate automatically to usage-based billing. Each plan keeps the same monthly price and includes a credit allotment – but Chat, agent mode, code review, and CLI usage all draw from that pool now. If you mostly use inline completions and open Chat occasionally, you likely won’t notice. If you run agent sessions for an hour a day? Run the math now. Annual subscribers face a different wrinkle: model multipliers increase June 1 even before their plan renews, which can make some usage patterns more expensive than going monthly. Worth checking your renewal date.
Can I use Copilot outside VS Code?
Yes – Visual Studio, JetBrains, Neovim, Eclipse, Xcode, and Azure Data Studio all support completions. Chat availability is narrower: VS Code, Visual Studio, JetBrains, Eclipse, and Xcode as of 2026. The completion quality is identical across editors; the chat UI varies. Pick the editor you already live in.
Next step: sign in to GitHub from VS Code, install the Copilot extension, and create a .github/copilot-instructions.md with three rules about how you want code written. That one file will outperform any prompt trick you read about this week.