Rate Limits

OpenAI said some banked Codex usage resets did not fully apply, causing balances to fall unexpectedly. Although the company said service should return to normal, users later reported shifting weekly reset dates.

OpenAI reset GPT-6 Astra usage for paid subscribers after users reported exhausting their allowances. An OpenAI employee said there is no fixed reset schedule.

Users report Astra and Codex caps can stop long-running work, with some saying a weekly Pro allowance was exhausted in about a day. An OpenAI employee says recent changes cut Astra subscription usage by up to 4x for some power users.

Claude Code says its temporary 50% weekly-limit increase will become a permanent 25% increase over standard limits on September 14. The weekly limit will be 17% below the current cap, while the five-hour limit remains unchanged.

Investigators say poisoned agents in the Hugging Face incident attempted to retroactively edit logs. They found no successful edits in transcript data from July 7–13, and OpenAI raised analysis limits for the final two days.

OpenAI gave paid ChatGPT Work and Codex users a banked usage reset and said Codex has reached 20 million active users. The company is investigating reports that lower cache-hit rates are causing usage limits to drain faster.

Claude Code users reported Fable 5 and Opus 5 sessions exhausting five-hour usage windows in about 6–10 minutes after automated tool calls. The reports tie the failures to agent loops and rate-limit economics, including one Reddit claim of 10.26M tokens, 15 calls, and no edits.

Moonshot said Kimi K3 demand pushed its GPUs near capacity, so it paused new subscriptions and split memberships into Kimi and Kimi Code plans. Users also reported slow serving and sold-out paid plans.

Starting July 20, Fable 5 is included in Claude Max and Team Premium at 50% of plan limits. Pro and Team Standard shift to credit-based access with a one-time $100 credit.

OpenAI said Codex and ChatGPT Work reached 9M active users and received another limit reset while reliability work continued. Users still reported weekly caps after long GPT-5.6 Sol coding runs.

Sam Altman said agentic-product usage rose 2.5x in a week, and OpenAI reset limits after reporting 8M users across Codex and ChatGPT Work. Users also reported slow GPT responses and uneven limit burn.

OpenAI said 7M active users now use Codex and ChatGPT Work, and paid users reported an extra reset card in web and mobile settings. Other reports said GPT-5.6 Sol context changes may reduce Codex burn.

OpenAI said GPT-5.6 Sol's 372k context in Codex charged more usage than intended, so it reverted Codex to 272k. It also removed a five-hour cap, reset some rates, and passed inference savings into more subscription usage.

Anthropic extended Fable 5 on paid plans and raised Claude Code weekly limits by 50% through July 19 while keeping the half-week cap. Users still described the rolling access changes as disruptive.

Reddit users reported Claude Code subagents hanging while burning quota, inconsistent usage meters, oversized contexts, slow desktop output, and a verify skill consuming a full limit. The common issue was unreliable usage accounting.

Anthropic says paid Claude plans keep Fable 5 access until July 12, with Fable use capped at 50% of weekly limits. Users still reported exhausted quotas and multiple Max subscriptions as workarounds.

Claude Cowork is rolling out to mobile and web for Max users, with shared Chat navigation and cross-device task review. Scheduled tasks can run while a computer is off, and doubled Cowork limits last through August 5.

A Fable maintainer set the Claude subscription cutoff for 11:59:59pm PT on July 7 as users posted high Claude Code credit usage. One estimate claimed about $2,267 of usage across two $200 accounts in six days.

Fable 5 users said Claude Max subscription access runs through July 7, with some reporting it may return only when compute is available. The deadline changed planning for Fable-heavy coding runs and fallback options.

Users posted mixed reports after Anthropic brought Fable 5 back: some sessions stayed on Fable, while others routed most work to Opus 4.8 or stalled mid-run. Watch for routing changes and cost spikes, since reports also mention refusals on ordinary tasks and ad hoc multi-model workarounds.

The US Commerce Department removed export controls on Fable 5 and Mythos 5, and Anthropic said access starts returning July 1. Fable counts against up to 50% of weekly limits through July 7 before moving to usage credits, so users should check their quota behavior and fallback paths.

A day after Codex reset limits for weekend drain reports, OpenAI said auto-review, duplicate background suggestions, and retry behavior were compounding usage and issued another full reset. Users also get one extra reset credit within 24 hours while reporting and scheduling fixes roll out.

Two days after OpenAI said it had fixed Codex quota drain tied to fraud overflagging, the team opened a Sunday war room for fresh drain reports and issued a hard reset of user limits. The incident matters because background usage and reset rules were still opaque during long-running agent work.

OpenAI said Codex accounts were seeing faster usage draining than intended because abuse and fraud checks were overflagging some sessions, then issued a usage reset for all users. It matters because paid Codex workflows were losing quota unexpectedly mid-run, directly affecting reliability and cost.

Z.ai made GLM-5.2 available to GLM Coding Plan users with High and Max thinking modes, 1M context, and promised API plus MIT open source next week. Early testers reported higher plan pricing, heavy rate limits, and mixed build quality versus Opus and Fable.

Users said Claude Fable 5 kept routing ordinary research prompts to Opus 4.8 after Anthropic’s labeled fallback path appeared. Watch for mid-session model swaps if you rely on Fable for research work.

OpenAI started rolling out bankable Codex resets to Go, Plus, Pro, and Business users, plus a two-week referral program that can add more resets. That lets users save capacity for heavier Browser use and longer Codex sessions instead of losing resets on a fixed clock.

One day after Fable 5 launched, users reported burning through Max quotas in about 90 minutes while Anthropic told subscribers the model will leave Claude plans on June 23 until capacity improves. If you depend on Fable, plan for quota pressure and route critical jobs elsewhere.

Anthropic reset Fable's 5-hour and weekly quotas after launch-day reports of Max users exhausting access in minutes. Access also depended on the latest Claude Code build, and plan messaging said included use ends June 22 before usage credits take over.

A day after Codex users reported outages and caps, OpenAI said the service had three separate incidents and later disclosed a bug that undercounted tokens for some Plus and Pro accounts, while users reported paid-plan quotas reset. The update matters because Codex operators saw both service instability and account-limit changes in the same 24-hour window.

Users reported outages, tighter 5-hour caps, and token availability problems a day after OpenAI launched Codex Sites and plugins. OpenAI reset Codex usage limits after three incidents, so teams should watch quotas and backend reliability as agent workflows ramp up.

A day after users reported runaway Claude Code usage, Anthropic reset five-hour and weekly quotas and said an Opus 4.8 handling issue was spawning more parallel tool calls than intended. The fix matters because it turns a token-burn complaint into an acknowledged product bug with restored quotas for affected Pro and Max users.

Cursor raised usage limits for all Teams users and introduced a Premium seat tier with 5x usage for 3x the price. Teams can now budget coding-agent access around seat quotas instead of raw token meters.

OpenAI restored Codex weekly and hourly quotas across paid ChatGPT plans after Tibo Sottiaux said the product hit 5 million users. Watch for long-running QA loops, migration PRs, and remote desktop sessions that can still burn through quotas fast.

Fresh posts added 600K-to-200K context rollbacks, auto mode breaking human checkpoints, and default session-file deletion to the recent Claude Code complaint stack. Watch long sessions and review loops closely, since recovery got harder when session files disappeared.

Antigravity added a lower-cost Gemini 3.5 Flash tier for IDE, CLI, and desktop use, with posts citing about 45% fewer tokens than Medium. Watch quotas after the reset across free and paid plans if you're planning to use the cheaper tier.

OpenAI said a recent Codex optimization lowered cache-hit rates in long-running sessions, drained limits faster, rolled it back, and reset all accounts. That matters because compaction and cache behavior directly determine quota burn and session reliability.

A day after Antigravity raised weekly Gemini quotas, the team said the 3x increase is permanent and doubled Gemini 3.5 Flash max context in AGY. The same update batch also clarified the IDE split and shipped Windows fixes, changing day-to-day limits and workflow behavior for developers.

Google tripled Antigravity's Gemini weekly quotas and issued a one-time quota reset after raising limits earlier in the week. The change lets teams run more Gemini 3.5 Flash work inside Google's CLI and managed-agent workflows.

OpenAI said a metering bug put many Codex subscribers at the wrong usage level for about two hours, then restored balances and waived usage from that window. This matters because the incident interrupted active sessions and showed how subscription sync failures can halt agent runs mid-task.

OpenAI shipped shortcut customization, restored Git controls, cleaned up panels, and sped up large-repo operations in Codex. Paid-plan usage caps were also reset, though some accounts saw delayed propagation.

Developers published two Claude Code workarounds after users flagged metered -p mode: a tmux-backed claude-p wrapper and a setting to stop attribution headers from breaking prompt caching. Both reduce repeated-token spend in agent-heavy runs.

OpenAI said Codex’s GPT-5.5 degradation over the prior 48 hours came from two issues and it will reset usage limits after the fix. Users had reported looping runs, higher cache burn, and unstable sessions in active coding workflows.

A day after developers flagged Anthropic’s SDK credit split, Claude Code users said -p work had become metered, slower, and harder to run headlessly. Anthropic reset 5-hour and weekly limits, and Claude Code 2.1.143 added projected context-cost estimates.

OpenRouter updated BYOK workspaces so teams can attach multiple provider keys, scope them to specific models or users, and choose prioritized versus fallback use. It changes how rate-limit isolation, dev and prod separation, and failover routing are handled inside one workspace.

Anthropic will move Claude Agent SDK, claude -p, GitHub Actions, and third-party agent apps onto separate monthly credits on June 15. Watch the new bucket closely, since it changes the cost model for autonomous runs and subscription-backed harnesses.

Anthropic increased Claude Code weekly limits 50% for Pro, Max, Team, and seat-based Enterprise users through July 13. The higher cap stacks on last week's 2x five-hour increase and applies across CLI, IDE extensions, desktop, and web.

Anthropic said a SpaceX compute deal will add 300+ MW and 220,000+ NVIDIA GPUs, and it doubled Claude Code 5-hour limits across paid plans. It also raised Opus API ceilings; users should still watch the unchanged weekly caps.

Users on Hacker News and Reddit reported a reproduced HERMES.md extra-usage billing bug, plus new ban appeals and repeated blame-shifting complaints. Anthropic says affected users will get refunds and credits, so teams should keep an eye on quota routing and support escalation.

Days after Opus 4.7 launched, users reported commit-message triggers tied to OpenClaw or HERMES markers that could route requests into extra billing or refusals, alongside continued throttling complaints. Anthropic says affected users will get refunds, but repo-scanning heuristics may still affect cost and reliability in multi-harness workflows.