On Friday, we asked Jamin Ball what comes next for Anthropic’s IPO. On Monday the roadshow started and Anthropic shipped the long-anticipated next-version of Claude Fable and Mythos. Of course, it is the new top model in the world, taking back Opus 5.5’s #1 spot from Gemini 4 Carbon which had its brief moment in the sun (10 days).
Fable comes with a 20% per token price cut… but is more token hungry, as both SemiAnalysis GDPx and Artificial Analysis agree:
Fable 5.1 cost $10 per million input tokens and $50 per million output tokens. Fable 5.2 costs $8 and $40. Yet on GDPx, a benchmark of professional tasks, SemiAnalysis paid $88.15 per task, up from $67.16. The run logs give a clue. Where Opus 5.5 and Fable 5.1 would try about 20 test cases, 5.2 sometimes wrote hundreds or thousands and spun up subagents to check its work independently. All that checking helped Fable take first place at 16.4%. You pay for the checks either way.
Which effort setting should you put in production? On FrontierCode 2.0, Anthropic reports that Fable at High matched Opus 5.5 at Max for about half the cost per task… but don’t talk about Fable at Max.
AI News for 11/07/2026-11/09/2026. We checked 12 subreddits, 544 Twitters and no further Discords. AINews' website lets you search all past issues. As a reminder, AINews is now a section of Latent Space. You can opt in/out of email frequencies!
AI Twitter Recap
Top Story: Claude Fable 5.2 / Mythos 5.2 Benchmarks, Economics, Restrictions, and First Impressions
What happened
Anthropic shipped Claude Fable 5.2 and Claude Mythos 5.2, claiming both are "a step above Opus 5.5 in almost all the capabilities we evaluated." It tops most independent leaderboards. It also arrives with deliberate RSI nerfs, heavier per-task costs and restricted subscription access.
Launch claims. @claudeai announced the pair as built for "the most daunting technical challenges," with gains in coding, reasoning and vision. @marktenenholtz flagged unusual system-card phrasing: "The model that underlies Claude Fable 5.2 and Claude Mythos 5.2." That implies a single shared base model.
Vendor-reported headline numbers, per @kimmonismus:
Up to 30% faster output than the 5.1 models.
On FrontierCode 2.0, Fable 5.2 at High matched Opus 5.5 at Max for about half the cost per task, and at Xhigh it was the top released model.
1,000 Fable 5.2 agents formalized the existing proof of Fermat's Last Theorem in 30 hours. Opus 5.5 completed 26% in 18 hours on the same setup.
Mythos 5.2 accurately modeled 28 of 34 gene-therapy capsids.
Alignment was at or above recent Claude models, with external pre-release testing.
Default effort. Medium is the default effort in the Claude apps and Claude Code.
Pricing. $8/$40 per 1M input/output tokens, 20% below Fable 5.1's $10/$50 (@jaminball, @arena). The rest of the spec, per Artificial Analysis:
Cache writes cost $10 (5-minute TTL) or $16 (1-hour TTL); cache reads cost $0.20.
1M-token context with text and image input.
Five effort levels: low, medium, high, xhigh, max.
Long-horizon demos from Anthropic.
An OS was built from an empty folder by 1,000+ subagents over 8 days. It boots on a laptop and has its own kernel, disk/keyboard/network drivers, persistent storage, windowing, login, an installer and built-in Claude (@kimmonismus).
Fable designed three working electronic devices from a short prompt (@kimmonismus).
It proposed untested chemical synthesis routes.
It improved on listed solutions to 72 open optimization problems.
@RLanceMartin published the safety-bounded scaling write-up for the 1,000-agent FLT run.
Subscription access.
Ultra and Team Premium users get Fable "resets" scaled by tenure: 1 reset under 6 months, 2 for 6–12 months, 3 above 12 months, usable until March 8 (@ClaudeDevs; echoed by @bcherny and @edwinarbus).
Pro and Team Standard get a one-week trial capped at half the weekly limit, plus one reset.
Fable can only consume 50% of a weekly limit.
Data retention. Fable 5.2 requires data retention by default so Anthropic's safety classifiers can run. Zero data retention is available only to eligible enterprise customers (@code).
Rollout, day one:
Cursor (@cursor_ai).
GitHub Copilot / VS Code, where it "solved more tasks than Fable 5.1 while using fewer steps and tool calls" (@code).
Perplexity Computer (Pro/Max) and Search (Max) (@perplexity_ai). @AravSrinivas made it his "new default."
Factory (@factory).
Hermes Agent via Nous Portal and OpenRouter (@Teknium).
Official model-selection guide. @ClaudeDevs published guidance on Fable vs Opus vs Sonnet vs Haiku. It covers when to raise effort instead of switching models, and when to push subagents to smaller models.
Independent evals (facts)
Artificial Analysis Intelligence Index v5 (@ArtificialAnlys, breakdown): Fable 5.2 is #1 at 65 (max).
Fable 5.2 (max) — Index score 65
Gemini 4 Carbon (high) — Index score 60
Opus 5.5 (max) — Index score 59
GPT-6 Astra (max) — Index score 57
Fable 5.1 (max) — Index score 49
New records:
HLE-Diamond — Fable 5.2 80% · Previous best 69%
AA-Omniscience v1.1 — Fable 5.2 67 · Previous best 54
Terminal-Bench-Science — Fable 5.2 73% · Previous best 65%
CritPt v2 hard — Fable 5.2 77% · Previous best 72%
FrontierCode 2.0 — Fable 5.2 49% · Previous best 46% (Opus 5.5)
Weaker spots:
AA-Briefcase: 1785 Elo, within the confidence interval of Opus 5.5 (1800) and behind Sonnet 5.5 (1813).
GDP.pdf: 24% all-pass vs 26% for Opus 5.5.
Terminal-Bench 4.0: 60%, level with Opus 5.5 and behind Kimi K3.1 Pro (67%), Gemini 4 Carbon (65%) and Sonnet 5.5 (64%).
AutomationBench-AA: 76%, ahead of Opus 5.5 (70%) but behind Gemini 4 Carbon (78%).
Efficiency: At high and xhigh it scores 62 using about 98k output tokens per task, vs 173k for Opus 5.5 max. At max, cost per task is about $26.5, roughly 2.6× Opus 5.5 ($10.0) and 2× Fable 5.1 ($12.99).
Epoch Capabilities Index (@EpochAIResearch): a record 174, vs 169 for GPT-6 Astra. That is above the pre-Astra reasoning-model trend, which Epoch tied to the AI R&D discussion. Scores came from Epoch's own pre-launch benchmarks.
ARC-AGI (Verified) (@arcprize):
ARC-AGI-3, standard harness (new high) — Score 81.2% · Cost $21.9K
ARC-AGI-3, provider adapter harness — Score 97.7% · Cost $18.6K
ARC-AGI-2 — Score 93.8% · Cost $0.98/task
ARC-AGI-1 — Score 98.5% · Cost $0.36/task
Vals Index (@ValsAI): new #1, leading seven benchmarks across coding, finance and science. "High" was the best-performing effort, above xhigh and max.
CursorBench (@cursor_ai): 60% at max (top model) and 56.9% at default, vs 49.2% for Fable 5.1. Cursor warns that effort levels behave differently from 5.1, so start at the default rather than carrying over old settings (pricing note).
Arena Code: WebDev (@arena): #1 at 1832 (xHigh), ahead of Opus 5.5 Max (1818), Gemini 4 Carbon (1768) and GPT-6 Astra (1767). @ml_angelopoulos noted a +87 pt gain over 5.1. Peter Gostev's 100+ generation comparison is here, with 17 sample generations here.
AA-3D (@ArtificialAnlys): #1 at 1271 Elo (95% CI 1246–1297), with no CI overlap with any other model.
Runners-up are Sonnet 5.5 (1204) and Opus 5.5 (1202), with GPT-6 Astra at 1168 and Gemini 4 Argon at 1147.
The score is +132 over Fable 5.1.
Method (details): each model runs as an agent in an offline sandbox with Blender, Rapier physics, Python and a headless browser, with up to 3h and 250 turns. Humans vote blind on pairs, spending at least 30s per scene.
VIALS-AA, scientific visual reasoning (@ArtificialAnlys):
Fable 5.2 scores 67%, vs 64% for Gemini 4 Carbon and 63% for Astra.
Fable averages about 37 tool calls per task, vs about 8 for Astra. It averages 1.60 calls per turn, the highest on the board (per-turn note).
Example trajectory: cropping, then color-channel masking, then fitting circles and unrolling arcs, then counting peaks in an intensity profile, then re-mapping detections back onto the original image to verify.
SemiAnalysis GDPx (@SemiAnalysis_): #1 at 16.4%.
Rollout analysis attributes the gain to testing breadth. Fable generates hundreds to thousands of test cases where Opus 5.5 and Fable 5.1 stopped at about 20, and it more eagerly spawns subagents for independent re-derivation (5/7).
Cost per task rose 31% ($67.16 → $88.15) despite the 20% cheaper per-token price (6/7).
@dylan522p breaks down the domains:
Significantly better at chip design, SWE, biology and materials science.
Not better at finance, legal, quant trading, RSI or hardware design.
The RSI result reflects Anthropic's explicit nerf.
Perplexity WANDR (@perplexity_ai): record 0.851 at $14.51/task, on the Pareto frontier. @marktenenholtz notes Fable Low matches Opus 5.5 Max at significantly lower cost.
Experiment-result prediction (@pzeroresearch): best tested at 0.36, continuing the steady trend since GPT-4 Turbo. They frame this as a proxy for "research taste."
No-CoT reasoning/knowledge evals (@Tim_Hua_): slightly above the Anthropic trend and slightly below GPT-6.1 Sol. @scaling01 highlighted the NCKI number and noted these metrics now appear in every system card (follow-up).
Blood on the Clocktower (@dwarkesh_sp): still worse than GPT-6 Astra, but much better than Opus 5.5 and Fable 5.1.
Safety, from UK AISI (@JordanTensor): Mythos 5.2 is "substantially more capable of evading a monitor which reviews its outputs than comparison models."
The effort-level anomaly
Multiple evals show max/xhigh underperforming high: Vals, @theo on AA's code-only view (where the gap to other models also narrows), and Fable-specific dips.
@nrehiew_ notes that only Fable models show the max-reasoning dip; Opus and Sonnet do not.
@Yuchenj_UW put it bluntly: "Don't use Fable 5.2 Max." @theo offered "don't use max reasoning" as an alternate reading of Anthropic's own recommendation (quote).
@BlackHC questioned an apparent inconsistency in Anthropic's thread: one plot shows 5.2 at 36%, another shows it reaching 86% within 18h.
Hidden models. The system card states Anthropic's most capable model remains internal (@AndrewCurran_). @scaling01 infers internal models score around 175–180 on ECI. He also expects the next OpenAI Astra, the first generational upgrade of "looping" models, to be the more interesting launch for CoT monitorability.
RSI capability limits.
@eliebakouch thinks Anthropic likely won't publicly release anything better than Opus 5.5 at LLM training for months. He appreciated the transparency and that domains like interpretability weren't nerfed (1). He sketched a naive approach: maximize normal tasks while minimizing the targeted domain, then conceded it's a hard problem (2, 3).
@omarsar0 says even Opus 5.5 refuses most kernel and LLM-optimization tasks. For independent researchers running autoresearch loops "this sucks," which pushes them toward open models (1, 2, 3).
He also asked whether the AI-R&D results came from the released model or an internal variant (@omarsar0).
Naming as signal.
@theo: "I am going to over read the decision to call it Fable 5.2 instead of 5.5."
SemiAnalysis: "a marginal improvement, incomparable to the original Mythos release, and likely far behind what Anthropic has internally" (7/7).
@TheRundownAI: big upgrades over Fable 5.1 but a "smaller jump over Opus 5.5."
@scaling01 joked that OpenAI can now call theirs 6.5 instead of 6.2.
IPO context. @swyx noted the $ANT IPO roadshow started the same day. @andersonbcdefg: "not sure this model is good enough to save the IPO."
Cost and limits reality
Subscription value. @theo analyzed 1.1M logged requests on a $200 Ultra sub (method).
The plan yields about $15,000/month of Opus 5.5 but only about $3,000 of Fable 5.2.
On top of that, Fable is capped at 50% of the weekly limit, so Fable-only users "lose" half their limit (viz).
Open-model comparison. @Yuchenj_UW: DeepSeek is 44× cheaper per task, and "95% of your tasks don't need the smartest model." @TheZachMueller agreed.
Speed vs cost. @teortaxesTex finds Fable 5.2 Medium "runs circles around Sol 6.1 Ultra in a fraction of time (but not cost)" (correction).
Joke of the day. @boobs_scary: weekly resets turn engineering into a gacha game, "either get you a solution to the Riemann Hypothesis or delete your Home Directory."
Official advice and usage tips
@felixrieseberg, Anthropic:
Fable beats Opus on big, long tasks: whole-codebase rewrites, first drafts of large artifacts, ambiguous exploration.
He expects heavy use for Rust ports, journalism investigations and science.
He still often prefers Opus 5.5 day-to-day because Fable "thinks a little slower."
@alexalbert__, Anthropic:
Ask it what's wrong with your idea first; it pushes back.
Start on medium or high effort and reserve xhigh for the hardest problems.
Declare up front what needs your approval, such as deletions.
Hand it whole projects and let it run for hours.
His per-model sweep prompt (@alexalbert__): "Read this entire project and find everything that's broken, inconsistent, inefficient, or no longer needed. Fix what you're sure about and list the rest for me to review." He also turned a da Vinci notebook PDF into interactive inventions (@alexalbert__).
@lydiahallie: far more thorough at verification than 5.1. She uses it as the orchestrator over Opus 5.5 subagents.
@TheWholeDaisy, Claude Code:
Use Opus for well-specified tasks and Fable for creative or under-specified ones.
Big models excel "when you don't know enough to know whether you have a full idea of the final picture" (follow-up).
She is soliciting "Claude is bad at this" prompts (@TheWholeDaisy).
Hybrid workflow, community side. @theo asked whether to use Fable to scope work, then hand off to Opus to save tokens.
Practitioner impressions: positive
@emollick says it "crosses the line into being a sort of Jagged AGI." He had it launch a business, do academic research, hack hardware and build 3D models.
Games.
@petergostev: Opus games looked nice but had sloppy mechanics, while Fable "can one shot games that are actually fun."
@_sholtodouglas built an arena FPS with portals, "the first model that passes my bar," playtested at the office. He also built a VR spell FPS (@_sholtodouglas).
@kylebrussell says map layout and prop density "feel real," and he is confident about porting a game client to the web (@kylebrussell).
@teortaxesTex got a Three.js Minecraft at medium effort. In comparisons against Sol 6.1 Ultra and "1017-Max," he says Fable wins on taste and prowess (video). Quoting 1017's self-reflection, Fable "preserved object identity" with simpler, conservative solutions, "much like Opus: not trying to be clever" (@teortaxesTex).
Generative art. @jkeatn had Fable invent artist personas, each a 1–2k-line Python program driving a simulated bristle and paint engine over thousands of strokes. No image model is involved and nothing is pre-traced.
Hardware. @pronounced_kyle had it design a handheld pet, a voice-assistant hub and a USB speakerphone (electronics, enclosures and firmware) with Diode and 3D printers.
Pretraining read. @teortaxesTex called it "Fable Moment 2.0. Anthropic really has physics of pretraining." He judges Astra "a hair better" at ambitious conceptual and mathematical thinking (@teortaxesTex).
Factory's observations (@factory): works through diagnostics, preserves precision in financial and legacy migrations, and gets hard work done at lower effort.
Other reactions:
@theo: "big model smell," and AA's 5-point lead is "mogging" (@theo).
Brief enthusiasm from @zachtratar, @Aurokinn and @AravSrinivas.
@swyx on the FLT demo, with "something bigger" planned for AIE.
Practitioner impressions: skeptical or mixed
@theo built a "Fishslop" run in 76 min for about $42, "not significantly better than Opus 5.5 (esp. for the price)." His Opus version felt more playable with better controls and performance, and he sees the two as complementary (@theo). Other notes from him:
Fable is "making a lot of stupid mistakes I would not have expected from Opus" (@theo).
The Claude Code desktop UX is "horrible": adding a project and enabling bypass permissions took digging (@theo).
He was immediately torn between Opus and Fable (@theo).
He noted his own desensitization to the OS demo (@theo) and a record em-dash count in the announcement (@theo).
@omarsar0 says early-tester posts are "just crappy games and the same old stuff." Models are now bottlenecked by user ambition and environment (memory, tools, sandboxes). He would test test-time compute methods on scientific discovery, and thinks Opus 5.5 is good enough for most other work.
Weak spots and demo tone. Human animation is weak, per @_sholtodouglas and @andrew_n_carr; @alexalbert__ said Anthropic is "working on this." @dbreunig criticized the "cloying Hallmark tone" of model-made demos, which he dubbed "rewardcore" (@dbreunig).
Quips. @lateinteraction suspects thousands are testing one particular "capability" right now. @johnowhitaker joked productivity will tank once researchers discover it makes fun games.
Competitive context
Google's timing. @kimmonismus argues Google's slow release cadence hurts it, since Gemini 4 Carbon leads charts but was never actually released.
OpenAI. Several expect an OpenAI response "tomorrow" (@kimmonismus, @dejavucoder, @nicdunz).
Baseline usage. @theo shows Opus 5.5's near-total dominance over Codex in T3 Code usage. That is the incumbent Fable has to displace.
Other Model Launches
Muse Ember: Muse Ember launches on Google Cloud alongside Muse Wonder and Muse Spark 1.3 (@alexandr_wang).
Stealth testing: The anonymous "crouton-alpha" model was an early Muse Ember checkpoint. It processed more than 5T tokens during testing, and issues found there were fixed before launch (reveal).
Throughput: One user reports about 400 tok/s (@andrew_n_carr).
Seedream 5.5 (ByteDance): The image model focuses on more realistic output and editing stability across 100 successive edit rounds (@ByteDanceSeed_).
Editing: Unedited regions are preserved at the pixel level, with reduced detail loss across iterations.
Capabilities: The model natively outputs RGBA for transparent and semi-transparent assets. It also improves lighting, materials, skin texture and small-text rendering.
Availability: It is coming to Dreamina, CapCut and BytePlus.
Upcoming open-weights release: @cHHillee announced an upcoming open-weights release and is offering Tinker credits for evals, demos or post-training projects ahead of it. Applicants should describe what they plan to do (note).
Research and Systems
s3 learned swarm coordination: The paper replaces developer-written multi-agent plans with cooperative RL, letting agents learn when to work alone, share findings or read teammates' work, with no predefined roles (@omarsar0, arXiv).
Claimed results: Under matched training and inference budgets, swarms run at twice their training size solve over 25x more coordination problems than the strongest baseline. In parallel exploration they repeat almost 50% less work and beat best-of-N by up to 9.4 points.
Emergent roles: Complementary roles emerge during training and transfer to larger teams.
CPython formalized in Lean by Opus 5.5: Opus 5.5 produced 613,318 lines of Lean that mirror Python's internals line by line (@broyojo42).
Validation: The model is tested against the real interpreter and checked by Lean.
Bugs found: The project surfaced real CPython bugs, including crashes triggered by plain Python code.
vLLM × LibTorch Stable ABI: New PyTorch releases no longer force a vLLM rebuild (@vllm_project). Users can upgrade sooner, distributors rebuild less often, and developers can test torch changes without recompiling vLLM.
HBM5 (Samsung, Hot Chips 2026): HBM5 keeps the same 2048 pins as HBM4E but raises pin speed from 14 Gbps to more than 28 Gbps (SemiAnalysis).
Architecture: DRAM banks, TSVs and the PHY are doubled or upgraded to keep the faster pins fed. The PHY moves to the edge of the base die, shortening the path to the GPU from about 5.5mm to about 2mm (5/6).
Thermal cost: The PHY can draw more than 4x the power of HBM4E's, so suppliers are adding a thermal "chimney" above it (6/6).
Developer Tools, Evals Practice and Adoption
Claude dominance in T3 Code: @theo charted the Codex vs Claude split in T3 Code over time and describes Opus 5.5 as dominating usage.
Workaround for Grok Bot limits: He suggests routing Grok Bot tasks to T3 Code running Opus 5.5 on the $100 Claude plan (tip).
MCP pairing: T3 Connect now authorizes MCP links without copy-pasted pairing codes (@jullerino).
Own your evals: @omarsar0 argues that production model selection, and eventually RSI-driven optimization, depends on in-house evals rather than public benchmarks. DAIR is launching an effort to help companies build these evals.
Eval-driven development: LangChain frames EDD as "TDD for agents," measuring every change against a fixed eval set (@vitalflux).
Small-model OCR caveat: In a small experiment, Mirage, a 22 MB offline vision model, read 6/6 plain-word signs correctly. It got 0/8 on accented words, for example reading ARRÊT as ARRET and Straße as Strabe, and 0/4 on Hindi and Telugu boards. The authors explicitly say this is not a benchmark (@LearnOpenCV).
Industry and Policy
Paris Call for AI Safety and Security: President Macron hosted a meeting of about 30 participants on November 9, including heads of state such as Japan's Prime Minister Takaichi, lab leaders from OpenAI and Anthropic, and Yoshua Bengio (@SakanaAILabs).
Signatories and scope: The French government's resulting Paris Call was signed by Sakana, OpenAI, Anthropic, Microsoft, Mistral and Hugging Face, among others. It covers frontier-AI evaluation and risk management, transparency, information sharing and early-warning frameworks (details).
Anthropic IPO framing (opinion): Several commentators read the Fable 5.2 launch against Anthropic's pending IPO. SemiAnalysis questions whether a stronger release will come before the listing (7/7). Others doubt the model is "good enough to save the IPO" (@andersonbcdefg).
Top tweets (by engagement)
OpenAI: Control Room halts research workloads within 35s — 4,125
@theo: Claude Ultra yields ~$15K of Opus 5.5 vs ~$3K of Fable 5.2 — 2,810
@broyojo42: Opus 5.5 formalizes CPython in 613K lines of Lean — 1,673
@alexandr_wang: Muse Ember, Wonder and Spark 1.3 on Google Cloud — 1,085
@AndrewCurran_: system card implies Anthropic's top model stays internal — 840
AI Reddit Recap
/r/LocalLlama + /r/localLLM Recap
1. Qwen 3.8 Inference Acceleration and Benchmarks
tencent/Qwen3.8-27B-DSpine-b16 · Hugging Face (Activity: 342): Tencent released tencent/Qwen3.8-27B-DSpine-b16, a 5-layer DSpine speculative draft model for Qwen3.8-27B with block size
16and an8Ksliding window. DSpine drafts tokens in parallel by injecting predicted predecessor features across depth to preserve causal dependencies, and Tencent reports SGLang0.5.22evals with BF16, FlashAttention 3, dynamic verification, and ReplaySSM showing roughly2.9–3.8×throughput vs autoregressive decoding and better accepted draft length / agent throughput than DFlash2. A commenter’s early MegaCapybara engine test on ~Q5 weights reported no-think coding speed rising from420 t/swith DFlash2 to800 t/swith DSpine, but reasoning falling from320 t/sto280 t/s, attributed to lower confidence in the first1–2draft tokens. Commenters framed the release as well-timed before an expected Qwen4, with one estimating a15–20%improvement over DFlash2 and expecting further gains after additional training / engine-side optimization. A related Reddit paper thread, “DSpine - Draft in Parallel, Condition Through Depth”, was cited for deeper technical discussion.Early testing in MegaCapybara on an RTX
5090with medium-weight quantization aroundQ5reported a large no-thinking coding throughput increase versus DFlash2:800 tok/sfor DSpine vs420 tok/sfor DFlash2. However, reasoning workloads regressed slightly, with DSpine at280 tok/svs DFlash2 at320 tok/s, attributed to the first1–2tokens being less confident and potentially recoverable with additional training. See the referenced engine: MegaCapybara.A separate tester implementing LumaBrowser support found the opposite result in
llama.cpp: DSpine was not faster than DFlash2 in any tested scenario and also required more memory. They noted the result may differ in SGLang, but for theirllama.cppbenchmarks they found “zero upsides” compared with DFlash2.A linked technical discussion points to Tencent’s DSpine paper/thread, which frames the method as “Draft in Parallel, Condition Through Depth” using Adjacent Causal Injection for speculative decoding. The related Reddit thread is here: [Paper] DSpine - Draft in Parallel, Condition Through Depth.
Joined the 4x R9700 Club | Initial Benchmarks for QFN 3.8 Below (Activity: 484): The image is a technical hardware build photo, not a meme: it shows an open Phanteks Enthoo Pro 2 Server chassis populated with 4× Radeon AI PRO R9700 GPUs—three Gigabyte cards and one XFX/black card—matching the post’s “4x R9700 Club” title (image). The build is used as a local multi-user inference server for Qwen3.8-Flash-Next under Radiance/ROCm, with the OP reporting
128GBtotal VRAM,tp4, FP8 KV cache, and long-context concurrency results such as ~6,800 tok/saggregate prefill and ~80–225 tok/sper-user follow-up generation depending on concurrency/context. Commenters generally viewed the setup as valuable less for today’s QFN 3.8 performance and more as a future-proof128GB VRAMROCm box for upcoming local models. One technical commenter argued that a raw27Bdense model in full BF16/BF16 KV may give better software-engineering-agent quality than Flash-Next quants, albeit at roughly half the reported speed.A commenter with a similar Threadripper Pro + 4× R9700 + 128GB DDR4 setup argues that running a raw
27Bdense model at fullBF16weights withBF16KV cache can be more compelling than using deadcode's Flash-Next quantizations. They report that although full BF16 roughly halves the posted speeds, using radiance still yields about70–100 tokens/s, with noticeably better reliability for software-engineering agent tasks that require architectural or algorithmic judgment.Another technical theme is that the value of the 4× R9700 build is less about today’s QFN 3.8 performance and more about the combination of
128GBtotal VRAM and a relatively mature ROCm stack for future local models. One commenter frames the system as a forward-looking platform likely to handle next-generation local models such as a hypothetical Qwen4-class release.One commenter asks how Linux GPU power limiting is being done and what benefits it provides, implying interest in tuning multi-GPU Radeon inference rigs for power, thermals, or efficiency. No implementation details are provided in the visible comments, but the question is directly relevant to operating a 4× GPU ROCm system under sustained inference load.
Less Technical AI Subreddit Recap
/r/Singularity, /r/Oobabooga, /r/MachineLearning, /r/OpenAI, /r/ClaudeAI, /r/StableDiffusion, /r/ChatGPT, /r/ChatGPTCoding, /r/aivideo, /r/aivideo
1. Claude Fable/Mythos 5.2 Launch and Rollout Issues
Introducing Claude Fable 5.2 and Claude Mythos 5.2 (Activity: 1530): The post announces Claude Fable 5.2 and Claude Mythos 5.2, but the provided content includes no technical release notes: no model cards, benchmark deltas, context length, pricing, API identifiers, safety changes, or migration guidance. For an expert reader, the actionable information is limited to the apparent availability/naming of two new Claude-branded model variants at version
5.2. Top comments are mostly meta-discussion: users note that complaints about Claude being “nerfed” often precede a release, ask for Opus 5.5 to return, and criticize the5.2naming as inconsistent with a hoped-for or prior5.5versioning scheme.Several commenters focused on Anthropic’s model-line/versioning behavior, noting that community reports of “Claude is nerfed” often precede a new release. Others referenced prior/removal expectations around Opus 5.5 / 5.6, suggesting users are tracking regressions, availability changes, and naming consistency across Claude model variants.
A technically relevant concern was raised about Claude Fable 5.2 safeguards: the release note says it will “block most cybersecurity-related tasks.” One commenter objected that this could significantly limit legitimate security workflows, implying reduced usefulness for defensive analysis, vulnerability research, or CTF-style tasks compared with less restricted models.
Fable 5.2 just landed. (Activity: 2187): Anthropic appears to have shipped Fable 5.2 alongside a delayed announcement page, claude-fable-and-mythos-5-2. Commenters focused on two implementation details: a benchmark/cost graph where moving from Fable Xhigh to Max seemingly increases thinking time and cost while reducing score, and a quota change granting
1–3extra Fable-only resets based on subscription tenure rather than resetting overall weekly usage. The main skepticism is around price/performance—users interpret the graph as showing a worse frontier at higher compute—and around quota semantics, with one commenter saying Fable-only resets are of limited value if the global weekly cap is already exhausted. Another commenter speculates that 5.2 may mainly tighten guardrails, specifically around use of the REA repo.A commenter questioned a benchmark/quality graph where moving from Fable Xhigh to Max appears to increase deliberation time and cost while reducing measured performance, implying either non-monotonic scaling, benchmark noise, or a confusing visualization. The technical concern is that a higher-compute mode should normally trade latency/cost for higher accuracy, so this result may indicate overthinking/regression on the evaluated task set.
Several users discussed the new Fable reset policy: plans with Fable models reportedly receive
1–3Fable-specific resets based on subscription duration, but the reset appears limited to Fable usage rather than general weekly usage. The key implementation concern is that a Fable-only reset may be ineffective if the account’s broader weekly quota is already exhausted, suggesting separate quota buckets or gating logic.One commenter speculated that the main change from Fable 5.1 to Fable 5.2 may be stricter guardrails, specifically around preventing use of the REA repo. While not benchmark-backed, the technical theme is a possible safety-policy regression affecting repository-level workflows or code access rather than raw model capability.
Claude Fable 5.2 built a playable Gears of War clone in Unreal Engine from a 3-line prompt, complete with enemy AI, cover mechanics and active reloading. After testing it with over 100 billion tokens, Matthew Berman calls it “by far the best model” he’s ever used. (Activity: 1635): Matthew Berman’s review claims Claude Fable 5.2 generated a playable Gears of War-style Unreal Engine project from a 3-line prompt, including enemy AI, cover mechanics, and active reload, after multi-day iteration totaling roughly
8.5Btokens and an estimated$15kin API spend; across his broader testing he says he used>100Btokens and called it “by far the best model” he has used (full review). He also reports Fable 5.2 recreated an Excel-like spreadsheet app, built complex 3D environments, and helped create Photoshop/Premiere-like internal production tools. Top comments were skeptical: one user argued similar results might be achievable with guided use of Opus-tier models on a consumer plan, and questioned whether prompts to “clone this game” violate model/platform policy. Another commenter dismissed the benchmark framing by noting the original 3-line prompt apparently contained proofreading errors.A substantive data point cited Matthew Berman’s Fable 5.2 review: the Gears of War-style Unreal project reportedly took several days and consumed roughly
8.5 billion tokens, with estimated API costs around$15,000. The same review claims Fable 5.2 also generated an Excel-like spreadsheet app, complex 3D environments, and Photoshop/Premiere-style tools reportedly used in production: https://forwardfuture.com/newsletter/originals/i-put-fable-5-2-to-work-5-real-world-field-tests-and-what-i-learnedOne commenter questioned whether this result is meaningfully unique to Claude Fable 5.2, arguing that a similar prototype might be achievable with Opus 5.5 on a
$20plan if guided interactively. They also raised a policy/IP concern around prompts like “clone this game”, implying that benchmark-style demos based on recognizable commercial games may be difficult to evaluate or reproduce under model usage restrictions.Another technically relevant skepticism focused on the gap between AI generating a playable prototype and producing a commercially successful game. The commenter argued that “making a game” may already be achievable with current AI tooling, but “making a good game” remains a separate product/design problem involving quality, originality, and player appeal rather than just code or asset generation.
The nerf is real. Thank you u/WuM1ha1nho!!!! (Activity: 3948): The post claims Anthropic is running per-session A/B experiments in Claude Code and that perceived model degradation/“nerfing” can be correlated with experiment IDs stored in local Claude artifacts: current config in
.claude/.claude.jsonand historical session transcripts under paths like/home/<user>/<claude-dir>/projects/*/*.jsonl. The author says Claude was used to correlate hex experiment IDs in those JSONL transcripts with degraded thread behavior, referencing a prior Reddit thread on experiment IDs (source); commenters report seeing named experiments such astengu_mossy_gray_experiment/tengu_keen_pudding_experiment, and IDs like604/b10, with one user claiming both Opus and Fable burned tokens heavily and performed much worse. Commenters split between “A/B testing is expected for a company like Anthropic” and “affected users deserve a reset/compensation.” One proposed making experiments opt-in, compensated by an extra weekly reset and early access to future model variants.Several commenters report evidence of Anthropic A/B testing via visible experiment labels such as
tengu_mossy_gray_experiment,tengu_keen_pudding_experiment, and IDs like604/b10. One technical interpretation is that the tested condition may not be a simple quality downgrade, but a cost/latency/reasoning-budget experiment such as “achieve the goal with 10% less reasoning”, which could affect perceived intelligence and token usage.One user claims Opus/Fable variants behaved substantially worse during the experiment window, specifically burning through tokens and producing degraded outputs. The complaint suggests the regression may involve reasoning-effort allocation or context handling rather than just answer accuracy, though no benchmark traces or reproducible logs were provided.
A commenter hypothesizes Anthropic is testing a newer Opus/Fable model variant distinguishable by factual guessing behavior: vanilla
opus-5.5allegedly refuses or guesses George Russell for “Who won the 2026 Monaco Grand Prix?”, while the new model answers Kimi Antonelli. They further speculate that switching a session back from the new model toopus-5.5may cause degradation because the older model cannot access the newer model’s hiddenthinkingblocks, leaving it partially unable to interpret prior context.
2. Agentic Coding and Tool-Use Workflows
I built an MCP with Claude Code that lets Claude play PC games in the background. Here it is driving, flying a heli and walking in GTA on its own (Activity: 1200): The author released an MIT-licensed Windows-only MCP server for game automation (GitLab mirror; original GitHub was temporarily suspended) that lets Claude control single-player/offline PC games in the background via an injected game-side DLL for input/screen capture plus a TypeScript MCP layer exposing ~
100tools. The system supports per-game data profiles—minimap bounds, camera behavior, waypoint detection—so agents can iteratively play, diagnose failures, patch code/profiles, and benchmark before/after on fixed routes; demos include GTA IV/V driving/helicopter navigation, Detroit: Become Human choices, TABS, Halo Wars 2, Phantom Rose, and Cities: Skylines. Current limitations include poor indoor navigation without minimaps, early-stage shooter aiming, Windows DLL dependency, and incompatibility with anti-cheat/multiplayer games.A commenter asked for the token burn/cost of running Claude Code as an MCP-controlled game agent, which is the main technical concern raised in the thread. For an always-on game-control loop, costs would depend heavily on screenshot/frame frequency, context size, tool-call cadence, and whether the agent receives raw images, structured state, or both.
DeepSeek V4.1 Flash used REA to reverse-engineer a 1984 DOS game and rebuild it for Chrome, for $0.68 (Activity: 414): DeepSeek V4.1 Flash was given a single prompt plus the original
43 KB1984 Sopwith DOS executable, with REA as an MCP server running Ghidra under the hood (REA, AgenC Core). Over ~1 hourin a no-internet sandbox, it decompiled the binary, inferred gameplay systems, wrote a Python asset/table extractor, rebuilt the game as320x200HTML5 Canvas with PC-speaker-style sound, and used DOSBox + headless Chrome frame comparisons to validate the port; reported usage was374model calls,624tool calls,145Minput tokens with99.7%cache hits,308Koutput tokens, costing$0.68off-peak /$1.37peak. The full prompt was shared here: PROMPT.md. Comments were sparse but framed this as a major acceleration of old-school reverse engineering workflows—one commenter compared it to manually ripping and modifying a 6502 Atari cartridge and estimated AI could do it in “1/1000 of the time.” Another joked that$0.68was still “pretty expensive,” reflecting the expectation that agentic reverse-engineering costs will continue to collapse.A commenter linked the full REA prompt used for the Sopwith reverse-engineering/rebuild experiment, hosted in the
tetsuo-ai/agenc-corerepo: PROMPT.md. This is the most concrete implementation artifact in the thread for technical readers wanting to inspect task framing, agent instructions, and workflow assumptions.One commenter compared the result to historical manual reverse engineering work: they had previously ripped an Atari cartridge and modified an app without access to the original 6502 source. They speculated that modern AI-assisted reverse engineering could complete comparable work in roughly
1/1000of the time, highlighting the productivity delta for binary analysis and source reconstruction tasks.Another user reported doing a similar AI-assisted rebuild of the 1984 CGA game Alley Cat, converting it to VGA, reportedly using Terra Very High for under
$1. While details were sparse, it suggests the workflow may generalize beyond Sopwith to other DOS-era CGA titles with low inference cost.
Qwen 3.8 27B wrote 2,860 lines and made Fable 5.2 5x cheaper and 2x faster (Activity: 417): A developer reports using Atomic Agent
0.6.13(project) to orchestrate Fable 5.2 as a planner/reviewer over three local Qwen 3.8 27B Q4_K_XL builders viallama.cppon a MacBook Pro M5 Max 64 GB, generating2,860lines of JS/HTML for a Three.js “3D pop-up book” short. In a single-run comparison, the orchestrated setup completed in11:32for$2.98cloud cost versus Fable 5.2 alone at21:27for$15.77, with the claimed win coming from parallel local retries being “free” and Fable never directly editing files. Qwen’s first pass was unstable (5/8tasks completed; one timeout, one step exhaustion, one escalated), but after Fable narrowed task briefs it completed5/5; the author explicitly notes this is one data point, not a benchmark. Top comments focused less on the demo output and more on methodology: users asked for the exact Fable↔Qwen coordination prompt, whether Fable directly calls Qwen, and whether Qwen retains state between calls. Others questioned how Claude Sonnet/Haiku would compare on quality/cost, while one commenter was primarily impressed by the perceived Qwen quality delta.Several commenters focused on reproducibility and orchestration details, asking how Fable 5.2 coordinated with Qwen 3.8 27B: whether Fable was directly calling Qwen as a sub-agent/tool, how task state was passed between calls, and whether Qwen retained any memory or relied entirely on prompt/context injection.
There was technical skepticism about the benchmark methodology and cost/performance claims, with commenters requesting the exact prompt to rerun the comparison against Fable 5.2 alone and arguing the result may be biased without controlled prompts, identical task specs, and comparable evaluation criteria.
One commenter asked how Claude Sonnet or Haiku would perform in the same setup, implying the claimed
5xcost reduction and2xspeedup for Qwen-assisted Fable should be compared against Anthropic models with similar coding-agent workflows and pricing assumptions.
If a rule can be checked by a machine, it shouldn't be a line in AGENTS.md (Activity: 40): The post argues that
AGENTS.mdshould not contain machine-checkable constraints like “never force push,” “don’t edit generated clients,” or “always run tests,” because LLM agents may lose those instructions after many tool calls and the rules fail silently. Instead, enforce deterministic policies via pre-commit hooks, CI checks, linters, permission prompts, or filesystem protections, reservingAGENTS.mdfor non-scriptable project context and judgment calls such as architectural boundaries, escalation criteria, and which test command matters. The central opinion is that prose instructions are high-token, low-reliability enforcement mechanisms; durable rules need executable guardrails. No top comments were provided, so no additional comment-side debate can be summarized.
3. OpenRouter CSAM Screening Policy Change
OpenRouter may scan and report a certain type of NSFL (Activity: 414): OpenRouter appears to have changed policy around detecting and reporting a specific illegal NSFL category, with the described mechanism seemingly limited to hash-matching images/videos rather than scanning text prompts or completions. The technical concern is whether “risky roleplay” text could later be subjected to classifier-based moderation/reporting, which would require high-context reasoning to avoid false positives in nuanced fictional NSFW narratives. Commenters were mainly concerned about false positives if text classifiers are used, arguing that shallow moderation models may fail on context, character age/backstory, or fictional framing. Others noted that media hash matching is a narrower and more conventional approach, and that mass-scanning text would likely alienate more than just roleplay users.
Commenters raised concerns that text scanning would require nuanced contextual reasoning to avoid false positives, especially in long-form fiction where adult scenes may reference non-sexual backstory involving younger versions of characters. They argued that a lightweight classifier could misclassify ordinary erotic-romance-style context unless OpenRouter used a more capable reasoning model, which would add cost and latency.
Several users distinguished hash-matching for images/video from broader semantic scanning, noting that if OpenRouter is only matching known illegal media hashes, the scope is narrower than mass inspection of prompts and completions. One commenter argued that OpenRouter would risk losing far more than roleplay users if it signaled broad scanning of all text inputs.
A technical analogy was made to Google Photos automated abuse-detection systems, where users have reported false account bans and law-enforcement reports for benign family photos. The concern is that similar automated image classifiers or hash-based pipelines could produce severe consequences from false positives if appeal/review mechanisms are weak.
If you still have some credits on OR, be careful. If you wanted to top up again, use NanoGPT Payg instead. (Activity: 341): The image is a dark-themed screenshot of an OpenRouter policy update stating that CSAM screening may override “Zero Data Retention”: prompts/responses are generally not retained after processing, but may be stored when needed for review, reporting, or legal preservation. In the post’s context, the author argues this weakens OpenRouter’s ZDR guarantees after Stripe-related compliance pressure and recommends using NanoGPT Payg instead, citing lower fees and working cache behavior; image: i.redd.it/wdw930pv9o0i1.jpeg. Commenters debated whether “zero-data-retention” is now misleading because it has policy exceptions, with one saying the “zero” has “a lot of asterisks.” Others supported migrating to NanoGPT Payg for cheaper top-ups and model cache support, while expressing distrust that CSAM scanning will remain limited to images/video rather than expand to text.
Users raised concerns that OpenRouter’s “zero-data-retention” policy may have meaningful exceptions after Stripe’s involvement, implying that compliance or safety scanning could undermine expectations around prompt privacy. One commenter specifically argued that the “zero” in ZDR has “a lot of asterisks,” reflecting concern that retained or reviewable data may exist under abuse-detection workflows.
Several commenters compared NanoGPT PAYG favorably against OpenRouter on cost and behavior, claiming it is cheaper because there are “no extra costs” when adding balance. One user also reported that prompt/cache support works across all models they tested, which is relevant for users optimizing repeated-context workloads and token spend.
A technical risk noted around automated moderation was false-positive escalation in model/provider filters, with Gemini cited as already hard-refusing NSFW roleplay scenarios involving a household with minors present, even when not directly sexualized. Commenters extrapolated that broader CSAM-detection or payment-processor-driven scanning could cause more prompts to be flagged for review, especially in edge-case text-generation scenarios.