Video summary

Your AI Coding Plan Is Now Worth Less

Main summary

Key takeaways

News and Commentary

Summary of the Video’s Main Points

  • AI coding subscriptions have been quietly “shrunk” while the public price stayed the same. The video argues that multiple vendors reduced effective usage allowances (or changed how they’re metered) after charging customers, making subscribers’ plans worth less than when they bought them.

Vendor-by-Vendor Changes

Anthropic (Claude)

  • Announced a permanent 25% increase to Claude code limits, but shortly after clarified it amounts to a ~17% cut versus the user’s current usage meter.
  • The allowance changes were described as having started with temporary boosts:
    • including doubling a session limit
    • adding weekly boosts
  • Those temporary boosts were extended repeatedly as competitors pressured the market.
  • By late August, what began as boosts effectively became baseline:
    • the temporary portion ends mid-September
    • it is replaced with the “25%” change, which the video claims works out lower in practice.
  • The video also emphasizes Anthropic’s lack of transparency:
    • real limit numbers are treated as a “mystery”
    • support/legal teams allegedly refuse to share the exact values.

OpenAI (Codex / ChatGPT-related coding features)

  • Meter changes were compressed into a short period:
    • Early August: removed a 5-hour Codex window and issued paid resets
    • user reports then indicated meters drained faster than expected
  • The video claims OpenAI stayed silent publicly until problems escalated.
  • It further claims Codex leadership later investigated and confirmed multiple bugs, including a background memory loop consuming quota.
  • After another reset and subsequent claims:
    • allowance was said to now go “10–50% further.”
  • After an apology/recovery period:
    • the 5-hour cap returned but only for the $20 tier
    • higher tiers (notably $100/$200) were kept exempt.
  • A new $100 business tier was launched around the same time.

Cursor and GitHub Copilot

  • Cursor
    • changed default “Auto mode” pricing:
      • from a flat rate
      • to model-dependent pricing
    • the email reportedly admitted this can raise costs for many requests.
  • GitHub Copilot
    • moved toward token pricing
    • framing suggests legacy plans became near-useless.
  • Across these vendors, the video’s theme is:
    • pricing labels remained stable
    • but the value inside the subscription fell
    • due to metering/rate-model changes.

Core Complaint: Poor Communication and Misleading Framing

  • The video argues customers learned about changes late or indirectly, such as:
    • deleted tweets
    • tool banners
    • community notes at midnight
  • It contrasts this with the marketing narrative:
    • vendors presented changes as protecting casual users or smoothing compute load
    • while the video claims higher-volume subscribers effectively faced throttling/ratcheting down.

Transparency Problems and “Unpublished Meter Math”

  • The video says none of the vendors publish exact limit values, forcing users to:
    • reverse-engineer meters through experimentation
  • Community conclusions (as described by the video) claim:
    • two cheaper accounts can outperform one expensive account
    • because caps and sub-caps (including model-specific sublimits) don’t scale linearly.
  • An example mentioned:
    • the “max” plan allegedly doesn’t double the weekly pool
    • due to a model sub-cap
    • and the “frontier” model may be constrained compared with cheaper options.

Financial / Market Context: Why This “Rationing” Is Happening

The video ties these behaviors to economics:

  • Vendors are constrained by GPU allocation, while:
    • enterprise API customers pay per token
    • subscriptions can become lower-margin during business hours
  • It references compute spend and projected losses, suggesting subscriptions become “loss leaders”
    • so rationing functions as a cost-control mechanism
  • It also notes Anthropic filed for an IPO
    • implying usage-cap changes could be strategically timed around market events.

Predictions and Advice

Predictions

  • The video predicts peak-hour throttling will return when market conditions allow.

Practical Advice for Subscribers

  • Avoid brand loyalty
    • the “value leader” rotates among vendors
  • Understand the meters/pools
    • avoid unnecessary model switching mid-session, which can force re-reading at full cost
  • Match cost to intent
    • use cheaper models for “testing/grind” work
    • save expensive models for real judgment calls
  • Consider self-hosted/local hardware
    • the only “meter” the user fully controls

Original video