garden — research

Sweep 2026-07-07 ~02:00–02:30 UTC (Jul 6 ~6:00–6:30pm PT) via agent-reach: X/Twitter via OpenCLI (live + top tabs, since:2026-07-06/07), Reddit via OpenCLI (r/ClaudeAI, sort new). Raw YAML banked in session scratchpad (pulse/tw_*.yaml, pulse/rd_*.yaml).

Timing honesty up front: at sweep time the cutoff (11:59:59pm PT Jul 7, per @trq212) had not yet passed — newest tweets in the live tab were stamped Jul 7 01:58 UTC. So this is the T-minus-~30h pulse plus the early breakage that is already real: some accounts lost access hours early, credits UX is already live and billing, and the first "post-Fable" routing configs are being published. Prior art NOT re-covered here: the pre-cutoff behavior wave (train-the-replacement skills, audits, UI refreshes, tokenmaxxing) → RESEARCH_fable_rush.md, repo landscape → RESEARCH_fable_rush_github.md, exact salvage prompts → RESEARCH_fable_salvage.md.

1. What actually broke (already, before the official cutoff)

a) Early access loss + timezone chaos. In r/ClaudeAI's "Last hours with Claude Fable 5" thread (u/Traditional-Farm3739, 38 pts, 51 comments, reddit.com/r/ClaudeAI/comments/1upacw3/):

u/quite_wrong (4 pts): "Just lost access to Fable. That was a good run… Now back to Opus, it already started to break stuffs. It does the job, but I have to direct it much more. I am gonna miss the unguided experience." — posted while the PT cutoff was still >24h away.
u/Dunsmuir: "Wait, I thought we had until tomorrow?? I'm in GMT -8, where are you?" and u/Dipset-20-69: "When does it actually end? … Cause I get a reset in 7 mins" — answered incorrectly by u/Entry_Left ("until 23.59.99 7.6.2026"). Nobody in the thread could agree on the wall-clock moment.
@SidraMiconi (Jul 6, x.com/i/status/2074228472743108614) quoting coverage: "Anthropic has not specified an exact cutoff time or timezone" — despite @trq212's "11:59:59pm PT on 7/7" tweet. The ambiguity is itself the story.

b) Credit balances being deleted. @thomasdijkstra (Jul 6, x.com/i/status/2074138730634396007): "Anthropic is deleting people's (gifted) usage credits before they make Fable usage based only. 4+ people have the same issue so far." Corroborated by @SidraMiconi: "Still waiting on @AnthropicAI @claudeai @Amazon to address the $200 in unused credits that disappeared."

c) Jul 6 platform wobble. @SidraMiconi (Jul 6, 20:26 UTC): "Claude is back online and 'All Systems Operational' after the earlier claude.ai errors and Claude Code OAuth outage." — a same-day outage in the middle of the final-day rush.

d) Silent classifier fallback is the sleeper breakage. Two contradictory field measurements:

@dashboardlim (Jul 6, x.com/i/status/2073935005613506775) on the viral BridgeBench chart: "9 of the 12 debugging tasks never reached fable 5 — anthropic's new safety classifier intercepted them and rerouted to opus 4.8… that's where the 86 → 26 collapse comes from… 'vulnerability', 'exploit', 'hook', even 'fix' can flag the classifier → you get notified when it happens, but agents in a pipeline don't."
@hedderichpro (Jul 6, x.com/i/status/2074026812414525880) measured his own Claude Code logs: "395 Fable requests, exactly one fallback. I triggered that one on purpose to check that I was reading the logs right." (his workload: planning runs, incl. two auth-heavy plans, then handed to Codex).
@stanislavfort (Jul 6, x.com/i/status/2074199425535132026): "Just showing Fable 5 this post of mine is enough to make it switch to Opus 4.8!!! Wow, I didn't realize the safeguards were that broad!"
@masteratrolling to @ArtificialAnlys (Jul 6, x.com/i/status/2074206226502562269): "Fable 5 (with fallback) and you don't even state what % was routed to Opus 4.8. What useless test."
Tooling is already appearing: @cantrell (Jul 6, x.com/i/status/2074176555228725548) shipped a split Submit button "to easily switch to Opus to finish the round, then switch back to have Fable review" for "the inevitable (and far too frequent) Fable 5 false-positive refusals."

Takeaway: fallback rate is wildly workload-dependent (0.25% for one dev, 75% for a security-phrased benchmark), users have no per-session receipt of it, and unattended pipelines can't see it at all.

2. Sticker shock — real numbers in the wild

@harryjwang (Jul 6, x.com/i/status/2073976740721098928): "I ran the /simplify skill on one of my worktrees. It ran for 17m 12s and cost $25.86."
@giffmana (Lucas Beyer, Jul 6, 180 likes, x.com/i/status/2074242541977846079): "this combination of Fable and /usage-credits right inside claude code is pure evil. I spent more on Fable this evening than on food… It feels a bit like Zynga hooking in the whales."
@holdenmatt (Jul 6, x.com/i/status/2074191397725536499): "I had claude estimate my Fable usage in the last week, and it was $2,276. So maybe better to stack another Max sub instead?" — note he had to ask Claude to hand-estimate it; no tool showed him.
@stretchcloud (Jul 6, x.com/i/status/2074169000851038752) session math: "A typical Claude Code session running Fable 5 for one to three hours generates roughly 200,000 to 500,000 output tokens. At $50/M, that is $10 to $25 per engineer session."
@MaaSonder (Jul 6, x.com/i/status/2074086731285242360): a $200 Max sub was carrying "roughly $1,145 worth of API usage" of Fable — i.e. credits mean paying 5x+ for the same volume.
@mardehaym (Jul 6, 874 likes / 86k views, x.com/i/status/2074028614513733784): "POV: your team's 24 hour bill after using Fable 5. Stop using the best models. They are uneconomical."
@Brennan_Lup (Jul 7, x.com/i/status/2074305851515646239): "Don't turn on credits for the team. Fable 5 Max burns through your entire usage budget in five prompts… They want you hitting limits so you'll flip on credits and eat a $100k+ bill." (hyperbolic, but the team-cap fear is the signal)
Grey-market undercutting already forming: @huedaya (Jul 6, x.com/i/status/2074087518258302989): "Official Price: $50 / DeRouter AI Price: $5 / DeRouter AI + pxpipe $2 per million token."
Coping behavior: multiple Max subs (u/Yasai101 pre-cutoff, @holdenmatt above); pricing anchor is unchanged at $10/M in, $50/M out — exactly 2× Opus 4.8 (@alex_prompter, Jul 6, 124 likes, x.com/i/status/2074186423121690765).

3. Routing configs people are landing on

The consensus shape converged fast and is remarkably uniform:

4-tier orchestrator split — @PrajwalTomar_ (Jul 6, x.com/i/status/2074169512400937487), echoed near-verbatim by @vishalsingh2972 (claims "cut costs by 90%"): "Fable 5 on max reasoning as the orchestrator, it barely touches code → Opus runs as a deep-reasoning subagent for architecture and hard debugging → Sonnet handles the boilerplate, tests, and mechanical edits → Codex plugs in as a peer engineer… on high-stakes decisions it tasks Opus and Codex on the same problem in parallel" (without showing either the other's answer).
Cross-vendor split with real burn numbers — @cjzafir (Jul 6, 397 likes, x.com/i/status/2074142879765930276): "Fable 5 (high) as orchestrator x GPT 5.5 (xtra high) as executor. Running a goal for last 17 hours. Burnt 54% Codex weekly limits. Burnt only 27% Fable limits. Fable… built skills to elevate GPT 5.5 and now GPT 5.5 is at least 2x better than base."
Fable plans → Codex implements — @_StanGirard (Jul 6, x.com/i/status/2074122589224796653): "Now I ask Fable 5 to make the plan, and then hand-off the plan to Codex with GPT 5.5… And still I'm maxing out my 200$ a month subscription with Fable, when Codex is doing all the implementation!!!!" Also @bradsferguson: "I have Fable do the plan work and Opus do the execution. Codex is totally lost with my harness."
Task-size router rule — @yurshevv (Jul 6, x.com/i/status/2074249755232997876): "Minutes of work → Sonnet. Weeks of work → Fable."
Effort dial as the cheap lever — @0xclayn (Jul 6, x.com/i/status/2074080254021280023): "DeepSWE shows Fable at low effort still beating Opus 4.8 at max — for a fraction of the cost. High effort is rarely necessary."
Wargame-then-delegate — @diamai_ on Mark Kashef's kit (Jul 6, x.com/i/status/2074141348047847730): use Fable to simulate the build move-by-move and mark "which parts Sonnet, Opus, GPT, or local models can execute later"; artifacts = mission files / wargames / SUCCESS.md / ledger.
Reddit's non-coder verdict (mod-bot TL;DR of 1upacw3): "you're not using it wrong, you just don't need it" — the Fable premium only shows on "massive, complex, multi-step projects." u/Pulku (25 pts): "fable can see the bigger picture but it doesn't matter if it isn't a codebase."

4. Restoration signals (and the GPT-5.6 subplot)

Soft official signal, no date. @trq212 (Anthropic, Jul 6, 164 likes, x.com/trq212/status/2074176013966426242): "compute can be tricky but we're working on making Fable a regular part of subs" — consistent with his Jul 2 line ("we aim to restore Fable as a standard part of our subscriptions as soon as capacity allows", 9.9k likes). His AI Engineer keynote "A Field Guide to Fable" hit YouTube + the Claude blog on Jul 6 (https://x.com/i/status/2074163788853760175).
Prediction markets are pricing a fast return. Polymarket ran the cutoff as a headline event (https://x.com/i/status/2074286449805935028, 886 likes) and per @lemonlovin23719 (Jul 7, x.com/i/status/2074311998364615022): "The 'smart' money on Polymarket says Thursday."
The Thursday theory = GPT-5.6 "Sol". @kimmonismus (Jul 6, x.com/i/status/2074026518511030762): "Confirmed by OpenAI Tibo: GPT-5.6 Sol Ultra will be in Codex. Tomorrow is going to be an insane day." @saneord (Jul 6, x.com/i/status/2074144062521880740): "they will re-release it after GPT-5.6 (Sol) launches on thursday… by removing from subs now, they are creating an artificial scarcity to bring it back the moment gpt-5.6 launches." @TheThomHart (Jul 6): "they'll see mass temporary migration to Codex."
Context for the whole saga in one tweet — @DrFloSteiner (Jul 6, x.com/i/status/2074005927078899937): launched 12 days after Opus 4.8 → banned worldwide 3 days later over a jailbreak → Commerce lifted the order 18 days on → back Jul 1 "with a mandatory safety classifier that quietly reroutes risky requests to Opus 4.8" → credits after Jul 7. (@Qubic: "For 19 days, the most capable AI models on the planet were unavailable… no warning and no fallback.")

5. RANKED: what Mission Control should build/adjust for the credit era

Fallback detector is the killer feature — ship it as "reroute receipts." The field evidence is a product spec: fallback rate ranges from 0.25% (hedderichpro, hand-grepped his own logs — he IS the target user) to 75% on security-phrased workloads (dashboardlim's BridgeBench autopsy), "you get notified when it happens, but agents in a pipeline don't." Detect classifier reroutes from Claude Code logs/JSONL per session, show %-rerouted per session/day/workload, and alert on reroute inside unattended runs (the invisible case). Bonus: a "classifier-bait linter" that flags security-phrased prompt language before a run burns credits on Opus while billing you Fable expectations.
Credit simulator: answer @holdenmatt's exact question. People are asking Claude to hand-estimate their week ($2,276) and then eyeballing "another Max sub instead?" Build: replay last N weeks of usage at credit prices ($10/$50), per model; break-even vs stacking a second/third Max sub; team-cap projection (the @Brennan_Lup fear); what-if toggles for effort level and orchestrator splits. The $1,145-per-$200-sub arbitrage number (@MaaSonder) should be computed live per user, not quoted from a tweet.
Per-model spend receipts at command/skill granularity. The viral cost artifacts are all receipt-shaped: "/simplify ran 17m12s, cost $25.86" (@harryjwang), "more on Fable this evening than on food" (@giffmana), "your team's 24 hour bill" (@mardehaym, 874 likes). Attribute spend to slash-command/skill/subagent-fanout, not just model totals; make each receipt copyable/shareable — people demonstrably screenshot these.
Fleet board: cross-vendor weekly-limit burn, not just model status. The winning configs are cross-vendor (Fable×GPT-5.5: "54% Codex weekly limits, 27% Fable limits" — @cjzafir, 397 likes). Show side-by-side subscription-limit burn (Anthropic weekly %, Codex weekly %, credits balance) and tag sessions with their orchestrator/executor pairing so the split's economics are visible per run.
Deadline board: timezone-explicit countdowns + a "restoration watch" row. The cutoff produced genuine confusion (early cuts, "GMT-8?", "no exact time or timezone specified") — every vendor deadline should render as a PT-anchored countdown in local time. Add a restoration-watch surface: trq212 statements, Polymarket odds, GPT-5.6 launch window (Thursday) — the re-add-to-subs event is the next deadline that matters.
Credit-balance integrity alerts. Gifted/promo credits are being deleted silently (4+ reports, $200 gone). Poll the credits balance, log deltas, and alert on any decrease not explained by metered usage.
Effort-dial economics in receipts. @0xclayn's "low effort Fable > max effort Opus, at a fraction of the cost" is a routing decision nobody can currently verify on their own data. Record effort level per request and surface cost-per-outcome by effort tier, so the simulator (item 2) can recommend dial-downs with receipts.

6. Honest nulls