This Week in AI Products: Tiering, Cyber Gates, and 100x Cheaper Retrieval
No new flagship — OpenAI tiered GPT-5.6 by price and risk, Neon and Castform shipped a 100x cheaper retriever, and Anthropic put Claude Code on autopilot.
If you were watching for a new flagship last week, you missed the story. Nothing big shipped between August 4 and 10. What shipped instead was tiering — the same GPT-5.6 family sliced by price, speed, and who you're trusted to be.
That's more useful than a bigger model. It tells you how the labs want enterprises to actually deploy.
###Luna goes free, Sol gets a slider
The main move was August 6: OpenAI made GPT-5.6 Luna the default for Free and Go ChatGPT accounts — unlimited text chats, new Think button for harder questions. Plus and Pro keep an updated Sol with a slider for how much reasoning you want.
I couldn't pull the origin post directly — openai.com was behind a Cloudflare challenge — but HN indexed it at 17:02 UTC (314 points) and RuntimeWire's syndication at 17:26 UTC confirms the details.
It's a routing hint. Luna where you can, Sol where you must. That pairs with the July 30 pricing change still echoing last week: Luna down 80% to $0.20/$1.20 per million tokens, Terra down 20% to $2/$12, Sol flat at $5/$30, plus a new Fast mode for Sol at 2x price for 2.5x speed. Don't burn Sol on retrieval loops.
A CNBC headline indexed August 5 also claimed Microsoft made Sol the default in GitHub Copilot for staff. The URL 404s so I can't verify the body — treat it as a directional enterprise signal, not a confirmed rollout.
###Cyber gets its own gated frontier
The most explicit enterprise launch landed August 10: GPT-5.6-Cyber inside a new two-tier Daybreak initiative. OpenAI's post and RuntimeWire's syndication both timestamped that afternoon describe a purpose-trained model that answers advanced exploit-development requests the general model refuses — RuntimeWire's headline puts it at 95% completion vs. 1.5% for Sol.
Access is the product. Daybreak Red requires verification, monitoring, and hardware keys, with a separate tier for broadly defensive work. If you run a security team, that's a real tier to evaluate. If you're OpenAI, it's a bet that "trusted hands" is a defensible distribution model. I'm not sure hardware-key gating scales, but I get why they tried it.
###The 100x cheaper retriever
The sleeper wasn't from a lab. On August 5, Neon (now part of Databricks) and Castform showed an RL post-trained 4B open model that matches Sol on retrieval at roughly 100x lower cost.
Their math is blunt: a typical multi-turn search with gpt-5.6-sol takes >10s and ~$0.03 end-to-end. Small models are already 100x cheaper but lacked retrieval skill. Castform's loop — synthetic data from lakebase_text and lakebase_vector, rollouts that call Lakebase Search on Neon, same call at inference — closes the gap by training on data already in your Postgres.
This is the MCP thesis with economics attached. If agentic retrieval is the workload — plan, search, search again — cheap specialized retrievers beat frontier calls on every turn except the last.
###Auto mode on by default
Anthropic flipped the other switch August 9: Claude Code's auto mode on by default, per TechCrunch (Enterprise section, 19:20 UTC). "Even less human oversight" is the pull quote.
I've got mixed feelings. As I wrote in March, the unit of work is now "a change I will review" — and review velocity is the bottleneck. Auto-by-default optimizes for commit speed and pushes cost to audit. If you turn it on, keep the allowlist discipline — scoped creds, per-tool gates, every call attributable.
###What I'd do Monday
- Split workflows by tier. Luna for triage, Terra for drafting, Sol for hard reasoning. Cyber only under Daybreak Red.
- Benchmark the small retriever. Even 20x cheaper changes your unit economics if you do multi-turn search.
- Set your auto-mode policy. "Auto" without an allowlist is just unreviewed deploys with better marketing.