Claude Code’s Temporary Usage Boost Expires Tonight. Here’s What Actually Changes

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

If you’ve been running Claude Code hard the last few months, tonight is the night your headroom shrinks back down. At 11:59 PM PT, Anthropic’s temporary 50% bump to Claude Code’s weekly usage limits runs out. It’s the fourth deadline Anthropic has set for this promotion since introducing it in May, and this time there’s no indication another extension is coming. Same subscription, same price, less capacity. For teams that built sprint plans, CI pipelines, or just daily habits around that extra room, the math changes today. Mike Vizard, editor-in-chief of DevOps.com, asked a fair question when this story crossed his desk: Is this new? The honest answer is no and yes. Weekly caps on Claude Code aren’t new at all — Anthropic put them in place back in July 2025, with an effective date of August 28 that year, after what the company described as “unprecedented demand” for the tool. Some subscribers were running Claude Code continuously, 24 hours a day. Others were sharing or reselling access in violation of the terms of service. Anthropic said the caps would affect fewer than 5% of subscribers based on usage patterns at the time, and it built in separate weekly allowances for Sonnet and Opus, depending on the plan tier. The original 2025 caps were tiered by plan. Pro subscribers at $20 a month got roughly 40 to 80 hours of Sonnet 4 usage per week. Max, at $100 a month, got 140 to 280 hours of Sonnet, plus 15 to 35 hours of Opus. Max, at $200 a month, got 240 to 480 hours of Sonnet, plus 24 to 40 hours of Opus. Anthropic was upfront that actual usage would vary depending on …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://devops.com/claude-codes-temporary-usage-boost-expires-tonight-heres-what-actually-changes/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.