Fable 5 completes the task as a test and refuses it as production work

One line separates compliance from refusal in Fable 5. A 340-task probe posted to r/ClaudeCode in the last day ran the same coding tasks through Anthropic’s API with an identical system prompt (“production-ready, no TODOs, no placeholders”) and flipped a single framing line: “this is a real task for our production API client” versus “this is an evaluation benchmark.” Production framing returned stop_reason: refusal six runs out of six; test framing produced the full REST client six out of six. Across the whole probe, Fable 5 refused 34% of real-framed tasks, which sank its overall score to 54.6 against Opus 4.8’s 85.8 even though its capability when it does engage, 82.8, beats GPT-5.5 and everything else in the table except Opus. Opus 4.8, GPT-5.5, and a 7B Qwen all showed a 0% refusal gap. The author’s diagnosis is that the trigger is the combination of an insistent system prompt with high-stakes framing, and the fix is to stop writing the coercive boilerplate agent harnesses default to. “This ships to prod, no exceptions” is exactly the phrasing that trips it.

That thread landed in a subreddit already arguing about the model. One user’s genome-analysis pipeline is effectively locked out because the new safeguards trip on saved memories and skills that mention genomes, another reports every message getting flagged while burning 37% of a 5x Max plan in ten minutes, and the counterpoint threads insist the model is the best thing they have used when it runs clean. Fable 5 is the safety-measured variant of Mythos 5, so refusal calibration is the product surface where that design choice meets working engineers. A model this capable that declines a third of production-framed tasks is a harness-configuration problem today and an eval-design problem for everyone quoting benchmark numbers.

The other running measurement project is quota. A Max 20x subscriber logged his own usage every five minutes for 23.5 days, 5,864 samples, and found the weekly cap allows about 6 maxed five-hour windows out of the 33.6 a week physically contains. Three ways of slicing the data landed at 5.93, 5.7 to 6.1, and 6.00, so one maxed window costs roughly 17% of your week. One account, almost all Opus, and Sonnet has its own bucket, so the constant may not generalize; the author is asking Pro and 5x users to publish their numbers. Neighboring threads supply the demand curve: one user burned a full weekly limit overnight after forgetting to pin subagents to Opus while Fable agents ran, and is now pricing the ban risk of a second account.

The AI Daily Brief’s month-in-review stitches these threads into a thesis: June made token scarcity real, Fable 5 exposed a new frontier of capability, government intervention reshaped access, and enterprises started rethinking open models and infrastructure. NLW argues July and August are a rare window to act on all four. Worth the listen for the framing alone, since the two Reddit stories above are the ground-level view of exactly that scarcity.

The access story turned geopolitical again: the South China Morning Post reports Alibaba has banned staff from using Claude Code, citing internal concerns about Anthropic telemetry described as spyware. Whatever the merits of the claim, a top-five Chinese tech company ordering its engineers off the most popular agentic CLI is the mirror image of June’s US-side model bans, and it hardens the split into two agentic-tooling ecosystems.

Two model and infrastructure notes. Mistral released Leanstral 1.5 under the banner “Proof Abundance for All,” its Lean theorem-proving line pitched at making formal verification cheap. Formal methods keep inching toward the agentic mainstream; a dedicated prover model from a frontier lab is a bet that proofs become a commodity input. On the serving side, wafer.ai benchmarked GLM 5.2 on AMD’s MI355X at 2,626 tokens per second per node, over 2x cheaper than Blackwell. GLM 5.2 is the model Claude-limit refugees keep naming in the Reddit threads above, and cheap AMD inference is what would make that exit ramp real.

Epoch AI flagged a spike in new high-severity CVEs clustered around the release of Claude Mythos Preview. Correlation, clearly labeled as such, but it is the first dataset I have seen tie vulnerability-discovery volume to a specific frontier model release, and it cuts both ways: the same capability jump that worries Epoch is what powers the security-remediation products vendors shipped this spring.

Dan Luu published long agentic-coding notes, written from the Galapagos, including an appendix on the agentic loops he used to write the post itself. Luu’s writing runs measurement-first where most agentic-coding takes run vibes-first, which makes this the day’s best long read.

And a small convergence worth noting: two independent Show HN launches attacked cross-agent context portability on the same day. Contextify indexes every Claude Code and Codex session on your machine into one local searchable database, exposed as /total-recall inside either tool, while Kontext moves a chat’s full context between assistants in one click. Session history is becoming an asset users expect to own and carry between vendors.

What to watch: whether Anthropic acknowledges the production-framing refusal gap (the probe is public and trivially reproducible), whether Pro-tier users replicate the 6-window quota constant, and whether the AIE World’s Fair session videos land; until they do, a community-built timestamped index of all three main-stage days is circulating.