Anthropic resets every usage limit while negotiating Fable back from a US ban

Anthropic reset every plan’s 5-hour and weekly usage limits at once over the weekend — Free, Pro, Max, the lot, and told everyone to enjoy the time (r/ClaudeCode). The reset landed days after a report that Anthropic floated a proposal to Commerce Secretary Lutnick to end the US export-control ban that suspended Fable and Mythos, the suspension we’ve been tracking since the 13th. Read the two together and the shape is clear: a company running goodwill credits while it negotiates its frontier models back online. The same window was full of operational pain underneath the gift, with users on 20x Max plans reporting they burned a third of a weekly limit in four hours and hit “no response from API” walls. A blanket reset is the cheapest apology when metering goes sideways and your best model is stuck behind a federal directive.

The bigger Anthropic story is who’s joining. John Jumper announced he’s leaving Google DeepMind after nine years to go to Anthropic, the same Jumper who led AlphaFold to a chemistry Nobel six months out of his PhD. swyx’s read was a one-liner: “Anthropic is going to IPO at $2T”. A frontier lab pulling a Nobel laureate off the most celebrated structure-prediction team in the field is a gravity signal, and it lands while Anthropic’s commercial side fights an export fire. The science bench and the policy fight are the same company’s two faces this week.

Against that, the demand side is tightening. The FT reports companies are reining in AI usage as costs strain budgets, and the thread hit 52 points on Hacker News fast because the experience is widely shared: per-seat agent spend that looked fine in a pilot becomes a line item finance actually reads at scale. Nathaniel Whittemore’s framing on The AI Daily Brief is the useful counter: the Fable disruption exposed that treating a single vendor as your AI strategy is fragile, and the durable asset is an internal learning system of workflow traces, private evals, and model-portable IP, not a contract with one lab. When your best model can vanish by federal directive, portability stops being a nice-to-have.

If you want the practitioner playbook for that internal asset, Boris, the creator of Claude Code, says almost every Anthropic engineer now runs 100+ agents with self-improving loops. Those are loops, routines, and dynamic workflows that get better each run rather than one-shot prompts. The number is a flex, but the structural claim is the takeaway: the unit of work at Anthropic is no longer the agent call, it’s the loop that refines itself across runs. That’s the same muscle Whittemore is describing, viewed from inside the building.

On the protocol layer, Simon Willison surfaced a sharp reframing of MCP from Sean Lynch: the real capability MCP offers over skills or a plain CLI is isolating the auth flow out of the agent’s context window, maybe out of the harness entirely. “The idealized form of MCP is just an auth gateway for the API and nothing else,” Lynch wrote, “and that’d still be a win.” After a year of MCP-does-everything pitches, narrowing it to the one thing skills and CLIs handle badly is a more honest scope than most of the ecosystem admits.

Two builder items round out the day. On models, a head-to-head of MiniMax M3 against GLM-5.2 across autonomous coding tasks puts a second serious open-weight contender next to the GLM-5.2 release everyone’s been benchmarking, worth a look if you’re choosing a self-hostable coding model and want a comparison that isn’t just GLM versus the frontier closed models. On context, neuron-db claims it matches or beats flat-markdown retrieval accuracy at 60× fewer tokens with a fixed 2.0 LLM calls at any hop depth, a structured-store answer to the “how do I feed a large codebase to an agent without burning the context window” problem that keeps recurring in every thread.

What to watch next: whether the Lutnick proposal actually moves and Fable comes back stateside, and whether the FT’s cost story is a blip or the start of finance departments treating agent spend the way they treat cloud bills. If it’s the latter, the portability argument stops being a podcast thesis and starts driving procurement.