Anthropic cuts Claude Code weekly limits 17%, users measure a bigger drop

Seventeen percent is the number Anthropic put on it. BleepingComputer reported that Claude Code’s current weekly limits are being cut by that much, and the number landed into a subreddit that had already spent two days arguing the real figure was larger. One user posted overnight that a single 30-minute audit session consumed 52% of their weekly Fable budget with prompt caching enabled and fresh sessions throughout. Another, posting early on the 21st, reports the same model and same prompt draining a Max plan at different rates depending on time of day, which is the kind of claim that is either a measurement artifact or a load-shedding policy nobody has documented. The session-log audit that circulated on the 18th, putting the effective drop at 60 to 70 percent rather than 17, still has no rebuttal with numbers attached.

The pricing argument has a technical twin that surfaced in the newsletters the same day. AlphaSignal’s Ben Dickson walked through the harness-cost gap: two developers running the same model on the same coding task can pay very different inference costs depending on whether they drive it through Codex, Claude Code, Pi, or something homegrown, with the spread reaching 5x. The finding that should reorganize how people pick a stack is that simple harnesses stay competitive, elaborate ones often buy small quality gains at substantial token cost, and a model does not reliably perform best inside its own vendor’s harness. That last point cuts against the default assumption behind every first-party agent CLI, and it arrives while everyone is watching their quota drain.

Alibaba open-sourced OpenCodeReview, a code review CLI built on a split most agent tools get wrong: deterministic pipelines handle file selection, bundling, and rule matching, and the LLM agent is confined to dynamic analysis of what those pipelines hand it. Built-in checks cover null-pointer exceptions, thread safety, XSS, and SQL injection. Putting selection and bundling in code rather than in the model is the cheap half of the harness-cost problem above, and it is worth reading the pipeline boundary even if you never run the tool.

Google shipped agent infrastructure on two fronts. Agent Development Kit for Kotlin reached 1.0 with feature parity against the Python and Java kits, plus Android-specific paths for on-device and hybrid inference, which makes it the first of the three ADKs that can put an agent loop on a phone. Separately, an open agentic orchestrator out of Google drew 104 points and 40 comments on Hacker News inside a few hours, with the discussion turning mostly on how its execution model compares to the orchestration layers teams have already hand-rolled.

The Jev conversation refuses to die down a week after launch. Sean Goedecke argues that System One models can train their own replacements: a fast general classifier you can prompt for anything from triaging Slack messages to playing Doom solves the two problems that keep teams from building bespoke classifiers, which are the missing ML skillset and the missing labeled dataset. Run Jev in production, keep its outputs, and you have the dataset for a small hand-built classifier that will be cheaper and faster than the general model it replaces. Independent testers are already publishing comparisons; one r/vibecoding post benchmarked Jev against classical models across 8 classification datasets, and a Jev-backed MCP server offering semantic code search inside Claude Code appeared on r/ClaudeCode the same evening.

On the model side, Qwen released Qwen-Image-2.1, pitched as a compact unified model for image creation and editing, and it took 120 points on the Hacker News front page with 42 comments. Compact is the operative word given where the rest of this issue sits.

What to watch: whether Anthropic publishes the accounting behind the 17% figure, or whether the gap between the stated cut and the measured one keeps widening with nobody reconciling it.

Feed note: the local mirror reported a stale last-sync timestamp, but daily ingest is current through 2026-09-21; item dates above are from the feed.