This Week in AI Dev: Frontier Prices Halved and a 27B Model Fit in 6GB (Week 39 of 2026)

Week 39 of 2026 cut the price of machine intelligence at both ends of the stack inside 48 hours. On 22 September, Anthropic shipped Claude Opus 5.5 at $4/$20 per million tokens with cache reads down 60% to $0.20; OpenAI shipped GPT-6 Sol ninety minutes later at $2/$10, a flat 50% cut, plus Luna at $0.10/$0.50. The same week, Ternary-Bonsai-2-27B packed a 27B multimodal model into 5.95GB at 98.2% of its FP16 score, and transformers learned to run llama.cpp's Metal kernels in-process. Unit-economics models from the spring are now stale.

By Rohit Raj — AI Consultant · Forward Deployed Engineer · LinkedIn

Every write-up this week framed 22 September as a two-vendor story: Anthropic priced Opus 5.5, OpenAI undercut it ninety minutes later, here is the head-to-head. Accurate, and too narrow to act on.

Widen the frame by a week and the *local* floor fell further than the API floor: a 27B-class multimodal model now fits under 6GB, the main Python inference stack stopped needing a separate engine, and a published architecture cut long-context prefill about 5x. Four independent groups pushed the same variable down at once, so the hosted-versus-self-hosted crossover moved with them. Six items below, one per vendor, each sourced to a primary doc.

What: Anthropic released Claude Opus 5.5 on 22 September 2026, API id claude-opus-5-5, on the Claude Platform plus AWS, Google Cloud and Azure.

Why it matters: $4 input / $20 output per million tokens, cache reads $0.20 (down 60%), cache writes $5, fast mode $8/$40. Anthropic reports 40% lower cost per typical task versus Opus 5 and ~30% faster output. Benchmarks: Terminal-Bench 4.0 66.4%, FrontierCode v1.1 54.4%, CursorBench 4.0 57.8%, OSWorld 2.0 81.8%, Humanity's Last Exam 67.7% with tools.

Plan around the cache-read cut. For an agent re-reading a large system prompt every turn, cache reads are most of the bill, and 60% off there beats the headline input cut.

Source: anthropic.com/claude-opus-5-5

Quick take: Reprice your agent workloads, especially cache-heavy ones.

What: OpenAI released GPT-6 Sol and Luna on 22 September 2026 — by several accounts about ninety minutes after Opus 5.5.

Why it matters: Sol is $2/$10 per million tokens, exactly half of GPT-5.6 Sol. Luna is $0.10/$0.50 — 50% off input, 58.3% off output. OpenAI presents these as permanent list prices, unlike the GPT-5.6 Sol promo that carried an expiry. Neither is the ceiling; GPT-6 Astra remains the flagship. Launch coverage converges: Sol is cheaper up to roughly the mid-40s on capability indexes, above which Opus 5.5 pulls ahead.

So the tier boundary shifted. Re-test work you routed to a flagship because the mid-tier could not hold up.

Source: openai.com — GPT-6 Sol and Luna · simonwillison.net

Quick take: Re-run evals before re-routing — a cut only saves if the cheaper tier passes.

What: Google published google/ax, a declarative Go orchestrator for agent workloads on Kubernetes. Apache-2.0, ~9.3k stars, top of GitHub daily trending.

Why it matters: An agent task becomes a Kubernetes resource — workspaces pre-wired to Git repos and MCP servers, sandbox limits, explicit egress allowlists, suspend/resume with checkpointing, and ax ssh into a live sandbox.

apiVersion: ax.io/v1alpha1
kind: Task
metadata:
  name: test
spec:
  workspaces:
    - name: golang
      goal: "Ensure that Go tool chain is available"
  debug: true

Steal the network-fencing default even if you skip the tool: an agent with an API key and unrestricted egress is an exfiltration path, and an allowlist is the cheapest control that closes it. If you are wiring MCP servers into production, that belongs in your design.

Source: github.com/google/ax

Quick take: Good design, unstable API — the README warns of breaking changes.

What: Hugging Face shipped native execution of llama.cpp quantized weights inside transformers on 22 September 2026, reusing ggml's Metal kernels via the kernels library (0.17.0+).

Why it matters: Loading GGUF already worked, but it dequantized to fp32 — the transformers API with the memory profile of full weights, defeating the point. This path keeps weights packed, running ggml kernels for quantization, normalization, attention and gated delta network ops, with a PyTorch fallback. On a 32GB M2 Max, Qwen3.5-4B at Q4_K_M generates ~16 tokens/second. Support starts with Qwen3.5 dense and MoE plus compatible Qwen3.8 checkpoints; the packed path needs Apple Silicon.

from transformers import AutoModelForCausalLM

model = AutoModelForCausalLM.from_pretrained(
    "unsloth/Qwen3.5-4B-GGUF",
    gguf_file="Qwen3.5-4B-Q4_K_M.gguf",
)

Source: huggingface.co/blog/transformers-llama-cpp-quants

Quick take: The win is deleting a process boundary — the llama.cpp sidecar can go.

What: Prism ML published Ternary-Bonsai-2-27B-gguf, Apache-2.0, September 2026. 27.36B parameters — 24.35B backbone, 2.54B embedding/LM head, 0.46B vision tower.

Why it matters: Weights are ternary with group-wise FP16 scaling at g128 — every weight is {−1, 0, +1}. PTQ1_0 packing lands at 5.95GB (1.75 bits/weight) against a 5.8GB ideal; PQ2_0 is 7.21GB at 2.13 bits, plus 0.63GB for the vision mmproj. Retention matters most: across 14 thinking-mode tests it averages 84.78 against an FP16 baseline of 86.32 — 98.2% — with 96.57 on math, 89.42 on coding. Throughput: ~47 tok/s on an M5 Max, 129.9 on an RTX 5090, 29.8–32.1 on a 72W L4.

Treat 98.2% as the publisher's own number until you reproduce it.

Source: huggingface.co/prism-ml/Ternary-Bonsai-2-27B-gguf

Quick take: The biggest item here if you ship on-device or on modest hardware.

What: Xiaomi's LLM-Core team published HySparse2 — hybrid sparse attention with two-level KV sharing — in arXiv 2609.26368, the architecture behind the coming MiMo-V3.

Why it matters: It reports roughly 5x fewer 1M-token prefill FLOPs than hybrid sliding-window attention on an 80B-A3B MoE backbone. The model splits into a YOCO-style self-decoder and cross-decoder, with KV Bridging connecting only full-attention layers, so cross-decoder KV caches are projected from self-decoder hidden states.

Prefill is the cost line people forget: paste a codebase into an agent and you pay to process all of it before one output token appears. A 5x cut makes million-token context ordinary rather than a demo. Note what it is not — a paper, not an open-weight drop. MiMo-V2.6 shipped openly this week; V3 has not.

Source: arXiv:2609.26368

Quick take: Nothing to install. Read it if you budget long-context agents.

Two are price changes to act on today. Three move a build-vs-buy line. One is a paper.

The two local-inference items landed on something I already run. The cover image above was generated on-device — FLUX.2-klein at 4-bit through MLX on Apple Silicon, ~25 seconds, no API call. I moved it local this year for an unglamorous reason: every free remote image endpoint either started charging or went dark, and the daily job kept falling back to a plain gradient. Owning the weights was the only version that stayed working.

So the ggml-Metal news is not abstract here. The same box drafts with a text model through a separate llama.cpp process over HTTP — a boundary existing purely because transformers could not run packed weights fast enough. That is what I am deleting this week, with Ternary-Bonsai under test.

The warning: retention is measured on benchmarks, and benchmarks are not your workload. Run your own evals before deleting the process that works. When I do this as a Claude Code consultant, the harness gets built before the migration — otherwise a regression looks like a bad day.

The Jev discourse. Three top r/LocalLLaMA threads this week were about Jev, none about the technology — a mod request to stop the advertising posts, an argument that the marketing targets people who think AI started with LLMs, and a 25-line Python reimplementation. When the top posts about a product are all meta-commentary on its promotion, the signal has moved to the campaign. The category is real — I covered the open-weights alternatives yesterday — but this week's volume is not news.

browser-use/video-use. 26.6k stars and a fun demo: describe an edit to Claude Code and it cuts filler words, grades colour, burns subtitles — reading video through transcripts rather than raw frames to keep token use sane. Skip-for-now rather than bad: under the hood it is ffmpeg plus one transcription call plus a prompt.

Q: Is Claude Opus 5.5 cheaper than GPT-6 Sol? No. Sol is $2/$10 per million tokens; Opus 5.5 is $4/$20 — half the price on both. Opus 5.5's advantage is at the top of the capability range and on $0.20 cache reads.

Q: When did Claude Opus 5.5 and GPT-6 launch? Both on 22 September 2026. Anthropic announced Opus 5.5 first; OpenAI announced Sol and Luna roughly ninety minutes later.

Q: Are the GPT-6 price cuts permanent? OpenAI presents $2/$10 for Sol and $0.10/$0.50 for Luna as standard list pricing, not a promotion — unlike the earlier GPT-5.6 Sol discount, which had an expiry.

Q: Can I run a 27B model without a GPU now? The weights fit: Ternary-Bonsai-2-27B is 5.95GB at 1.75 bits per weight. Throughput still depends on hardware — ~47 tok/s on an M5 Max, 129.9 on an RTX 5090.

Q: Does transformers replace llama.cpp now? Not generally. The new path runs ggml Metal kernels in-process on Apple Silicon for Qwen3.5-family checkpoints, ~16 tok/s on Qwen3.5-4B Q4_K_M. llama.cpp stays broader.

Two price cuts and three capability jumps in a week quietly invalidates a spring unit-economics model. The work is rarely the migration — it is an eval set good enough to tell whether the cheaper tier holds for *your* workload.

That is the work I do: fixed-scope MVP builds, and founding engineer for hire with teams that need production AI shipped, not prototyped.