{"version":"2.1.268","anchor":"rate-limit-overage-check-now-excludes-1m-context-credit-clam","canonical_anchor":"rate-limit-overage-check-now-excludes-1m-context-credit-clam","heading":"Rate-limit overage check now excludes 1M-context credit-clamp cases","tier":"notice","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/rate-limit-overage-check-now-excludes-1m-context-credit-clam","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Rate-limit overage check now excludes 1M-context credit-clamp cases\n\nRate-limit errors caused by needing 1M-context credits now show the correct dedicated message instead of a generic overage one\n\n**What**\n\nWhen Claude Code hits a 429 rate-limit response, it decides whether to show an 'extra usage' (overage) message or a different one. That check now specifically excludes cases where the error is actually about needing 1M-context usage credits, so those get routed to the dedicated usage-credits message instead.\n\n**Why**\n\nThis prevents a case where a 1M-context credit issue was being mislabeled as a generic overage-disabled error, which would have pointed users toward the wrong fix.\n\n- Area: Rate Limits\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}