GITHUB PAUSES COPILOT INDIVIDUAL SIGN-UPS, TIGHTENS LIMITS, RESTRICTS OPUS TO PRO+; COPILOT CLI GETS USABILITY BOOSTS
GitHub paused new Copilot Individual sign-ups, tightened usage limits, restricted Opus to Pro+, and shipped quality-of-life updates to the Copilot CLI. GitHub ...
GitHub paused new Copilot Individual sign-ups, tightened usage limits, restricted Opus to Pro+, and shipped quality-of-life updates to the Copilot CLI.
GitHub announced paused sign-ups for Copilot Pro/Pro+ and Students, new token-based limits, and Opus 4.7 availability only on Pro+—with refunds offered until May 20 announcement. Limits now surface inside VS Code and Copilot CLI to help avoid hitting caps.
Simon Willison explains the driver: agentic workflows burn far more compute than older usage patterns, so per-request billing and long sessions strained margins; the plan changes add per-session and weekly token caps overview. A recent model-picker incident is marked resolved, but some confusion persists around which Copilot products are affected incident thread.
Copilot CLI pre-releases add session naming/resume, a terminal usage “contribution graph,” LSP timeout config, and MCP OAuth cleanup, plus Windows/Linux fixes releases.
Agentic coding sessions now hit token caps faster; model access changes may impact your team’s workflows and budgets.
CLI improvements make session management and usage visibility better, which helps teams operate within the new limits.
-
terminal
Measure typical tokens burned per multi-turn coding/ops session and verify you stay within new per-session and weekly limits.
-
terminal
Validate which models appear in the IDE and CLI under your plan (Pro vs Pro+) and confirm fallbacks behave as expected.
Legacy codebase integration strategies...
- 01.
Audit who is on Individual Pro vs Pro+ and consider migrating power users or moving seats to Enterprise to stabilize access.
- 02.
Upgrade Copilot CLI and test session naming/resume, usage graph, and MCP auth flows; document outages and limit behaviors.
Fresh architecture paradigms...
- 01.
If you depend on long-running agents or Opus quality, start on Pro+ or an enterprise plan to avoid churn.
- 02.
Design workflows with hard token budgets, explicit background modes, and observable usage from day one.
Get daily GITHUB + SDLC updates.
- Practical tactics you can ship tomorrow
- Tooling, workflows, and architecture notes
- One short email each weekday