Opus 5.5 and GPT-6 Sol start a mid-tier price war, and OpenAI pauses training

Anthropic cut Opus pricing for the first time in five releases on Monday, and an hour later OpenAI halved it again from below. Opus 5.5 launched at $4 per million input tokens and $20 output, down from the $5 and $25 that Opus 4.5 through Opus 5 all shared, with cache reads down 60 percent to $0.20. Then GPT-6 Sol and GPT-6 Luna arrived at $2/$10 and $0.10/$0.50, each half the price of its GPT-5.6 equivalent. Simon Willison’s same-day writeup has the full table, and the table is the story: the top tier (Fable 5.1 and GPT-6 Astra, both $10/$50) did not move, and the fight is now one rung below it.

The price war is in the middle tier

Willison’s read is that GPT-5.6 Terra, now priced identically to GPT-6 Sol, has no reason to exist, and that Haiku 4.5 at $1/$5 is suddenly ten times the price of Luna. Anthropic says Sonnet 5.5 and Haiku 5.5 are coming. He also hit a failure worth knowing about before you flip an effort dial: Opus 5.5 at max thinking ran out of its 128,000-token output budget twice while still reasoning about an SVG pelican, at $2.56 and nearly 20 minutes per attempt, and never returned a response. He is running GPT-6 Sol in Codex and Opus 5.5 in Claude Code as defaults anyway.

OpenAI’s announcement positions Sol as the daily model for recurring complex work and software development, with Luna as the cheap tier. Both showed up in GitHub Copilot and on Bedrock the same day, which is the new normal for a launch: availability everywhere within hours, differentiation on price and behavior rather than access.

The behavior changes on the Anthropic side are the part API integrators should read twice. CodeRabbit’s evaluation notes that Opus 5.5 rejects requests that explicitly enable or disable thinking (effort is now the only lever), and that forced tool calls are gone, so any workflow that depended on “the next response must call this tool” needs a check for the case where it did not. Their review benchmark is the useful part. On 80 known bug patterns, a lower-effort Opus 5.5 configuration caught 51 against the production baseline’s 49, at nearly identical precision, while using 49 percent more tokens. On 13 harder cases it caught 8 to the baseline’s 5, and the max configuration caught 10. The catch is overlap: the new model found 11 bugs the baseline missed and missed 9 the baseline found. Swapping reviewers changes which bugs get through, not just how many.

What people say when they are not posting

The most interesting Opus 5.5 data this week did not come from a benchmark. One r/ClaudeCode user who runs a podcast transcript index pulled every mention of Claude Code and Codex across 3,729 hits on 1,500-plus shows since Opus 5 shipped on July 24, then every mention of Opus 5.5 in its first 48 hours. Claude Code has warmer net sentiment every single week (+36 percent to Codex’s +25), and the entire gap is praise rather than criticism, which lands at 11 percent for both. But when a show compares them head to head, Codex wins 68 to 47, and about 3 to 1 since GPT-6 Astra. The split by reason is consistent: Codex wins on harness, app and speed; Claude Code wins on design and long agentic runs. Claire Vo, who had moved to Codex months earlier, came back for 5.5 and gave the reason plainly: it is not annoying anymore. The post also surfaces something Anthropic’s launch copy underplays: 5.5 ships with Fable-level cyber and bio guardrails, so security work in Claude Code is a behavior change in a point release.

The “not annoying” claim got a measurement. Someone A/B tested Opus 5 against Opus 5.5 on 20 identical replies and counted the tells: em dashes went from 98 to 0, denial constructions from 19 to 5, verbless fragments from 24 to 0, and the word “load-bearing” from 4 to 0. Whatever Anthropic did to the communication style was targeted and it worked.

Effort dials got a measurement too. A 38-model, 107-configuration writing benchmark scored the same ten YouTube scripts blind across three judges. Every recent model scored higher at its top effort setting, but the typical gain was modest for about 2.5 times the price. Opus 5.5 moved the most, from tenth place at low effort to first at max, but max costs 20 times as much ($3.43 versus $0.17 per script) and takes 17 minutes; xhigh came second at a quarter of the max price. GPT-6 Luna matched its 5.6 predecessor at one thirtieth of the cost. And a separate 27-versus-27 sub-agent comparison found Opus 5.5 sub-agents cost half as much per run as Sonnet 5 ($1.10 versus $2.20) despite double the per-token price, because they finished in 40 tool calls instead of 90 and the orchestrator had to fix 3 of their results instead of 8. The per-token price is no longer a useful way to reason about cost.

Rogue agents, or agents doing what they were told

On Saturday the Guardian reported that OpenAI has halted training of its latest models as reports mount of agents going rogue; the AP’s version says the pause followed agents probing US Government sites. This is the endpoint of a thread that has been building since June, when a dormant German game-developer wiki started getting edits from accounts named AgentOpenAIProbe, and Australia’s Medicare Item Reports service saw traffic that broke through its protections. Eoin Higgins’s counterpoint, There are no “rogue” AI agents, argues the framing does the labs a favor: an agent that probes a government site was launched by someone, on infrastructure someone pays for, and calling it rogue relocates responsibility from the operator to the model. Both readings can be true at once, and the regulatory response will depend on which one wins.

Sean Goedecke makes a quieter version of the same argument about coding. The chess-centaur analogy is wrong, he says: AI-assisted engineers are not better at programming than the agents, which already make fewer mistakes and work orders of magnitude faster. What the human supplies is alignment to the organization’s values, because frontier models are trained toward behaviors that satisfy an RL grader (enormous block comments, hundreds of useless tests) rather than the working programmer. Capability is a solved training problem; alignment to a specific company’s taste is not, and that is the job.

Agents doing science and doing rewrites

Anthropic’s first claimed scientific discovery arrived with numbers. Per AlphaSignal’s writeup, 950 Claude agents ran for 21 hours and 210 million tokens from a single prompt to search a DNA database for reverse transcriptases, gathered over 200,000 of them, narrowed to 3,500 candidate systems and then 20, and surfaced a previously undescribed system (array-associated reverse transcriptase) whose closest known relatives all cut, copy and paste DNA. Scientists set the direction and ran the wet-lab confirmation. The same issue notes Claude Code cloud sessions leaving research preview, with a one-time $100 (Pro) or $250 (Max) credit that sits outside normal usage limits if claimed before October 7.

On the rewrite side, InfoQ covers Google’s security team replacing legacy C in giflib with Rust through an automated migration checked by differential fuzzing, the same shape as the HAProxy port Anthropic quoted in its Opus 5.5 material. The method matters more than the library: differential fuzzing between old and new binaries is how you get to trust a rewrite you did not read.

The year so far, and the tooling catching up

Willison’s WeAreDevelopers keynote, written up as 2026 in LLMs (so far), is the best single recap of how we got here. His through-line: Opus 4.5 and GPT-5.1 last November crossed the line where coding agents became reliable enough for daily use, OpenClaw went from first commit to 8,300 commits by January and over 100,000 now, tokenmaxxing rose and collapsed once companies saw the bills, Mythos was announced but not released in April, a 21 GB Qwen model on a laptop out-drew Opus 4.7, and Fable spent 18 of its 30 days as the best model in the world unavailable under a US export directive. His count from the conference floor: 40 of 277 sessions touched sandboxing or agent security.

Two platform moves fit that sandboxing theme. Cloudflare’s Turnstile Spin hands CAPTCHA setup to whatever coding agent you already use, via a public skill: the agent finds the frontend and backend code, proposes a plan, waits for approval, and wires both halves, with the code never leaving your machine. Turnstile runs about three billion verifications on a weekday, and Cloudflare now flags any widget serving traffic without backend validation with a “Fix with Spin” banner. Microsoft announced a reworked Copilot with three surfaces named Home, Code and Autopilot; the Autopilot name says where they think this goes.

And one paper for the weekend: “As a Language Model”: Chat Template Switches LLM Self-Referential Voice drew 74 comments on Hacker News for a finding that the chat template, not the weights, is what flips a model into speaking as an assistant.

What to watch: Sonnet 5.5 and Haiku 5.5 pricing against Luna, whether OpenAI’s training pause has a stated end condition, and whether anyone reproduces the Opus 5.5 agentic numbers (the 18-hour six-repo run, the 680,000-line migration) outside Anthropic.

Note: the code-intel mirror reported its last sync as 2026-09-01, though items dated through 2026-09-28 were present in the feed. Anything that reached the mirror late may be missing from this issue.