Fable is 8% of Anthropic spend and the free lunch is over

Ramp’s billing index, drawn from 70,000 companies’ credit-card spend, puts Fable 5 at 8.0% of Anthropic model usage in July. Opus 4.8 takes 28.0%. Sonnet 4.6 takes 8.3%. Opus 5, which shipped July 24th, sits at 3.5%. Those numbers arrived inside an FT story on Anthropic’s finances, and Simon Willison pulled out the parts that matter: annualized revenue of $65bn for July against $47bn in May, 6,000 customers spending $100,000 a year or more, and a Q3 the company expects to book as profitable on the same accounting it used for Q2. OpenAI’s annualized revenue is over $40bn and up 35% quarter-to-date on the back of GPT-5.6. The business is compounding. The frontier model is not the one most teams actually run.

Drew Breunig wrote the practitioner’s version of that fact the same day, and Willison quoted the passage worth keeping: before Fable, tuning your harness or your context strategy felt like wasted effort, because a cheaper model would land in three months and paper over the problem anyway. Fable broke that assumption by being genuinely better and genuinely expensive at once, while Opus, GPT-5.6, K3, and GLM stayed good enough for most of the code. So teams started routing work by tier instead of buying the top of the menu. The free lunch was model prices falling faster than your requirements grew, and it ended.

Which makes the timing of Dan McAteer’s essay on harness evolution in Latent.Space useful rather than academic. His central number: Harness-Bench ran one model over 106 identical tasks in different harnesses and scored between 52.4 and 76.2, a 23.8-point spread with the weights untouched. OpenAI got a comparable result on ARC-AGI-3, tripling GPT-5.6 Sol from 13.3% to 38.3% by adding retained reasoning and compaction and nothing else. McAteer’s argument is that models keep absorbing harness capabilities into their weights, so the engineering job is deletion; he cites Anthropic’s Thariq Shihipar saying the team recently cut 80% of Claude Code’s system prompt. What survives absorption is the human-facing part: permissions, identity, legibility, and a policy surface governing when an agent is allowed to interrupt you. He predicts every agent company ships one within a year, the way they all shipped AGENTS.md.

The security picture underneath all this routing got a harder number. SUSVIBES, a benchmark of 186 feature-request tasks taken from real open-source projects where human programmers originally committed vulnerable implementations, evaluated 12 agentic coding configurations on frontier models. SWE-Agent with Claude 4 Sonnet produced functionally correct solutions 57% of the time and secure ones 11.8% of the time. The authors then tried the obvious mitigation, appending vulnerability hints to the feature request, and it did not close the gap. Functional correctness and security are being measured as one thing by most teams and they are not one thing; the leaderboard is public and worth checking against whatever configuration you run in CI.

A second benchmark went after memory rather than security. DreamBench-SWE scores software agents on multi-session hygiene, where later tasks depend on evidence that cannot be inferred from the current session and outcomes are graded by executable hidden oracles. In the preregistered successor run, agents with no external memory passed 21 of 180 tasks, deterministic verbatim event memory passed 82, and one pinned hosted Mem0 configuration passed 97. Every memory-bearing condition beat no-memory after Holm correction, and none of them beat each other in a way the authors will defend. Read it as a floor result: memory of some kind is worth roughly four times nothing, and the differences among memory products are still inside the noise.

The cost story is not confined to tokens. OVHcloud is raising prices in September, with 2026-edition gaming servers up 87% and other recent hardware up 40 to 59%, because founder Octave Klaba says memory cost six times more in June than a year earlier as suppliers moved capacity to high-bandwidth memory for AI accelerators (InfoQ has the details, and AWS has already repriced one reserved GPU product). AI demand is now setting the price of infrastructure that has nothing to do with AI, which is a cost line that shows up in your bill whether or not you ship an agent. SemiAnalysis pushed on the supply side of the same question in InferenceXv3, asking whether the CUDA moat holds under agentic inference workloads, where the traffic shape is long-horizon, tool-interleaved, and cache-heavy rather than a stream of short chat completions.

Cloudflare open-sourced Cloudflare OS, its internal corporate AI platform, built on a capability-based permission model with sandboxed execution and provisioned connectors (InfoQ’s writeup). The design point worth noting is that it routes to a model only where a model is needed, holding token cost down by treating inference as an expensive call rather than the default execution substrate. That is the same tiering instinct Breunig described, implemented as platform policy instead of developer discipline.

For a data point from the other end of the discipline spectrum, a developer on r/vibecoding posted the full accounting of directing an agent to build a mobile game and its backend platform in 6.5 weeks: 1,347 commits, 35 spec sessions, the entire backend in a single day. The workflow is specific enough to argue with, which is more than most of these posts offer. Set it next to the SUSVIBES 11.8% and you have the shape of the current moment, where throughput is real and verified safety is not.

What to watch: whether anyone publishes a routing policy with actual per-tier cost and pass-rate numbers instead of a vibe, and whether the first attention-policy surface McAteer predicts shows up as a config file or as yet another dashboard.