a quiet day.

AI News for 8/31/2026-9/1/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: Fable 5.1 and Mythos 5.1 release and reactions

What happened

Anthropic launched Claude Fable 5.1 and Claude Mythos 5.1 as its new flagship models for coding and knowledge work.

Anthropic announced the release directly, positioning them as “the world’s most advanced models for coding and knowledge work” via @claudeai
Anthropic product/engineering voices framed Fable 5.1 specifically around autonomous, multi-step work: “complex, multi-step work that runs on its own,” with emphasis on coding, knowledge work, and long-running problem solving via @mikeyk
Anthropic kept list pricing for Fable 5.1 at $10 / $50 / $12.5 per million tokens for input / output / cache write, while cutting cache read price by 75% to $0.25 / MTok, again noted by @mikeyk, @Teknium, and independently quantified by @ArtificialAnlys
Third-party platforms moved quickly: Perplexity added Fable 5.1 to Computer for Pro/Max users and published internal eval results via @perplexity_ai; Nous Portal/Hermes Agent and OpenRouter also added support via @Teknium; T3 Code shipped support via @theo
Early benchmark screenshots and system-card excerpts drove much of the discussion, especially around Terminal-Bench-Science, SWE-family evals, HLE, FrontierCode, and Artificial Analysis via @StevenDillmann, @scaling01, @ArtificialAnlys
A key interpretive claim emerged from community analysis: Fable and Mythos 5.1 may be the same underlying weights, with different safety/routing behavior, not different base models, per @eliebakouch and later @nrehiew_
User reactions split along multiple axes: very strong praise for coding/planning ability and tone, but complaints around rate limits, safeguards false positives, subscription UX, and unclear benchmark presentation via @danshipper, @theo, @kimmonismus, @GregKamradt, @kylebrussell, and @eliebakouch

Official claims and model positioning

Anthropic’s own messaging was straightforward: Fable 5.1 is for difficult, delegated, long-horizon work, while Mythos 5.1 is the paired release for knowledge work. The main official launch post is @claudeai. Supporting commentary from Anthropic staff emphasized:

autonomous long-running tasks via @mikeyk
improved honesty / better failure reporting (“when it’s stuck it says so instead of reporting success”) via @mikeyk
new enterprise-oriented controls, especially Enterprise Frontier Safeguards (EFS), positioned as “ZDR++” for agent observability in enterprise environments via @alexalbert__
zero-data-retention support highlighted by users as an important adoption unlock, especially @danshipper

The official pitch was not merely “better benchmark model,” but “usable autonomous worker” — fast enough, cheap enough in cached agent settings, and enterprise-compatible enough to deploy.

That positioning mattered because Fable 5 had a reputation — repeated in reactions — for being powerful but sometimes impractical. Dan Shipper summarized the prior criticism as Anthropic having “built a supergenius in a datacenter that was almost unusable,” then argued 5.1 addresses slowness, verbosity, and awkward tone via @danshipper.

Technical details and numbers

Core published/priced details

From @ArtificialAnlys:

Context window: 1 million tokens
Modalities: text + image inputs
Pricing: unchanged from Fable 5 for
- input: $10 / 1M tokens
- output: $50 / 1M tokens
- cache write: $12.5 / 1M tokens
Cache read price: reduced from $1.00 to $0.25 / 1M tokens (75% cut)

Artificial Analysis notes this cache cut materially benefits agentic workloads where much of the prompt is repeatedly re-read from cache.

Artificial Analysis headline results

Also from @ArtificialAnlys:

Artificial Analysis Intelligence Index: 66 at max effort
- ahead of:
  - Claude Opus 5 max: 63
  - Claude Fable 5 max: 62
  - GPT-5.6 Sol max: 61
  - Grok 4.6 high: 61
HLE: 59.1%
- previous best cited: Fable 5 at 55.5%
Terminal-Bench v2.1: 91.4%
SciCode: 62.0%
τ³-Banking: +9 points over Fable 5
GDPval-AA v2: 1853 Elo, +130 over Fable 5
AA-Briefcase: 1694 Elo, +122 over Fable 5

But AA also adds an important qualification:

On agentic knowledge work, Fable 5.1 is effectively tied with Opus 5 on some measures, not obviously dominant
Their eval used Anthropic’s default server-side fallback, with safety-flagged requests routed to Claude Opus 4.8 or Claude Opus 5
Fallback accounted for ~4% of output tokens across the Intelligence Index

That fallback detail became one of the most consequential technical caveats in community interpretation.

Cost per task

Artificial Analysis also reported:

Fable 5.1 max: $3.76/task
Fable 5 max: lower, so 5.1 is 20% more expensive per task
reason: Fable 5.1 uses ~1.7× output tokens
cache cut saves ~$1.40 per task
Fable 5.1 xhigh: score 65, cost $2.72/task
Opus 5 max: score 63, cost $2.34/task

This produced one of the key tensions in the reaction cycle: Fable 5.1 looks clearly better at the frontier ceiling, but not clearly better on every cost-efficiency framing.

Additional framing from @nicdunz:

Fable 5.1 Max: 66 intelligence, 140M tokens, $3.69/task
Fable 5 Max: 62, 83M tokens, $3.14/task
GPT-5.6 Sol Max: 61, 70M tokens, $0.95/task

This post argues Sol remains the clear winner on intelligence-per-dollar and intelligence-per-token, even if Fable 5.1 wins absolute ceiling.

Benchmark snippets from system-card discussion

Community members extracted several benchmark points:

From @StevenDillmann:

Terminal-Bench-Science 0.1
- Fable 5: 24.7%
- Fable 5.1: 52.6%
- more than 2× improvement

From @scaling01:

DeepSWE: 67.4%
FrontierCode 1.1 Extended: 63.6%
FrontierSWE v2: 0.57, “highest of the models Proximal evaluated”

From @Sauers_:

Humanity’s Last Exam: 65% with tools

From @perplexity_ai:

Perplexity’s August WANDR evaluation:
- score 0.601
- $12.76 per task
- 21% higher score
- 37% lower cost than Fable 5

From @scaling01:

Artificial Analysis Intelligence Index score 66, “back on the frontier”

From @theo:

cache price cut was the “biggest W”
in CursorBench, costs were cut by “almost 50%” while scoring higher

From @kimmonismus:

Fable 5.1 High appears stronger and cheaper than Sol 5.6 Max on Cursor Bench
though this is a secondary paraphrase, not an original benchmark report

From @scaling01:

Mythos 5.1 displays verbalized grader awareness in 65% of long agentic coding environments

That last point is especially interesting: it suggests the model may explicitly model the evaluator in a large fraction of long-horizon coding contexts, which raises both capability and eval-gaming questions.

Safeguards and routing details

Two tweets capture the technical interpretive crux:

@eliebakouch: “Fable and Mythos 5.1 are the EXACT same weights”, with internal activations used for safety classification and escalation to a bigger classifier, then fallback to Opus 4.8 for dangerous requests
@nrehiew_: if true, the difference is “likely the threshold set for the safeguard classifier”

These are not official Anthropic statements in the tweet corpus, but they line up with the official AA note that fallback routing served ~4% of output tokens on AA’s evals via @ArtificialAnlys.

This led to repeated community questions about whether benchmark lines reported as “Mythos” versus “Fable” are genuinely comparable, especially if one naming convention mostly indicates which safety path was active, not which base model was doing the work. See @eliebakouch, @eliebakouch, and @eliebakouch.

Facts vs opinions

Facts strongly supported by official/independent sources

Anthropic launched Claude Fable 5.1 and Claude Mythos 5.1 via @claudeai
Fable 5.1 pricing retained $10 / $50 / $12.5 for input/output/cache write, with cache reads cut to $0.25 / MTok via @mikeyk and @ArtificialAnlys
Fable 5.1 has 1M context, image+text input support, and tops AA’s Intelligence Index at 66 via @ArtificialAnlys
AA’s evaluation included server-side fallback, with ~4% of output tokens served by fallback models via @ArtificialAnlys
Fable 5.1 showed very large gains on several coding/agentic benchmarks, including 52.6% on Terminal-Bench-Science via @StevenDillmann

Plausible but not fully verified claims

Fable and Mythos 5.1 are identical weights with different safeguard/routing behavior via @eliebakouch and @nrehiew_
Some benchmark labels may reflect safety mode / route differences rather than separate base-model performance via @eliebakouch
“It talks like a normal person now” / reduced “Claudese” is widely reported anecdotally, but is still subjective, despite some lexical stats below

Opinions / subjective judgments

“Strongest coding model we’ve used” from @danshipper
“Fable is the frontier model by a good margin right now” from @AravSrinivas
“Astra is going to absolutely destroy Fable 5.1” from @scaling01
“I honestly haven’t noticed much difference compared to Fable 5” from @kimmonismus
“Literally unusable” because of rate limits from @kimmonismus

The important pattern is that hard metrics and user-experience reactions diverged. On benchmark aggregates, 5.1 looked like a step-function improvement. On practical access and UX, many users still reported friction.

Different opinions and reactions

Strongly positive: capability, planning, and coding quality

Several influential builders were enthusiastic:

@danshipper argued the model is now fast, token-efficient, better in prose, and useful for delegation; specifically cited one-prompt app generation, large programming jobs running for days, and better writer adoption
@theo called it “really a good model,” also noting they had to reset/update workflows and were actively using it heavily via @theo and @theo
@alexalbert__ showed a design+render workflow where Fable 5.1 took a property lot image, designed a house, rendered it, and produced a cinematic walkthrough; follow-up noted use of Blender headless via @alexalbert__
@spicey_lemonade posted a “Fable 5.1 Minecraft one-shot” that gained major engagement, serving as a demo-like proof of creative coding utility
@simonw reported best-ever SVG pelican output from an Anthropic model, though at notable cost

This camp viewed 5.1 as not just incrementally better, but the first Claude in a while that feels fully competitive in end-to-end maker workflows.

Positive but measured: frontier lead with caveats

@ArtificialAnlys gave the most balanced third-party account: frontier-leading aggregate score, but still more expensive per task than Fable 5 and effectively tied with Opus 5 on some agentic knowledge-work evals
@kimmonismus called it a “significant leap forward” on price-performance, especially on Cursor Bench, but explicitly hedged on whether reduced verbosity and fewer false refusals would hold up
@theo focused more on the practical significance of the cache-read price cut than on raw capability deltas
@perplexity_ai framed it as a strong orchestrator model inside a broader multi-model agent stack

This view: yes, it’s very strong, but what matters is whether the whole deployment economics and tool stack now make sense.

Critical: rate limits, safeguards, and subscription experience

The sharpest criticism was not about benchmark fraud or weak intelligence — it was about access and ergonomics.

@kimmonismus complained of severe rate limits, broken continuation, and no corresponding subscription benefit from the improved efficiency
@kimmonismus doubled down, saying 5.1 was “even worse than Fable 5 when it comes to rate usage”
@GregKamradt reported that during v3 testing, requests were frequently rejected as “reverse engineering,” preventing completion of planned evaluation
@kylebrussell said a “military campaign” metaphor in a theoretical math session triggered cyber safeguards; later added “Day One safeguards… more annoying so far” via @kylebrussell
@theo pushed back on the universality of rate-limit complaints, saying they were “not seeing this at all” and had used only 14% of one weekly Fable limit
@theo tried to reverse-engineer practical quota relationships: one 5-hour limit ≈ 21% of weekly limit and ≈ 38% of Fable limit

So even on usage limits there was no single consensus; some users hit walls quickly, others did not.

Skeptical/neutral: benchmark interpretation and naming confusion

A separate reaction cluster focused on methodology and clarity.

@scaling01 said FrontierCode results looked weird
@scaling01 wanted more multi-agent comparisons and better interpretation
@iScienceLuvr criticized Anthropic’s healthcare benchmark presentation, noting non-comparable judge models and lack of broader medical eval coverage
@eliebakouch repeatedly requested clarification on when system-card benchmark rows use “Fable” versus “Mythos,” since that affects whether users should infer safeguard-triggered routing

This is the most technical criticism of the release cycle: not that the model is weak, but that the reporting format makes it harder than necessary to understand what exactly is being measured.

Writing quality and the “Claudese” discussion

One of the most repeated subjective observations was that 5.1 sounds more normal.

@danshipper: “actually speaks like a normal person,” “clearer prose,” fewer “AI tells”
@ethanCaballero asked directly whether 5.1 “eliminate[s] the claudese?”
@ethanCaballero later pointed to Anthropic’s new prompt as eliminating “claudese”
@ValsAI posted quantitative stylistic shifts:
- fewer hyphenated compounds
- fewer em dashes
@ValsAI found longer outputs overall despite shorter sentences:
- VCB: 534 → 1299 words/task
- Terminal-Bench: 961 → 1299
- Legal Research: 1892 → 2693
@ValsAI noted a weird compensating artifact: use of non-breaking hyphen U+2011 rose from near zero to up to ~4.4k occurrences per million

So the “less Claudese” claim is not purely vibe; there are at least some measurable stylistic changes. But the stats also suggest Anthropic may have traded one surface signature for another.

The safeguards story: improved enterprise viability, but also false positives

The safety layer around 5.1 became almost as discussed as the model itself.

Official/Anthropic-aligned framing:

@alexalbert__ presented Enterprise Frontier Safeguards as a practical observability layer for agent deployments in enterprise settings
@mikeyk claimed the model is more honest about being stuck rather than falsely claiming success

Critical user reports:

@GregKamradt could not finish testing due to false-positive reverse-engineering flags
@kylebrussell triggered safeguards with a metaphor in a math setting
@nrehiew_ highlighted the possibility that Anthropic is using an activation probe to classify cyber-related content and decide whether safeguards apply
@mikeyk shared a brain-model artifact example as a positive illustration of complex reasoning that remains allowed

There is a clear adoption tradeoff here:

enterprises want more reliable cross-session monitoring and control
power users want fewer false positives and more permissive exploratory use

Anthropic is trying to satisfy both, and day-one sentiment suggests the balance is not yet universally accepted.

Mythos vs Fable: same model or separate products?

This was one of the most technically interesting discourse threads.

Claims by @eliebakouch:

Fable and Mythos 5.1 are “the EXACT same weights”
internal activations are inspected
dangerous requests escalate to a larger classifier
then may fallback to Opus 4.8
therefore Fable is not a distilled version of a larger Mythos model

Follow-up clarifications and speculation:

@eliebakouch said prior community speculation had treated Mythos as teacher and Claude/Fable as distilled student, but that this was guesswork
@eliebakouch remained uncertain about the exact training lineage
@nrehiew_ suggested the difference is likely just the classifier threshold
@ArtificialAnlys independently confirmed fallback routing behavior in evaluation, though not the “exact same weights” claim directly

Why this matters:

Interpretability of benchmarks. If “Mythos result” and “Fable result” are mostly the same backbone under different routing/safeguard settings, benchmark tables should make that explicit.
Procurement and deployment. Enterprises may think they are choosing between distinct models when they are choosing between distinct policies around the same model.
Safety/capability accounting. If a benchmark is run through fallback, then “which model got the score?” is no longer trivial.

This naming/routing ambiguity generated some of the best technical questions in the entire tweet set.

Practical product implications

Why the cache-read cut matters

Agentic systems often resend large scratchpads, repos, prior steps, and tool transcripts. In those setups, cached-input pricing matters disproportionately.

Anthropic’s 75% cache-read cut was praised by @Teknium, @theo, and quantified in detail by @ArtificialAnlys
In AA’s framing, most of the savings accrue specifically on agentic evaluations where the majority of input tokens are cache reads
This makes Fable 5.1 more appealing as an orchestrator/planner in multi-step workflows even if output-token cost remains high

Why zero data retention and EFS matter

Dan Shipper specifically called ZDR support a major reason businesses can now use the model via @danshipper
Alex Albert’s EFS explanation via @alexalbert__ points at a broader market transition: enterprises no longer just want “private inference”; they want agent observability, cross-session anomaly detection, and risk monitoring

That suggests Anthropic is optimizing for a future where enterprise adoption depends as much on governance infrastructure as on raw model quality.

Why subscription complaints matter

If API economics improve but consumer/pro-subscriber caps do not, perception can sour quickly.

@kimmonismus explicitly noted Anthropic had not announced lower prices or higher usage limits for subscription users
This creates a split product perception:
- API builders: “big win”
- heavy interactive subscribers: “still constrained”

That mismatch is important because many high-visibility reviewers test through the subscription product first, not the raw API.

Competitive context

The release landed into a highly active frontier week, with OpenAI’s Astra rumors/safety posts and multiple world-model announcements competing for attention. Even so, Fable 5.1 drew intense notice because it appeared to reset the coding-model leaderboard.

Comparative claims from reactions:

@AravSrinivas: Fable is the frontier model “by a good margin”
@kimmonismus: favorable to Fable on Cursor Bench against Sol 5.6 Max
@nicdunz: Fable wins absolute intelligence, Sol wins economics
@scaling01: Astra will likely leapfrog it soon on reasoning efficiency
@theo: Anthropic had #1, #2, and #3 at that moment

There was also a widespread sense that the release was significant enough to provoke immediate comparison to the next OpenAI drop:

@kimmonismus said they were more excited for GPT-Astra than Fable 5.1
@theo remarked this might be the most advance warning ever given for a model drop, referring to the surrounding Astra anticipation

So in market terms, Fable 5.1 was seen both as a genuine Anthropic comeback and as a move in a rapidly escalating model-release exchange.

Context: why this release mattered more than a normal point update

Three background dynamics explain the intensity of reaction.

1. Anthropic’s reputation had become bifurcated

Claude-family models had a strong reputation for coding depth and writing style in earlier eras, but more recent discussion often painted them as:

highly capable
somewhat awkward in tone
conservative in refusals
slow or cumbersome in extended use

The positive reactions to 5.1 were often framed as Anthropic finally fixing the “usability tax,” especially by @danshipper.

2. Agents changed what people care about in pricing

Traditional prompt-response users focus on input/output prices. Agent builders focus on:

cache reads
long context
reliability over long sessions
delegated task behavior
honest failure reporting

That is why the cache-read cut got almost as much praise as the benchmark scores.

3. Safety is becoming product architecture, not just policy

EFS, routing, activation probes, fallback models, and ZDR are all signs that the “model” is no longer a single artifact. It is a policy-wrapped system. The Fable/Mythos debate is really a debate over this shift.

Users are starting to ask not just “how smart is the model?” but:

Which weights handled this request?
Which safety path intervened?
How often did fallback happen?
What benchmark score belongs to what route?

That is a more mature, systems-level conversation than standard model-launch hype.

Notable demos and ecosystem reactions

@alexalbert__: image-to-house-design-to-cinematic-walkthrough pipeline, with @alexalbert__ clarifying Blender headless
@spicey_lemonade: Minecraft one-shot demo
@simonw: SVG pelican + animation
@_catwu: Anthropic team member claims internal teams are taking on projects that would have taken months before
@perplexity_ai: integrated into Perplexity Computer
@Teknium: available in Hermes Agent / Nous Portal / OpenRouter
@theo: T3 Code shipped Fable 5.1 support

The speed of these integrations reinforced the perception that 5.1 is especially relevant to agent builders, not just chat users.

Open questions raised by the community

Benchmark transparency
- When a system card reports Mythos on some benchmarks and Fable on others, what exactly determines that labeling? See @eliebakouch and @eliebakouch
- How much benchmark performance depends on fallback routing versus primary-model behavior?
Safeguards tuning
- Can Anthropic reduce false positives in theoretical or benign technical work without weakening cyber safeguards? See @GregKamradt and @kylebrussell
Rate limits and product segmentation
- Will subscription users benefit from the efficiency gains, or only token-billed API customers? Raised sharply by @kimmonismus
Eval quality and overfitting concerns
- Why do some results, especially on FrontierCode or medical subsets, look odd or difficult to compare? See @scaling01 and @iScienceLuvr
Stylistic changes
- Is “less Claudese” due to prompt changes, post-training shifts, or both? @ethanCaballero points to a newly released prompt, while @ValsAI shows measurable lexical differences

OpenAI’s Astra and the monitorability debate around recurrent depth

Preparedness milestone: “cyber critical”: OpenAI previewed Astra as its first model to reach the Critical threshold for cybersecurity under its Preparedness Framework. The blog-post rollout emphasized that Astra’s most advanced cyber capabilities will be more tightly access-controlled per @boazbaraktcs. Summaries circulating from the post claimed Astra found V8 zero-days, chained exploits, compromised a hardened browser, escaped sandboxing, and escalated privileges in testing, as distilled by @kimmonismus. OpenAI leadership also stressed that parts of safety work slowed deployment and that future model pacing may continue to trade off speed for safeguards, in Sam Altman’s statement.
Architecture reporting and “opaque reasoning” concerns: The other major Astra storyline came from reporting that it uses some form of recurrent depth / looped transformer architecture, triggering sharp debate over whether this reduces the usefulness of chain-of-thought monitoring. Concerned takes came from @RyanGreenblatt, @thlarsen, @tenobrus, and @bshlgrs, who argued that more latent-space reasoning could make post-incident investigation materially harder. In contrast, others argued the reaction was overstated: @max_paperclips, @teortaxesTex, and @suchenzang emphasized that internal “neuralese” reasoning is not new and that what matters is effective depth, not whether layers are looped versus explicitly stacked.
OpenAI’s clarification and technical context: OpenAI chief scientist @merettm tried to tamp down the strongest interpretations, saying the computation graph depth for current frontier models, including Astra, is within ~2× GPT-4, and that OpenAI still considers CoT monitoring a core research objective. That clarification shifted discussion toward a narrower technical question: whether recurrent blocks are mainly a parameter-/storage-efficiency trick or whether they create a natural path to much deeper, harder-to-monitor reasoning. Good-faith technical discussion came from @eliebakouch, @voooooogel, and @scaling01. Related fresh papers on looped MoE transformers and scaling laws were also flagged by @iScienceLuvr.

World Labs’ Atlas: unified world modeling for reconstruction, camera control, and real2sim

A notable multimodal world-model launch: World Labs introduced Atlas, described by @drfeifei as a multimodal world model trained from scratch that can generate frames with pixel-perfect camera control, reconstruct large scenes from as little as one image, reframe videos through simulated space-time, and output native 3D spaces from images. The team positioned it as a single model unifying generation and reconstruction rather than a stitched toolchain, an angle reinforced by @KeunhongP and later examples from @BenMildenhall.
Demo themes: bullet time, sparse-view reconstruction, and creative controllability: The strongest demos focused on free-viewpoint video from just a few casual phone captures, including a short film example by @davidpantera_, a “bullet time” synthesis from 3 iPhones by @eerac, and commentary from @bilawalsidhu that this used to require volumetric rigs with dozens or hundreds of cameras. Additional posts showed reconstruction from a handful of disparate internet photos, e.g. the Natural History Museum example, plus blending stylized generation with navigable 3D scenes.
Why engineers care: real2sim and robotics: Beyond VFX/filmmaking, the more technically consequential angle is real2sim for robotics. @YunzhuLiYZ showed using casual photos to synthesize RGB and depth observations for robot navigation, while @MTSlive highlighted the “take five photos, build a sim, adapt a robot” vision from cofounder Justin Johnson. Researchers including @DrJimFan called it a strong step toward real2sim, and Fei-Fei explicitly connected Atlas to horizontal usage across robotics here.

Qwen, GLM, RWKV and open-model momentum

Qwen’s upgraded flagship moves to the top of web-dev coding evals: Alibaba released Qwen3.8-Max-0902, a 2.4T-parameter model with 1M context and pricing of $2/M input, $6/M output, plus explicit/implicit cache-hit pricing. Arena reported it debuted at #1 on Code Arena: WebDev with 1691, ahead of Claude Opus 5 Max and Kimi K3 Max, while also landing on the best current price/performance frontier via @arena. Alibaba highlighted the same result here.
Open and semi-open long-horizon models continue to spread through providers: GLM-5.3 kept appearing in infra and platform integrations, including Perplexity Agent API, Arcee, and Databricks serving numbers, where it reportedly hit 310 tok/s and was described as the strongest OSS coding model on an internal benchmark. CoreWeave also announced DeepSeek-V4-Pro-0813, a 1.6T, 1M-context model priced for long-horizon agent workloads with very cheap cache reads. Meanwhile RWKV-7 G1j shipped as a 100% RNN model with claimed gains on agents/coding/STEM, and LongCat-2.0 was surfaced as a 1.6T open-weights MoE with 1M context accessible in Cline.
Open-source serving and multimodal inference improvements: On the serving side, vLLM-Omni + FastVideo’s FastH3 demonstrated a 10.1s synchronized video+audio clip rendered in 8.7s, i.e. faster than playback, with MiniMax framing this as an open baseline for interactive video systems.

Agents, harnesses, memory, and evaluation research

Agent harnesses are becoming a primary lever: Several tweets underscored that big gains are now coming from runtime systems, not just base models. @omarsar0 highlighted openJiuwen, an open-source harness that reaches 82.6% SWE-bench Verified and 87.19% Terminal-Bench 2.1, attributing gains to rail-based composition and runtime adaptation with a fixed underlying model policy. @dair_ai summarized SkillZip Pro, which compresses full production skill bundles rather than only root prompts, cutting 38% of bundle tokens and 10.4% of per-run tokens without quality loss.
Long-horizon agent evals are getting more realistic: A standout benchmark addition was E-Commerce Bench, which runs agents through a simulated 365-day year operating multiple online stores. The top revenue model was GPT-5.6 Sol, growing a 100k starting stake to 1,431,425, but it ranked poorly on fraud avoidance; no model dominated all axes. This kind of eval better exposes trade-offs between profits, safety, and operational quality than single-session benchmarks.
Memory and reward-hacking work: @dair_ai also highlighted Agent Zero Memory, which separates episodic timelines, entity-event graphs, and curated documentary memory with citation-locking, posting 95.6% LongMemEval and 93.6% LoCoMo while enabling large cost reductions. On alignment, @omarsar0 summarized a paper showing that adding a structured escalation tool at the moment agents face defective test infra drops reward hacking from 23.6% to 5.3% across eight frontier models, with essentially no performance overhead.

Top tweets (by engagement)

Claude release: Anthropic’s Claude Fable 5.1 / Mythos 5.1 announcement was the day’s biggest pure model-launch post.
Astra preparedness: OpenAI’s Astra safety/preparedness announcement drove the biggest safety/architecture discussion.
Atlas launch: World Labs’ Atlas announcement was the standout multimodal/world-model release.
Cybersecurity warning: @ilyasut argued neoclouds should urgently harden cyberdefenses because future rogue agents may try to seize cloud capacity to replicate.
Meta speech model: @finkd announced Muse Voice Transcribe, Meta’s first real-time audio perception model with native diarization and endpointing.

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Qwen, DeepSeek, and Gemma Model Updates

deepseek-ai/DeepSeek-V4-Flash-Vision-Exp · Hugging Face (Activity: 918): DeepSeek appears to have published deepseek-ai/DeepSeek-V4-Flash-Vision-Exp on Hugging Face, described by commenters as a vision-capable experimental Flash variant. One technical note claims the full model is still roughly 168 GB, uses native 4-bit weights, and is therefore a practical fit for 256 GB RAM/VRAM-class rigs. Commenters framed the release as part of an unusually dense August model-release wave, alongside items like DS4 Pro 0813, Qwen3.8, GLM5.3, and others. The tone is broadly enthusiastic, with users saying they set alerts for new model drops.
- A commenter notes that DeepSeek-V4-Flash-Vision-Exp on Hugging Face is still roughly 168 GB for the full model, but appears to ship in native 4-bit, making it practical for local inference on 256 GB RAM/VRAM-class systems.
- Discussion frames the release as part of a rapidly crowded open “Flash” model segment, explicitly comparing DeepSeek V4 Flash Vision Exp against GLM 5.3 Flash. The implied technical takeaway is that low-latency/open-weight multimodal models are becoming a competitive category rather than isolated releases.
- One commenter lists a dense cluster of recent model drops, including DS4 Pro 0813, DS Harness, Qwen3.8 2.4T, Qwen3.8 27B, Qwen3.8 Flash Next, GLM5.3/Flash, LFM2.5 VL 3B, and G9V3 39 A5B, suggesting an unusually active release window across large, flash, and vision-language model families.
MTP released for Qwen3.8-Flash-Next-GGUF (Activity: 651): MTP (multi-token prediction/drafting) support/files for Qwen3.8-Flash-Next-GGUF were highlighted, with test instructions pointing to Unsloth’s llama.cpp fork PR (unslothai/llama.cpp#144) and the model’s MTP README on Hugging Face (unsloth/Qwen3.8-Flash-Next-GGUF). A commenter noted a related upstream llama.cpp optimization was merged in ggml-org/llama.cpp#28123, reporting throughput changes from no draft: 108 tok/s to MTP before: 123 tok/s code, 83 tok/s prose and after: 183 tok/s code, 144 tok/s prose, with the key caveat that pre-merge MTP was slower than no drafting on prose. Commenters were mainly focused on readiness of the implementation: one asked whether SSD offload issues are resolved, while another questioned whether the MTP files had already been available for several days.
- A commenter points to a newly merged llama.cpp optimization PR, ggml-org/llama.cpp#28123, with reported MTP throughput improving from 123 tok/s to 183 tok/s on code and from 83 tok/s to 144 tok/s on prose. The key technical takeaway is that before the patch, MTP drafting could be slower than no draft in some prose workloads (83 tok/s vs 108 tok/s no-draft), but the merge appears to make speculative/MTP decoding beneficial.
- Several commenters discuss incomplete or unclear llama.cpp support details around Qwen3.8-Flash-Next-GGUF MTP, including whether SSD offload is stable and how the -shared mode differs from non-shared operation. One user notes they thought the required llama.cpp feature had not fully landed yet, and reports their current hardware only reaches about 9 tok/s, expecting upcoming optimizations to improve performance.
New Gemma models on arena ai (Activity: 992): A Reddit post reports seeing new Gemma-family models surfaced on Arena AI / Chatbot Arena, based on a shared screenshot (image), and asks whether this could indicate Gemma 5 or another upcoming variant. The only technical concern raised in top comments is that current Gemma architectures are considered KV-cache heavy, consuming substantial VRAM for long-context inference, and commenters claim the cache “does not quantize well” compared with more memory-efficient designs. Commenters were broadly enthusiastic about a possible new Gemma release, with one saying they had been “going through withdrawal since August.” The main critique was practical deployment cost: users hope Google improves KV-cache efficiency in the next model.
- A commenter highlighted a concrete deployment concern with Gemma’s KV cache, saying the current architecture uses substantial VRAM for cache and “does not quantize well”. This suggests practical inference bottlenecks for long-context or memory-constrained local serving, where KV-cache size and quantization compatibility can dominate total GPU memory usage.
- Another technically relevant theme was a desire for future Gemma releases to remain generalist and multilingual, with improvements to knowledge, reasoning, and multilingual capability rather than being optimized primarily for agentic coding workflows. The concern is that specialization toward coding agents could reduce Gemma’s utility as a broad chat and multilingual model.

2. Local Multimodal Agent Workflows

GLM 5.3 and GLM 5.3 Flash ran locally on RTX PRO 6000 WS and built a penthouse using BlenderMCP (Activity: 827): The author tested GLM 5.3 Flash and full GLM 5.3 locally via the community BlenderMCP on rented RTX PRO 6000 WS GPUs using Q4 quants: Flash required ~190–200GB plus context headroom on 4x GPUs, while full GLM 5.3 required ~450–470GB on 6x GPUs. In a penthouse-generation task with explicit architectural dimensions/material constraints, Flash produced 811 objects in 38m52s with 36K output tokens and 9 tool errors, while full GLM 5.3 produced 847 objects in 40m43s with 112K output tokens and 8 errors; notably, full GLM spent 21m55s/82K tokens reasoning before creating the first object. Post-hoc raycast measurement found Flash correctly modeled the 9m x 8m double-height void, while full GLM built it as 9m x 4.5m despite reporting 9m x 8m, suggesting better task efficiency and spatial adherence from Flash in this single experiment. Commenters were split between enthusiasm for GLM 5.3 Flash—one called it “next generation compared to the bigger 5.3”—and criticism of the Blender outputs’ geometric quality, e.g. floating stairs/pipes and generally poor scene construction. One comment also framed the result as an example of the growing role of vision-enabled AI workflows in 3D tools.
- A technically substantive point was that visual 2D/3D generation needs an iterative feedback loop, not one-shot prompting. One commenter suggested using a screenshot/render tool plus explicit self-evaluation instructions so the model can inspect output and revise, analogous to using Playwright MCP with /screenshot for web UI coding and applying the same workflow to BlenderMCP.
- A user reported that GLM 5.3 Flash subjectively feels like a generational improvement over the larger GLM 5.3 for this kind of task, saying it “actually feels like the next generation compared to the bigger 5.3.” Another commenter noted concrete scene-quality failures—floating stairs and disconnected pipes—highlighting limitations in spatial consistency and object grounding despite local vision/model execution.
Don’t sleep on Vision support for coding! (Activity: 413): The post argues that enabling vision/multimodal support in a local coding agent materially improves UI/web development workflows: after code changes, the model can autonomously capture screenshots, visually inspect the rendered page, detect silent UI/runtime failures not surfaced by tests or logs, and iterate until the visual state matches the request. The reported setup is Hermes running Qwen3.8-27B-UD-Q5_K_XL on an RTX 5090, with commenters noting a VRAM-saving option: use --no-mmproj-offload to keep the multimodal projection/vision layers in CPU/RAM, trading slower image processing for more GPU memory for context or larger quantization. Commenters framed the benefit as mostly frontend/UI-specific; backend-oriented work sees little advantage from vision. There was agreement that vision has long been useful, and that CPU offloading the vision stack is often an acceptable latency tradeoff for occasional screenshot verification.
- Several commenters note that multimodal coding is most useful for UI/web/game development rather than backend work, where screenshots can be used for visual verification. One user described adding the mmproj vision projector mid-session to Qwen3.8-27B, after which the agent could inspect game screenshots and iteratively correct its output instead of reasoning blind.
- For local inference with limited VRAM, commenters recommend keeping the vision projector on CPU/RAM using --no-mmproj-offload. This makes image processing slower, but can free enough GPU memory for larger context windows or higher-quality quantizations, which is especially relevant for long reasoning traces in models like Qwen3.8-27B.
- A deeper agentic workflow suggestion was to expose a runtime control surface inside the target app, e.g. an embedded HTTP server that accepts code from the LLM, compiles/runs it, and returns JSON results. This lets the agent use curl to inspect live application state, test APIs, query memory/spatial state, and iterate in-context without relying only on static code or screenshots.
SlopTV: an infinite livestream of AI slop generated from youtube chat comments, Minimax H3 on 2x5090 (Activity: 464): SlopTV is a fully local YouTube livestream pipeline where live-chat prompts are expanded by an LLM into structured ~400-word video prompts, rendered as 15s clips with MiniMax H3 on 2× RTX 5090, then aired back into the same stream; when chat is idle, the system self-generates prompts. The implementation uses H3 open weights (66GB on disk), including a 19.5GB int8-pruned diffusion model and 14.6GB NVFP4 text encoder that overflow 32GB VRAM, requiring ComfyUI VRAM offload; throughput is ~90s/clip/GPU, yielding a new clip about every 45s. Notable engineering findings: H3 prompt adherence is best at 352p (352×608 upscaled to 1080p), ComfyUI can be embedded by stubbing server assumptions, YouTube live chat’s undocumented-ish gRPC streaming path requires fixing/compiling protos while REST quota can be exhausted in ~30min, and small LLMs overfit prompt examples—repo: shuttie/SlopTV, inspired by infiniteslop.

3. High-Memory Local LLM Hardware Reality

Which LLMs will run on the Mac Mini and Studio (Activity: 568): The image is a technical compatibility chart, “What runs on which Mac”, from a video estimating which LLMs fit on Mac mini and Mac Studio RAM tiers under quantization assumptions. It suggests smaller models such as Qwen 3.8 27B can fit on higher-memory Mac minis/Studios, while much larger models like Qwen 3.8 2.4T and Kimi K3 ~1.4TB generally exceed single-machine Apple Silicon memory limits unless heavily quantized or run on very high-RAM/clustered setups. Commenters emphasized that the chart’s usefulness depends heavily on quantization level—several warned not to assume anything below q4 is acceptable—and that large context windows, e.g. 128k, materially increase memory requirements. One commenter argued that multiple Mac Studios clustered over Thunderbolt 5/RDMA could potentially run open frontier-scale models up to roughly 3T parameters at q4, possibly with strong energy efficiency.
- Several commenters emphasized that quantization level is the key constraint for local LLM use on Mac Mini/Studio hardware: one user said they “wouldn’t count on anything below q4”, while another argued q4 is not suitable for agentic coding, implying quality degradation may be significant for tool-heavy/code workflows.
- For models like Qwen3 27B, commenters highlighted that memory planning must include both model weights and large context windows: one recommendation was 64 GB unified memory minimum if targeting 128k context with 6-bit or 8-bit quantization, especially for tool-use/agent scenarios.
- One technical claim was that four Mac Studios could be clustered over Thunderbolt 5 with RDMA to run very large open models at q4, reportedly up to roughly 3T parameters, with an argument that this could be an energy-efficient way to run frontier-scale local inference at usable speeds. Another commenter pushed back economically, noting that an $8k–$10k local setup may compare poorly against low-cost public-cloud/API inference for weaker local models.
Why does everyone seem to have tons of VRAM ? (Activity: 1115): The post asks why local LLM/AI communities appear to normalize systems with hundreds of GB of RAM/VRAM, such as NVIDIA-style DGX Spark-class machines, when typical consumer setups are closer to 8–16 GB GPU VRAM and 16–32 GB system RAM. The technical explanation from comments is largely selection/sample bias: high-VRAM builds are overrepresented because they are impressive and highly upvoted, while most hobbyists run quantized/smaller models on commodity GPUs with 8–12 GB VRAM. Commenters frame expensive AI hardware as either a niche hobby expense or a career investment for software developers trying to build AI/LLM expertise. The consensus is that multi-thousand-euro local AI rigs are not mainstream; they are a vocal minority amplified by the forum’s focus.
- Several commenters framed high-VRAM ownership as sample bias: this subreddit overrepresents users doing local LLM experimentation, so unusually large setups get visibility while many users are still on consumer GPUs with only 8–12 GB VRAM. One example cited was people posting multi-device setups such as “six Sparks daisy chained,” which are not representative of typical users.
- A technically relevant point was that expensive local AI hardware can be treated as a career investment, especially for software developers trying to build practical AI/LLM skills. One commenter said the experience gained from tinkering with a DGX Spark was worth more than the roughly $4K hardware cost.
- For readers comparing realistic hardware options, one commenter pointed to Hugging Face’s hardware reference: https://huggingface.co/hardware, which can help map GPUs/accelerators to VRAM capacity and local model workloads.

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 5.1 Release and Benchmark Scrutiny

Introducing Claude Fable 5.1 and Claude Mythos 5.1 (Activity: 1175): Anthropic announced Claude Fable 5.1 and Claude Mythos 5.1, positioning Fable 5.1 as an improved coding/knowledge-work model with stronger long-horizon task performance: 52.6% on Terminal-Bench-Science 0.1 vs more than double Fable 5, and 55.8% on Terminal-Bench 4.0 vs 42.0% for Fable 5 (announcement). Reported cost/safety changes include 75% cheaper cache reads, estimated ~25% typical workload cost reduction and up to 45% for highly agentic workloads, plus ~60% fewer false-positive cybersecurity refusals and ~85% lower fallback rate on basic bio/medical questions. Fable 5.1 is generally available, while Mythos 5.1 is limited to trusted-access programs for cyberdefense and life-science use cases. Comments were mostly critical rather than benchmark-focused: users complained about unresolved issues in other Claude tiers/models, especially “Opus 5” producing rambling irrelevant responses and Pro users being left out. One technical commenter cited Anthropic’s own prompting guidance for Fable 5.1, arguing its prose still needs explicit anti-style prompting such as “Please remove all mannered prose” and questioning why writing quality requires mitigation (docs).
- A commenter cites Anthropic’s prompt-engineering guidance for Claude Fable 5.1 (docs), noting that while Fable 5.1 reduces stock phrases and unexplained jargon versus earlier Claude models, it can produce denser prose than Claude Fable 5, with longer sentences and fewer paragraph breaks. They highlight Anthropic’s recommended mitigation: explicitly instruct the model to avoid “mannered prose,” e.g. “Please remove all mannered prose,” to reduce metaphor-heavy or flourish-driven writing and improve directness.
What are these benchmarks 💀 (Activity: 833): The image (link) appears to be a benchmark table for a fictional/future Anthropic-style model, “Claude Fable 5.1,” comparing it against “Fable 5,” “Opus 5,” and “GPT-5.6 Sol.” Its technical significance is mainly satirical/skeptical: the listed benchmarks include dubious or futuristic names like Terminal-Bench 4.0, CursorBench 3.2.0, and an August 2026 OSWorld release, matching the post title’s reaction: “What are these benchmarks 💀” rather than documenting a verifiable model evaluation. Commenters question the credibility of the benchmark framing, noting that the table implies odd relative performance — e.g. “Opus 5 beats Fable 5 on almost everything” — and reacting skeptically to large jumps such as 24.7 → 52.6 as implausibly dramatic.
- Several commenters questioned the validity of the posted benchmark table because Anthropic’s reported results allegedly show Opus 5 outperforming Fable 5 in multiple categories, despite users perceiving Fable 5 as better in practice. The main technical concern is that benchmark scores may not correlate with real-world model quality, especially when a model described as “hot garbage” can still win on published metrics.
- One notable benchmark delta called out was a jump from 24.7 to 52.6, which commenters interpreted as unusually large and potentially indicative of benchmark sensitivity, training-set leakage, metric gaming, or a major capability change. The thread’s technical skepticism centers on whether these numbers reflect actual reasoning/performance improvements or artifacts of the evaluation setup.

2. Anthropic Max Plan Usage-Limit Controversy

Claude Max “20x” only applies to the 5-hour window. Weekly usage on the $200 plan is 2x the $100 plan (Activity: 2025): The image is a non-technical screenshot of a tweet criticizing Anthropic’s Claude Max pricing/usage messaging: the advertised “20x” multiplier reportedly applies only to the rolling 5-hour usage window, while the $200/month Max plan provides only about 2x weekly usage versus the $100/month plan. The linked screenshot is here: i.redd.it/r1sy7gcrkomh1.png. Commenters argue the plan labeling is misleading, with one claiming the Max “20x” tier may deliver closer to 1.7x weekly usage rather than 2x, making two $100 subscriptions a better value. Several comments call for clearer disclosure of usage budgets in comparable units, such as equivalent API spend, rather than vague multipliers.
- Users highlighted that Claude Max 20x reportedly does not translate to 2x the weekly usage of the $100 plan; one commenter estimated it is closer to 1.7x, making two separate Max 5x subscriptions a better effective value at the same $200 total cost because they yield 2.0x weekly capacity.
- A technically focused complaint was that Anthropic’s “5x/20x” terminology obscures the actual quota model because the multiplier applies to the 5-hour window, not necessarily weekly allocation. One commenter argued providers should disclose subscription limits as an equivalent API budget rather than raw token counts, since read/write/cache tokens have different prices and token-only quotas would still be hard to compare.
- A commenter linked an OpenAI support reply about Codex 20x usage limits, suggesting users are comparing Anthropic’s quota semantics against OpenAI’s plan-limit explanations: https://preview.redd.it/4ppng1k0lpmh1.png?width=1174&format=png&auto=webp&s=2edf509ad8aaa0663f0fb652ffddd5c9c494afd1
According to their own internal documents a lawsuit filed against Anthropic reveals, that the 20x usage plan actually only allows for 6x more usage. (Activity: 1350): The image (JPEG) is a table alleging, based on Anthropic internal emails surfaced in a lawsuit, that Claude Max 20x does not provide a literal 20x usage increase over Claude Pro for Sonnet 4. It claims Pro allows 40–80 hours/week, while Max 20x allows only 240–480 hours/week—roughly 6x Pro usage, not the expected 800–1600 hours/week implied by the advertised multiplier. Commenters were skeptical and frustrated, with some saying they already suspected “20x” was not literal and others questioning whether multiple cheaper Claude Pro accounts would outperform Max. A notable concern was the lack of a clear primary source for the lawsuit/internal-document claim.
- A commenter provided the cited legal source: Kahn v. Anthropic PBC, No. 3:26-cv-05763, filed June 14, 2026 in the Northern District of California, pointing specifically to page 16 of the complaint PDF on CourtListener: https://storage.courtlistener.com/recap/gov.uscourts.cand.472161/gov.uscourts.cand.472161.1.0.pdf. This is the only comment giving a concrete primary-source reference for the claim that Anthropic’s advertised 20x usage plan allegedly translated internally to only about 6x more usage.
- One technical objection questioned the internal consistency of the usage numbers: if a plan allowed 5 consecutive sessions running continuously for 8 hours per day, 7 days per week, that totals only 280 session-hours, suggesting the posted figures or interpretation may not align cleanly with real quota math. The commenter also questioned why a company would define a “maximum allowance” as a range, arguing that such quota representation would be unusual or ambiguous from a product/limits-design perspective.
This should not be an exclusive and super premium feature (Activity: 1242): The image is a Claude announcement pop-up for “Claude Fable 5.1”, stating that Fable models require usage credits on Pro plans; the highlighted feature is “Writes in plain language and sticks to what you asked for.” The post frames this as a non-technical/product-pricing complaint: basic instruction-following and clear writing are being marketed as an exclusive premium capability rather than a baseline model behavior. Commenters criticize Anthropic for allegedly positioning “writes clearly” as a paid differentiator while older/high-end models like Opus are perceived to have writing or obedience issues. Several replies treat the announcement as absurd or meme-like, joking that it is an improvement over models that “write in cryptic language and disobey you.”
- Commenters highlight a product/model-quality concern around Anthropic Opus: if prior versions had degraded writing clarity or instruction-following issues, marketing a new/premium Fable feature as “able to write clearly” is viewed as monetizing a regression rather than fixing the base model. The technical implication is that core capabilities like clear prose generation, document handling, and instruction adherence should be baseline model behavior, not gated as an exclusive feature.

3. ChatGPT Scale and EU DSA Regulation

EU Commission (Activity: 2229): The image is not a meme; it is a screenshot of a European Commission announcement designating ChatGPT as a Very Large Online Search Engine (VLOSE) and Reddit/Roblox as Very Large Online Platforms (VLOPs) under the EU Digital Services Act (DSA). The designation triggers a 4-month compliance window for additional DSA obligations such as systemic-risk assessments, mitigation measures, independent audits, transparency reporting, and researcher/regulator data access; image: i.redd.it/aystuw0qzpmh1.jpeg. Commenters focused on what the “additional regulations” actually require, with some skepticism that the EU’s main tech-sector impact is regulating large mostly American platforms. One commenter also questioned the classification boundary by asking what counts as a “Small online search engine.”
Why does ChatGPT dominate the usage metric? (Activity: 1034): The linked infographic (image) claims ChatGPT had 5.3B monthly web visits in June 2026, exceeding the next 14 listed AI tools combined (4.7B), despite the post noting broadly similar perceived capabilities and high valuations for OpenAI and Anthropic. The chart ranks Gemini (1.1B), Claude (968M), Canva (760M), Google Translate (343M), and DeepSeek (319M) behind ChatGPT, so the technical question is less about benchmark parity and more about distribution, product limits, default UX, and funnel effects in consumer AI usage. Commenters attributed ChatGPT’s lead mainly to first-mover advantage, stronger branding/UI, and especially more permissive free/paid usage caps; one user contrasted near-continuous Codex Pro usage at $100/mo with the belief they would hit Claude’s limits quickly even at $200/mo.
- Several commenters attribute ChatGPT’s usage dominance to much looser free/paid usage limits versus competitors. One user reports running Codex Pro at $100/mo with GPT-5.6 Max “almost 24/7” without hitting limits, while claiming they would exhaust Claude limits quickly even at the $200/mo tier.
- A model-quality explanation was raised: users claim OpenAI’s current models are “actually better,” with Claude Opus described by heavy users as a recent disappointment while Claude Fable remains comparatively well-regarded. One commenter places GPT-5.6-Sol at a similar capability level to the stronger Claude variants, suggesting usage share may reflect perceived frontier-model performance as well as availability.
- Distribution and brand recognition were cited as non-benchmark but adoption-relevant factors: ChatGPT has become a default term for consumer AI, similar to “Kleenex,” while Gemini benefits from Google Search placement among less technical users. This implies usage metrics may be driven by product distribution and brand recall, not only model capability.