GitHub Copilot just announced usage limits. I wrote about the solution two months ago. This week GitHub paused new sign-ups and tightened usage limits for Copilot — citing agentic workflows consuming far more resources than the original pricing model could handle. Here's the thing: this is exactly the problem I was trying to solve when I wrote my blog post back in March. I noticed I was defaulting to Opus models for everything — file listings, simple queries, complex architecture decisions — all treated the same. So I ran an experiment: I had all 17 GitHub Copilot CLI models evaluate each other anonymously using the LLM Council technique, to figure out which model is actually right for which task. The conclusion was straightforward: - Opus = deep reasoning, architecture, the expensive senior engineer - Sonnet = solid default for most coding tasks - Haiku / Mini = fast execution for simple, well-defined work - Codex = precision coding and terminal workflows Match model tier to task complexity. Use fast/cheap models for 80% of tasks, escalate for the 20% that actually need it. This can be fully automated with agent instructions. GitHub's new limits are essentially forcing that discipline. But you don't have to wait to get hit by a limit — you can set it up intentionally. GitHub's announcement: https://lnkd.in/dk3RZQQb My full writeup with the experiment, results, and model selection instructions: https://lnkd.in/dysdTKSJ Have you thought about which model you're defaulting to — and whether it's actually the right one for the job? #GitHubCopilot #AI #DeveloperTools #Microsoft
Very helpful Stefan. I am using it, works like a charm.
Exactly 👍
Sir we need to follow Anthropic and remove Claude models from Copilot subscriptions