/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Docs: Microsoft plans to eventually move GitHub Copilot from request- to token-based billing, as the week-over-week cost to run it has nearly doubled since Jan.

www.wheresyoured.at/news-microso... …Forums:r/BetterOffline:Exclusive: Microsoft To Shift GitHub Copilot Users To Token-Based Billing, Reduce Rate Limits

Ed Zitron's Where's Your Ed At Edward Zitron

Context & Ripple Effects

The coverage arc moves quickly from internal indications of token-based billing and tighter limits to GitHub’s announced June 1 migration to monthly AI Credits. Subsequent reports describe the model taking effect and users encountering materially tighter effective usage than under flat-rate plans.

The story matters because it makes Copilot’s underlying inference costs visible to customers: the reported rise in operating cost is followed by a pricing mechanism that meters consumption rather than absorbing it in a subscription.

First-order effects

  • GitHub Copilot users face reduced predictability in their monthly spend and available usage as requests give way to token- or credit-based metering and tighter limits.
  • Microsoft/GitHub can align Copilot revenue more directly with costly usage, while restricting access to higher-cost models by plan tier.

Second-order effects

  • Developer teams that relied on broad flat-rate access will have an incentive to set usage controls, route simpler work to cheaper tools or models, and scrutinize whether Copilot use is worth its incremental cost.
  • Competing coding-assistant vendors face pressure to clarify their own limits and pricing economics; flat-rate offers become harder to sustain if model-serving costs remain elevated.

Third-order effects

  • If usage-based billing persists, AI coding assistants may evolve from a bundled developer perk into a metered infrastructure expense, with procurement focused on cost per useful task rather than headline subscription price.
  • The episode points to a broader test of whether AI application vendors can preserve adoption while passing variable inference costs through to users; the outcome will shape how much premium-model access remains included in standard plans.

The trend: Generative-AI software is shifting from subsidized flat-rate subscriptions toward pricing and product limits that expose the economics of compute-intensive usage.

Discussion

  • @edzitron.com Ed Zitron on bluesky
    Exclusive: Microsoft is reducing rate limits on GitHub Copilot, removing Opus from $10-a-month subscriptions, and plans to move users to token/API-based billing some time later in 2026 in a sign that it's looking for way to cut costs for its AI services.  —  www.wheresyoured.at/n…
  • r/BetterOffline r on reddit
    Exclusive: Microsoft To Shift GitHub Copilot Users To Token-Based Billing, Reduce Rate Limits
  • @carnage4life Dare Obasanjo on bluesky
    AI token subsidies seem to be ending across the industry.  —  GitHub Copilot has paused new signups on multiple plans, removed Opus from $10-a-month subscriptions, and plans to move users to token/API-based billing later this year.  —  Usage quotas are also being reduced and user…
  • r/GithubCopilot r on reddit
    This is plain extortion