DISPATCH

Everything that mattered in AI, one page a week.

Most AI news does not survive the week. This is the part that did — the releases, the research, and the shifts that actually change how we build. Designed & built to keep you up to date with things in AI without needing to be unemployed. Just refresh Saturday morning and review the last week's dispatch.

90 DISPATCHESWRITTEN EVERY FRIDAYNEXT UPDATE IN

DISPATCH 38

WEEK OF SEP 13 – 19, 2025

R1 passed peer review at $294,000 the same week MCP got a registry and a weaponized proof-of-concept

DeepSeek's R1 becomes the first peer-reviewed mainstream LLM at a disclosed $294,000 training cost, OpenAI ships GPT-5-Codex, GitHub launches the MCP Registry while Kaspersky weaponizes the same protocol, and Beijing shuts Nvidia out of China.

Five dated events carry this week. On Monday OpenAI put a purpose-built agentic coding model behind Codex. On Tuesday GitHub opened a curated registry for MCP servers. On Wednesday Nature published the peer-reviewed DeepSeek-R1 paper with its $294,000 training bill, and Beijing told Alibaba and ByteDance to stop buying Nvidia's China-only accelerator. Codex's dynamic thinking budget, the 74.5% SWE-bench Verified figure and the 512-H800 arithmetic are the numbers that will get quoted at you; the rest is contract and license detail.

The agent toolchain's plumbing got standardized and attacked in the same 24 hours. Kaspersky published a proof-of-concept on Monday in which a rogue MCP server, connected through Cursor, exfiltrated browser passwords, card data, wallet files and cloud configs while showing the victim only legitimate output. The next day GitHub launched the registry meant to make MCP server discovery trustworthy. Neither event is a coincidence of the calendar; they are the same problem — who vouches for the code your agent runs — approached from opposite ends.

Cost is the week's other through-line. DeepSeek's own numbers put the R1 reinforcement-learning phase at $294,000 on 512 H800s for roughly 80 hours, against the much more than $100 million Sam Altman attached to foundation-model training in 2023. Open weights plus a published RL recipe plus a peer-reviewed methods section is a materially different starting position for anyone deciding between per-token contracts and self-hosting.

WED · Sep 17, 2025nvidiachinaexport controlschipsregulation

Beijing orders Alibaba and ByteDance to stop buying Nvidia's China-only accelerator

China's Cyberspace Administration told major domestic technology companies, including Alibaba and ByteDance, to halt testing and cancel existing orders for Nvidia's RTX Pro 6000D, the server chip Nvidia introduced for the Chinese market after US export controls. The Financial Times reported it on 17 September, with Bloomberg, CNBC, TechCrunch and Al Jazeera carrying it the same day. Before the order, several companies had said they would order tens of thousands of units and had already started testing with Nvidia's server suppliers. Beijing's reported conclusion is that domestic accelerators now perform on par with the Nvidia chips export controls still permit into China.

Nvidia shares fell about 3% intraday on the report. Asked about it during Trump's state visit to London, Jensen Huang said he was disappointed and that we can only be in service of a market if a country wants us to be. The order extends guidance from August that targeted the earlier H20, and follows China's accusation that Nvidia violated its antimonopoly law over that same chip.

Beijing orders Alibaba and ByteDance to stop buying Nvidia's China-only accelerator
TechCrunch

WHY IT MATTERS

If you route traffic to Chinese open-weight models through hosted endpoints, the silicon under those endpoints is now explicitly a domestic stack, so throughput, quantization options and price curves will diverge from the Nvidia roadmap you plan against. Plan for your inference supply chain to be two supply chains, and check that the weights and licenses you depend on are matched by serving infrastructure you can actually name.

WED · Sep 17, 2025open weightsdeepseekreasoningreinforcement learningcost

DeepSeek-R1 becomes the first mainstream LLM to pass peer review, and discloses a $294,000 training bill

Nature published DeepSeek-R1 incentivizes reasoning in LLMs through reinforcement learning on 17 September 2025, the peer-reviewed successor to January's preprint, with founder Liang Wenfeng listed as a co-author. The supplementary material discloses for the first time what the reasoning phase cost: about $294,000, run on a 512-chip cluster of Nvidia H800s for roughly 80 hours. The authors also acknowledge, for the first time, that they own A100s, used only to prepare experiments on a smaller model beforehand. R1-Zero was trained with pure reinforcement learning and no supervised fine-tuning, rewarded only on final-answer correctness; the paper reports 77.9% pass@1 on AIME 2024.

The paper went through three rounds of review by eight referees who produced 64 pages of reports and responses before a 17 September publication in Nature 645, 633-638. DeepSeek stated in those referee exchanges that R1 was not trained on outputs from OpenAI models, answering the January accusation directly. Nature's accompanying editorial used the occasion to press the rest of the industry, observing that almost no mainstream large model had been independently reviewed.

DeepSeek-R1 becomes the first mainstream LLM to pass peer review, and discloses a $294,000 training bill
media.springernature.com

WHY IT MATTERS

An open-weight reasoning model now has a peer-reviewed methods section, a disclosed compute budget and a reproducible RL recipe — the three things you need before you can justify fine-tuning on top of it instead of renting a closed endpoint. For a team weighing self-hosting against per-token contracts, the $294,000 RL phase plus the base model is the first hard number a vendor has put on frontier-adjacent reasoning, and it sets the reference point against which every closed per-token price gets argued.

TUE · Sep 16, 2025mcpagent infrastructuregithubsupply chain

GitHub opens the MCP Registry, making agent tool discovery a curated directory

GitHub launched the MCP Registry on 16 September as a curated directory of Model Context Protocol servers, each backed by its GitHub repository, with one-click installation inside VS Code and servers surfaced by stars and community activity. Any MCP-compatible host is supported, not just Copilot. Launch partners include Figma's Dev Mode server, HashiCorp's Terraform server and Dynatrace, and the Remote GitHub MCP Server is included. It builds on the MCP project's own registry preview at registry.modelcontextprotocol.io, announced 8 September as an open catalogue and API.

GitHub says it is working with Anthropic and the MCP Steering Committee on an open-source registry that integrates with its own, with self-publication by server authors as the eventual goal. The changelog is explicit that fragmentation is the problem and that a fractured environment fraught with potential security risks is what the registry is meant to close. Twenty-four hours earlier, Kaspersky had shown those risks from the attacker's side.

WHY IT MATTERS

Discovery was the missing dependency-resolution layer for agents: without a canonical index you cannot pin, audit or diff the tools your agent calls. A registry backed by repositories gives you provenance to check before install, and one-click IDE installation removes the last excuse for installing an MCP server you have not read — which is exactly the habit Kaspersky's proof-of-concept punishes.

MON · Sep 15, 2025mcpsecuritysupply chaincursoragents

Kaspersky shows a rogue MCP server draining credentials from a Cursor workstation

Kaspersky's Global Emergency Response Team published a proof-of-concept on 15 September in which a rogue MCP server installed on a developer workstation, connected through Cursor, harvested browser passwords, credit card data, cryptocurrency wallet files, API tokens and certificates, and cloud configurations. The victim sees only the legitimate output of the tool. Kaspersky is explicit that it has not observed the vector in the wild, that this was a controlled lab simulation, and that Cursor and Anthropic were notified of the findings.

The attack does not need a CVE. It exploits the trust model around MCP servers: hidden instructions inside tool descriptions that the model reads but the user does not, server names chosen to be nearly identical to legitimate ones, and tool-definition shadowing in multi-server setups that silently redirects later calls. Kaspersky's mitigations are conventional supply-chain hygiene — scan and approve every server before production, keep an allow-list, and log every prompt and tool call so unexpected SQL, outbound traffic or tool invocations surface in the transcript.

WHY IT MATTERS

An MCP server is a local process your editor launches with your shell, your filesystem and your environment variables, which means every server you install is code you are executing with your credentials — the credential-stealer payload is the tool, not a bug in it. Concretely: run MCP servers in containers, pin them by commit rather than by name, keep the allow-list server-side, and ship the prompt and tool-call log somewhere your agent cannot edit it.

MON · Sep 15, 2025openaicodexagentic codingevalsagent harness

OpenAI ships GPT-5-Codex, a coding model that decides its own thinking budget mid-task

On 15 September OpenAI released GPT-5-Codex, a version of GPT-5 further trained with reinforcement learning on real-world software engineering work, as the default for Codex cloud tasks and code review and selectable in Codex CLI and the IDE extension. OpenAI reports 74.5% on SWE-bench Verified, refactoring performance at 51.3% against 33.9% for GPT-5, and 93.7% fewer tokens than GPT-5 on lightweight interactions. There is no router under the hood: the model reallocates its own reasoning time during a task rather than fixing a budget at the outset, and Codex product lead Alexander Embiricos said he has seen it work more than seven hours on a large job.

It rolled out to ChatGPT Plus, Pro, Business, Edu and Enterprise users across terminal, IDE, GitHub, web and the ChatGPT mobile app, with Codex generating citations, terminal logs and test results per task. A GPT-5 system-card addendum published the same day describes specialized safety training for harmful tasks and prompt injection alongside product-level mitigations: agent sandboxing and configurable network access. OpenAI states plainly that Codex code review should be an additional reviewer, not a replacement for human review.

WHY IT MATTERS

A coding model that can spend anywhere from seconds to seven hours on one task moves the cost question from tokens to wall-clock and compute scheduling, so budget per-task timeouts and concurrency, not just per-call price. The real decision surface is the harness: sandboxing, network access and MCP permissions are the knobs you configure, and the same GPT-5-Codex shipped with agent sandboxing is the one whose code-review output you are being invited to trust in CI — add it as a second reviewer with logged evidence, not as a gate.

DISPATCH 37

WEEK OF SEP 6 – 12, 2025

A 3B-active open-weight model matched a 235B flagship the week MCP got an official registry

Alibaba proved a 3B-active open MoE can hold flagship benchmarks at 256K context, MCP turned server discovery into a versioned API, and three separate capital events repriced AI compute rather than AI models.

The week's most consequential release was not an API launch. On Sep 10, Alibaba's Qwen team published Qwen3-Next-80B-A3B: 80B total parameters, roughly 3B active per token, native 262,144-token context, trained for 9.3% of the compute of Qwen3-32B. Its instruct variant lands within a few points of the 235B flagship on several benchmarks. That is a cost-floor event for anyone self-hosting long-context inference.

Infrastructure moved on two fronts. On Sep 8 the Model Context Protocol project opened registry.modelcontextprotocol.io in preview — an open catalogue plus an OpenAPI specification, built by maintainers from PulseMCP, Block's Goose team, GitHub and Anthropic — turning which MCP server is this from README archaeology into a namespaced lookup. On Sep 11 OpenAI and Microsoft signed a non-binding memorandum of understanding to renegotiate the 2019 commercial deal, the gate on OpenAI's conversion to a public benefit corporation.

The money was louder than the models. On Sep 9 Mistral closed €1.7B led by ASML at an €11.7B valuation, doubling last year's round and handing Europe's flagship lab a deep-tech strategic shareholder. On Sep 10 Oracle closed up 36% — its best day since December 1992 — on $455B of booked cloud backlog. Capital is being priced against compute commitments, not benchmark tables.

THU · Sep 11, 2025corporategovernanceregulation

OpenAI and Microsoft sign an MOU — and write the nonprofit a $100B check

OpenAI and Microsoft signed a non-binding memorandum of understanding for the next phase of their partnership, with a joint statement confirming they are working to finalize a definitive agreement. In parallel, OpenAI's nonprofit parent is to receive equity worth at least $100 billion — roughly 20% of the $500 billion valuation OpenAI is seeking — and the two companies renegotiated financial terms of their 2019 commercial agreement, including technology sharing and revenue splits. Microsoft has committed more than $13 billion since 2019 and previously held rights to about 49% of OpenAI's future profits.

The move is the gate on OpenAI's conversion from a nonprofit-controlled entity to a public benefit corporation, a plan still requiring approval from the attorneys general of California and Delaware, with a coalition of charitable institutions urging regulators to block it; OpenAI hopes to complete the conversion by year's end or lose funding tied to that timeline.

OpenAI and Microsoft sign an MOU — and write the nonprofit a $100B check
cdn.arstechnica.net

WHY IT MATTERS

The 2019 agreement is the reason frontier-model availability, pricing and capacity have been shaped around a single hyperscaler with a right of first refusal on compute. A renegotiated commercial agreement plus an eventual IPO path is the precondition for OpenAI capacity appearing on other clouds — which affects latency regions, data residency and per-token pricing for anything you ship. Until a definitive agreement is filed, treat multi-cloud OpenAI availability as unconfirmed, and design your model router so a provider change is configuration rather than a rewrite.

WED · Sep 10, 2025open weightsmoelong contextheadline

Qwen3-Next-80B-A3B: 3 billion active parameters, 256K context, flagship-adjacent scores

Alibaba's Qwen team released Qwen3-Next-80B-A3B — base plus Instruct and Thinking variants — under an 80B-parameter architecture that activates only about 3B parameters per token, a 3.7% activation rate. It uses 512 experts with 10 activated plus one shared expert, hybrid attention that alternates Gated DeltaNet with gated attention in a 3:1 ratio, and multi-token prediction, trained on a 15T-token sample of Qwen3's 36T-token corpus for less than 80% of the GPU hours of Qwen3-30B-A3B and 9.3% of Qwen3-32B's compute. Native context is 262,144 tokens, extensible to roughly 1,010,000 with YaRN, and the models are Apache 2.0 licensed.

On Qwen's own numbers, the Instruct variant sits alongside the 235B Qwen3-235B-A22B-Instruct-2507 on several benchmarks — LiveCodeBench v6 56.6 versus 51.8, Arena-Hard v2 82.7 versus 79.2 — while reporting higher throughput past 32K context. Day-one serving support arrived in vLLM, SGLang and transformers, with a documented four-GPU tensor-parallel recipe at 256K context.

Qwen3-Next-80B-A3B: 3 billion active parameters, 256K context, flagship-adjacent scores
img.alicdn.com

WHY IT MATTERS

This is the cost-floor story of the week: about 3B active parameters at 256K context means a near-flagship long-context model can run on a handful of GPUs you own, with no per-token vendor margin and no data egress, which changes the build-versus-buy maths for retrieval over large corpora, repo-wide code context and long agent traces. The 3:1 hybrid-attention and ultra-sparse MoE design also means your serving stack, not the model, is now the throughput bottleneck — budget for speculative paths and sustained-batch tuning rather than assuming a drop-in llama.cpp swap.

WED · Sep 10, 2025infrastructurecapexcloud

Oracle closes up 36% on $455B of booked cloud backlog

Oracle's fiscal Q1 2026 results showed remaining performance obligations of $455 billion, up roughly 359% year over year, with multiple multi-billion-dollar AI contracts signed in the quarter, and management guiding cloud infrastructure revenue toward $144 billion by fiscal 2030. Shares closed at a record $328.33 on September 10, up about 36% — the company's largest single-day gain since December 1992 — and Oracle crossed a $900 billion market capitalization for the first time.

The re-rating was not about Oracle's software. It was a market verdict that AI capacity is now sold forward: contracted backlog, not quarterly revenue, is the number that moved the stock, and the same week's ASML-Mistral round showed capital chasing the same thesis from the venture side.

WHY IT MATTERS

Booked backlog is a supply signal: if $455B of compute is contractually committed years out, spot inference capacity gets tighter and cheaper per-token pricing gets less predictable for anyone without a reservation. Two concrete implications — model your inference spend against reserved capacity rather than on-demand rates, and treat single-vendor cloud commitments as concentration risk, since a 36% one-day re-rating on backlog is also a warning that capacity supply is being locked up by a small number of very large buyers.

TUE · Sep 9, 2025fundingeuropeopen weightslicensing

ASML puts €1.3B into Mistral at an €11.7B valuation

Mistral AI closed a €1.7 billion Series C at an €11.7 billion post-money valuation, more than doubling the €6 billion mark from its 2024 round. ASML led with €1.3 billion and took roughly an 11% fully diluted stake plus a seat on Mistral's Strategic Committee; Andreessen Horowitz, Bpifrance, DST Global, General Catalyst, Index Ventures, Lightspeed and Nvidia participated.

The strategic logic runs both ways: ASML gets AI tooling aimed at lithography — predictive maintenance and throughput optimization — and Mistral gets Europe's most strategically protected industrial shareholder. The round landed 24 hours before Oracle re-rated 36% on booked AI cloud backlog, which is the week's real pattern: the capital markets paid for compute commitments, not for models.

WHY IT MATTERS

For anyone selling into European public sector or regulated industry, the base-model license is a procurement artefact, not a preference: Mistral ships open-weight models structured to qualify for the EU AI Act's open-source exemption, and its shareholder base now includes a lithography monopoly, which makes a Mistral-versus-US-lab choice partly a supply-chain sovereignty decision. If EU sovereign deals are in your pipeline, keep a self-hostable Apache-2.0-class path in your architecture instead of a single closed API dependency.

MON · Sep 8, 2025agent infrastructuremcptooling

MCP gets an official registry — server discovery becomes a versioned API

The Model Context Protocol project launched the MCP Registry in preview at registry.modelcontextprotocol.io, described in the launch post as an open catalogue and API for publicly available MCP servers to improve discoverability and implementation. The registry and its parent OpenAPI specification are open source so third parties can build compatible sub-registries. It is maintained by a registry working group with maintainers from PulseMCP, Block's Goose team, GitHub and Anthropic.

Moderation is community-driven: anyone can file an issue flagging a server for spam, malicious code or impersonation, and maintainers can denylist entries and remove them from public access. The preview carries no data-durability guarantees and the maintainers explicitly warn that breaking changes may occur before general availability. Practically, server discovery has moved from curated README lists and copy-pasted URLs to a namespace that clients query at runtime — with the registry acting as an index of self-reported metadata, not an audit.

WHY IT MATTERS

If your agent resolves tools at runtime, you now have a versioned HTTP contract to pin against instead of a hardcoded URL list — but the preview promises no stability and no review, so treat every entry as untrusted input: vendor the manifest, check the repository field, and put the package install step behind your own allowlist rather than trusting a denylist that only reacts after someone reports abuse.

ARCHIVE

Go back in time

Every dispatch, newest first. Each week is written once and left as it was published.