GitHub Revamps Individual Copilot Subscription Plans
copilot
| Source: HN | Original article
GitHub has rolled out a reshaped pricing structure for its Copilot individual subscriptions, splitting the service into two tiers – Copilot Pro and the newly introduced Copilot Pro+. The change, announced on the company’s blog on 20 April, raises the base price of Copilot Pro from $10 to $12 per month and adds a $20‑per‑month Pro+ option that bundles Copilot Chat, priority access to the latest AI models and an expanded context window of up to 64 k tokens.
The move reflects GitHub’s strategy to monetize the rapid evolution of generative‑code assistants while rewarding power users with features that were previously limited to enterprise customers. Pro+ subscribers will be the first to receive updates from the Claude Opus 4.7 model, which promises more accurate completions and better handling of multi‑file refactorings – a capability highlighted in our recent coverage of Copilot’s integration with Claude‑based code generation (see 21 April). For developers in the Nordics, where remote and distributed teams rely heavily on AI‑driven productivity tools, the tiered pricing could influence budgeting decisions and adoption curves.
The new plans also tighten licensing rules: individual accounts must now link a verified payment method and can no longer share a single license across multiple machines without purchasing additional seats. Existing users are given a 30‑day window to migrate, after which the legacy “Copilot for Individuals” plan will be retired.
What to watch next: GitHub has hinted at a forthcoming “Copilot Studio” beta that will let users run a local LLM with persistent memory, echoing the community‑driven localmind project that surfaced in mid‑April. Additionally, the upcoming GitHub Universe conference in September is expected to reveal whether the Pro+ tier will expand to include fine‑tuning capabilities or tighter integration with Azure AI services. Developers should monitor the rollout for any regional pricing adjustments and the impact on open‑source contribution workflows.
Sources
Back to AIPULSEN