The one thing
01DeepSeek shipped an MIT-licensed model that speaks Codex natively, and it runs a task for three cents.
DeepSeek-V4-Flash-0731 went to public beta on the API yesterday: 284B total parameters, 13B active, a 1M-token context, MIT licence, weights on Hugging Face.1 The line that matters is buried in the changelog — it natively supports the Responses API format and is specifically adapted for Codex. The harness you already run can point at open weights without a translation layer.
Yesterday a bad convention in your repo was a nuisance. Today the arithmetic of which model reads it has changed by two orders of magnitude, and that is a procurement decision, not a preference.
Deeper — what migrating actually involves
- The base URL does not change. Set
model=deepseek-v4-flashand the existing OpenAI ChatCompletions or Anthropic-shaped client keeps working; V4-Flash additionally speaks the Responses API format natively, which is what makes the Codex path a configuration change rather than an adapter. - Check your legacy model names first. DeepSeek's changelog lists
deepseek-chatanddeepseek-reasoneras discontinued from 2026-07-24. If either string is still in your code, verify what it resolves to before you assume anything. - The 0731 build keeps the architecture and parameter count of the preview and was only re-post-trained. Anything you benchmarked against the preview has to be re-run, not extrapolated.
- V4-Pro is untouched by this update and its general release will follow soon with no date attached. Do not put it in a plan.
- Where the economics break down: at 1M context and 210M tokens of thinking on a hard evaluation, latency and rate limits become the binding constraint long before cost does. Price is the easy part of this migration.
Shipped
05GPT-5.6 price cut · Fast mode
From 30 July, Luna costs 80% less and Terra 20% less: Terra $2 / $12 per million in and out, Luna $0.20 / $1.20. Sol unchanged. Fast mode replaces Priority Processing — 2.5× faster at double the price, and priority-tagged requests keep working.3
MCP 2.0 — stateless
The 2026-07-28 spec drops server-side sessions: one HTTP request instead of initialising, holding an Mcp-Session-Id, then calling. No sticky routing, no session store. Simon Willison shipped three clients and servers off it in a week.4
Deeper — what changed on the wire
legacy POST /mcp → initialize → Mcp-Session-Id: 8f2c…
POST /mcp + Mcp-Session-Id → tools/call
stateless POST /mcp → tools/callThe server stops holding state, which means an MCP endpoint becomes an ordinary HTTP handler: no session store, no routing the second request back to the same machine, no reason it cannot run on a serverless function. Most of the MCP is a lot of work objection from last year was this handshake.
The second-order argument is the interesting one. An agent with a shell and curl can do more than any tool server, and is far harder to secure — every capability is implicit. An MCP tool surface is enumerable, auditable, and small enough that a laptop-sized model can drive it correctly.
Cline 4.1.0 → 4.1.2
The stable VSIX now ships two extensions in one package — legacy and a new SDK build — with a loader that activates one per window under a staged rollout starting at 1%. Check which you are running before filing a bug.5
Deeper — how to tell which build you are on, and one fix worth having
- 4.1.2 added a Legacy / Next indicator next to the version on the About page in settings. That is the only reliable way to know which of the two extensions your window activated, and the two have different internals — a bug report without it is unactionable.
- 4.1.1 removed the MCP server-key machinery: native MCP calls now route by server name instead of a random in-memory uid, so routing survives restarts and changes to the server list.
- SDK 0.0.67 honours the per-server
timeoutincline_mcp_settings.jsonfor initialize, tools/list and tools/call. It was previously hardcoded at 1.5 and 5 seconds; it now defaults to 60 and clamps between 1 and 3600. If you disabled a slow MCP server months ago because it kept timing out, that was probably why.
qm — multiplayer agent harness
Open-sourced yesterday: per-person and per-room scoped memory, files, permissions, crons and a durable sandbox, driven interchangeably by Pi, OpenCode, Codex or Claude Code. 521 points on Hacker News in a day. Runs in your own cloud; no production deployment workflow in the repo yet.6
Gemini CLI 0.53.1
Capacity exhaustion is now classified as terminal instead of retryable, which ends the loop that hung sessions instead of failing them. Cherry-picked into 0.53.1 and 0.54.0-preview.1 within hours.7
Promised, not shipped
DeepSeek V4-Pro general release — no date · Chrome dynamic patching — research · Two Chrome security releases per week — pilot
The conversation
01An intelligence index of 50 at three cents a task makes V4 Flash frontier-class and open. Every aggregator ran with that this morning, and so did the top of this issue.
- X · benchmark scepticismResolves a contradiction
The number everyone quoted came off DeepSeek's own harness. The DeepSWE jump — 7.3 → 54.4 — is self-run, which is why every other table disagrees.
- @dnhkng · Hacker NewsReader-posted, unverified
Posted the split nobody else ran. Against GPT-5.6 Terra it wins Terminal Bench 82.7 to 78.4 and Toolathlon 70.3 to 53.1 — and loses DeepSWE 54.4 to 69.6 and Agents' Last Exam 25.2 to 50.4.8
- r/LocalLLaMA · 741 points, 188 commentsUser claim, contradicts the above
The top thread of the window reads it the other way: "V4 Flash GA ranks the same as Sonnet 5 and Grok 4.5 on DeepSWE." One number, two communities, opposite conclusions.9
It is not a frontier model. It is a terminal-and-tools model priced like a toy, and that is the more useful sentence. The benchmarks it wins look like an agent doing shell work; the ones it loses look like an agent left alone for an hour.
A note against ourselves: every dramatic number in circulation traces back to the vendor's own harness, and we printed one at the top without saying so. The number was right. The frame was lazy.
Deeper — the rest of the floor sweep
- What it actually costs in the field. 100k in and 20k out for about 2¢. A full day of agent tinkering for 10¢. One 32-minute agent run on a single prompt at $0.07. The counterweight from the same window: one user burned $2 failing to build a GUI while the model kept reporting success.10
- Local inference is fast and broken at the same time. Two RTX PRO 6000 Blackwell reported at roughly 230–250 tokens per second single-stream at 131k context; two DGX Sparks at 60–82 tokens per second decode with better than 80% speculative-decode acceptance. But stock vLLM and SGLang assert on the newest cards — sparse MLA and speculative-decode kernels — and people are running community forks to get past it.
- Verbosity is real and promptable. Multiple independent reports of noticeably more thinking-out-loud than the preview. The workaround circulating is blunt and effective: instruct it not to plan, or turn thinking off for tasks that do not need it. That matters because thinking tokens are what you pay for.
- No vision. Text in, text out — confirmed on the model page. For agent work where half the loop is a screenshot, that is a hard boundary, not a footnote.
- Where it fails. First-hand reports of weak results on game and 3D work: visuals passable, core functions broken, and the model's own self-audit failing to catch it. The pattern is that it recovers well inside a tool loop and poorly when it has to hold a whole design in its head.
Three communities: Hacker News, Reddit (six subreddits swept, filtered to the window) and X (one window-constrained search). Practitioner figures are flagged unverified.
In production
01security bugs fixed in Chrome 149 and 150 with AI-assisted discovery and triage, per Google's own security team — one a sandbox escape that had survived 13 years. The counterweight is in the same post: bugs found faster widen the patch gap, so Chrome is piloting two security releases a week.11Source · blog.google, 31 July
Skip this
05An AI fund down 67% in July. Market movement. It changes nothing you will ship this month.
"Apple will watch everything burn when the AI bubble bursts." Opinion column, no new facts, nothing to check.
The benchmark inside the GPT-5.6 announcement. A vendor comparing itself on an exam it chose. We quoted the prices from that post and left the ranking alone.
Google Earth generating fake satellite imagery. A real story on the wrong beat — nothing here touches your toolchain.
"AI is getting way too expensive." Paywalled opinion, published the same week two vendors cut prices by 80%.
Everything we saw
4242 candidates scanned · 12 used in this issue — the rest, with the reason each one was left out
End of feed. That is everything from the window worth your time.
Next issue tomorrow, 06:00 UTC — and if nothing ships, it will say so in two hundred words.