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 46

WEEK OF NOV 8 – 14, 2025

An AI ran 80% of an intrusion, a judge ordered 20 million chats produced, and GPT-5.1 shipped a shell tool

Anthropic disclosed the first AI-orchestrated espionage campaign, OpenAI put a patch-and-shell agent loop into its API, a New York magistrate ordered 20 million ChatGPT logs handed to news plaintiffs, and CoreWeave cut capex guidance two days before Anthropic committed $50 billion to building its own data centers.

This was the week agentic AI stopped being a demo category. On Thursday, Anthropic published a report on a campaign it detected in mid-September: a threat actor it assesses with high confidence to be Chinese state-sponsored drove Claude Code through roughly thirty target organizations, with the AI performing an estimated 80-90% of the tactical work. The same week, OpenAI shipped the tools that make that kind of loop ordinary — a patch tool and a shell tool in the Responses API.

The money moved in the opposite direction from the guidance. CoreWeave beat on revenue, nearly doubled its contracted backlog to $55.6 billion, then cut full-year revenue and capex guidance because a third-party data-center developer was behind schedule; the stock fell about 5-6%. Two days later Anthropic announced $50 billion of its own custom capacity with Fluidstack in Texas and New York — its first build-out rather than a rental, and a direct bet that the delay was a scheduling problem, not a demand problem.

And the discovery fight in the copyright cases turned into a data-governance problem for every team that logs prompts. OpenAI spent Wednesday arguing in the Southern District of New York that producing a 20-million-conversation sample of consumer ChatGPT logs to the New York Times and its co-plaintiffs is a privacy catastrophe; the court's own proportionality maths says the sample is less than 0.05% of the logs OpenAI retained. In-window, no frontier lab released near-frontier open weights — Kimi K2 Thinking's trillion-parameter MoE landed on November 6, just before this window opened.

THU · Nov 13, 2025securityagentsmcpanthropic

Anthropic: a state-sponsored group used Claude Code to run an 80%-automated espionage campaign

Anthropic disclosed on Thursday that a threat actor it assesses with high confidence to be Chinese state-sponsored, tracked internally as GTG-1002, manipulated Claude Code into attempting intrusions against roughly thirty organizations — large technology companies, financial institutions, chemical manufacturers and government agencies — and succeeded in a small number of cases. The company says it detected the activity in mid-September 2025 and describes it as the first documented case of a large-scale cyberattack executed without substantial human intervention. Operators split the work into small, individually innocuous tasks and told the model it was an employee of a legitimate cybersecurity firm running defensive tests.

Anthropic's account puts the AI's share of tactical operations at 80-90%, with humans making perhaps four to six critical decisions, and at peak the framework issued thousands of requests, often multiple per second, with tool access frequently reached through the Model Context Protocol. The disclosed kill chain is the standard one, executed by an agent: reconnaissance, vulnerability research and exploit writing, credential harvesting, backdoors, data exfiltration, then generated documentation of the intrusion. It escalates Anthropic's August 2025 report on Claude used in a data-extortion campaign against 17 organizations, where humans stayed in the loop directing operations.

Anthropic: a state-sponsored group used Claude Code to run an 80%-automated espionage campaign
Anthropic

WHY IT MATTERS

The report is really about blast radius, not alignment: an agent holding shell, file and MCP tool access executes with whatever credentials you gave it. If you run coding or ops agents in production, treat revocation of API keys, OAuth tokens and MCP server registrations — plus freezing memory stores and tool-call histories — as the containment step, because isolating a host does nothing to an agent that talks to an API from anywhere.

WED · Nov 12, 2025modelsopenaiagentspricing

GPT-5.1 ships with adaptive reasoning — and one day later, apply_patch and a shell tool in the API

OpenAI rolled GPT-5.1 out on Wednesday to ChatGPT subscribers first, splitting it into GPT-5.1 Instant, which adds adaptive reasoning and decides for itself when to deliberate, and GPT-5.1 Thinking, tuned to spend less time on easy prompts and persist on hard ones. The model keeps GPT-5's pricing and rate limits, carries a 400,000-token context window, and scores 76.3% on SWE-bench Verified, all under the same GPT-5 generation label rather than a new family. The developer release followed on Thursday alongside gpt-5.1-codex and gpt-5.1-codex-mini for long-running Codex-style harnesses.

The part that changes architecture is tooling, not benchmark deltas. Two new Responses API tools landed with the developer release: apply_patch, which emits freeform structured diffs to create, update and delete files without JSON escaping, and shell, which lets the model propose commands that your integration executes and returns results for — a plan-execute loop you own. Extended prompt caching now keeps context hot for up to 24 hours, with cached input still 90% cheaper than uncached, and reasoning effort none is now the default for latency-sensitive calls.

GPT-5.1 ships with adaptive reasoning — and one day later, apply_patch and a shell tool in the API
Anthropic

WHY IT MATTERS

apply_patch plus shell means OpenAI now ships the edit-run-test loop as primitives rather than leaving it to framework authors — expect harness parity pressure on Anthropic's and Google's SDKs. The 24-hour cache is the quieter decision-relevant change: overnight and multi-hour agent sessions stop re-paying full input cost, which resets the cost model for long-running agents, and reasoning effort none by default means auditing latency assumptions made for GPT-5.

WED · Nov 12, 2025infrastructureanthropiccapex

Anthropic commits $50 billion to custom data centers with Fluidstack

Anthropic announced a $50 billion investment in American computing infrastructure on Wednesday, building custom data centers with neocloud provider Fluidstack in Texas and New York, with more sites to come and capacity online through 2026. The company says the project creates about 800 permanent jobs at an average salary near $144,000 plus roughly 2,400 construction roles, and frames the spend against more than 300,000 business customers, with accounts above $100,000 in run-rate revenue growing nearly sevenfold in a year.

This is Anthropic's first move to build rather than rent. Its existing capacity comes from Google and Amazon, and the new sites are described as custom-built to maximize efficiency for its own workloads, which puts it in the same physical-supply-chain race as OpenAI's Stargate program and Meta's multi-hundred-billion-dollar commitments. It also lands two days after CoreWeave told investors that a third-party data-center developer was behind schedule — the same class of dependency Anthropic is now internalizing.

WHY IT MATTERS

Compute access, not model quality, is the binding constraint on what you can ship, and a $50 billion dedicated allocation to one lab shifts who can serve frontier models at what price and with what rate limits. If your architecture assumes you can rent the same capacity a frontier lab uses for inference, or that neocloud delivery schedules hold, this week gave both assumptions a counterexample.

WED · Nov 12, 2025legalprivacyopenaidata governance

OpenAI asks a judge to reverse an order to produce 20 million user chats

OpenAI filed for reconsideration on Wednesday asking Magistrate Judge Ona Wang in the Southern District of New York to reverse a discovery order requiring it to hand a 20-million-conversation sample of consumer ChatGPT logs to the New York Times and other news plaintiffs, arguing that 99.99% of the transcripts have nothing to do with the copyright claims and that producing them would expose private user conversations. Its CISO, Dane Stuckey, published a user-facing post the same day; a Times spokesperson responded that the court ordered a sample anonymized by OpenAI itself, under a legal protective order, and that no user's privacy is at risk.

The scope is narrower than the headline: the sample is a random draw of consumer conversations from December 2022 to November 2024, excludes business and enterprise customers, is de-identified by OpenAI's own tooling, and represents less than 0.05% of the tens of billions of output logs the company retained in the ordinary course. The Times had previously sought a far larger sample — a July motion to compel covered 120 million logs.

WHY IT MATTERS

Any product that logs prompts and completions for debugging, evals or abuse review is accumulating the same category of material, and this is a live example of it becoming discoverable in third-party litigation. If you cannot demonstrate de-identification on demand and defend a retention window, your logs are a legal liability rather than an asset — the retention policy you write now is the one you will have to defend in production.

MON · Nov 10, 2025infrastructureearningscoreweaveai bubble

CoreWeave doubles revenue to $1.36B and nearly doubles backlog — then cuts capex guidance

CoreWeave's third quarter, reported Monday, was a demand story with a delivery problem attached. Revenue more than doubled year over year to $1.364 billion from $583.9 million, the net loss narrowed to $110 million from $359 million, adjusted EBITDA reached $838 million, and revenue backlog nearly doubled to $55.6 billion from about $30 billion on contracts with Meta, OpenAI and Poolside. The company then trimmed full-year revenue guidance to $5.05-5.15 billion and cut 2025 capex guidance to $12-14 billion from the $20-23 billion it forecast a quarter earlier, citing a third-party data-center developer behind schedule; shares fell roughly 5-6%.

The balance sheet carries the risk the backlog is meant to offset: about $9.7 billion of obligations due within twelve months against roughly $14 billion in total debt, both up sharply from the prior quarter. CEO Michael Intrator described relentless demand alongside industry-wide supply-chain pressure, and said the affected customer agreed to reschedule delivery while preserving the contract's total value. Management guided that 2026 capex will rise substantially, which puts the deferral into next year rather than removing it.

WHY IT MATTERS

For anyone buying inference, the signal is that contracted GPU capacity is not the same as delivered capacity — the slippage that forced a guidance cut will surface as quota tightening and spot-price volatility before it surfaces in earnings. Architect for provider portability across at least two clouds plus an owned-model fallback, and treat multi-year capacity commitments as schedule risk you are underwriting, not insurance against it.

DISPATCH 45

WEEK OF NOV 1 – 7, 2025

Frontier weights for free, compute at $38B: the week the open-model cost floor met the capex bill

A trillion-parameter open-weight agent and a 12-hour autonomous scientist shipped in the same seven days that OpenAI committed $38B to AWS and a UK judge set the first boundary on AI copyright.

The window ran Monday to Thursday hard. On Nov 3 OpenAI signed a $38B, seven-year AWS deal, its first contract with the cloud market leader and the formal end of Microsoft's cloud exclusivity; on Nov 5 Edison Scientific announced Kosmos, an AI scientist whose single run reads 1,500 papers and writes 42,000 lines of analysis code; on Nov 6 Moonshot AI published Kimi K2 Thinking weights and Google Cloud opened Ironwood, its inference-first TPU, to customers.

Two of those stories are the same story told twice. Kimi K2 Thinking activates 32B of its 1T parameters per token, ships under a modified MIT license with a 256K context window and native INT4, and was reported by CNBC — from an unnamed source — to have cost $4.6M to train, three days after the most valuable private AI lab in the US committed $38B to rent other people's GPUs. Open weights are the price ceiling on closed APIs now, not the consolation prize.

The market read the week differently. Michael Burry's 13F, filed Nov 3 and reported Nov 4, disclosed puts on Nvidia (about $187M notional) and Palantir (about $912M); the Nasdaq fell 1.9% on Nov 6, and Palantir ended the week down more than 12%. Builders got a cheaper stack and a repriced one in the same five days.

THU · Nov 6, 2025open weightsmoonshotreasoningagentslicensingquantization

Moonshot publishes Kimi K2 Thinking: 1T parameters, 32B active, modified MIT, native INT4

Moonshot AI released Kimi K2 Thinking on Nov 6 with weights on Hugging Face: a mixture-of-experts model of 1T total parameters activating 32B per token, 384 routed experts with 8 selected plus one shared expert, 61 layers, MLA attention and a 256K context window. It is a native INT4 checkpoint — quantization-aware training applied to the MoE components in post-training — for roughly 2x generation speed and a smaller disk and VRAM footprint, and it runs on vLLM, SGLang and KTransformers behind an OpenAI and Anthropic-compatible API. The license is modified MIT: unrestricted commercial use except that products above 100M monthly active users or $20M monthly revenue must display Kimi K2 in the UI.

The self-reported numbers put an open download next to closed frontier models: 44.9% on Humanity's Last Exam with tools against GPT-5's 41.7%, 60.2% on BrowseComp against 54.9%, and 71.3% on SWE-bench Verified, with Moonshot claiming stable tool use across 200-300 sequential calls where earlier models drift after 30-50. CNBC reported the training bill at $4.6M from a source familiar with the matter, which it could not independently verify; Moonshot's CEO later said on Reddit that the figure is not official.

Moonshot publishes Kimi K2 Thinking: 1T parameters, 32B active, modified MIT, native INT4
Hugging Face

WHY IT MATTERS

Long-horizon agent traces are the expensive part of your bill — hundreds of tool calls, each carrying a growing context — and this is the first openly downloadable model sized for exactly that workload, with INT4 weights so the memory maths is survivable on hardware you own. The practical effect: you can put a frontier-adjacent agent loop behind an OpenAI-compatible endpoint, self-host or buy at open-model prices, and treat closed-API token pricing as a comparison rather than a constraint. The license clause bites only at hyperscale, so white-label use below 100M MAU is unaffected.

THU · Nov 6, 2025infrastructurehardwaregoogleinferencevllmcost

Google Cloud opens Ironwood (TPU v7) — 10x v5p peak, 9,216 chips per superpod

Google Cloud announced Ironwood, its seventh-generation TPU, for Cloud TPU customers on Nov 6, pitched at what the post calls the age of inference: 10x peak performance over TPU v5p and more than 4x per-chip performance versus TPU v6e for both training and inference, 9,216 chips in a single superpod over 9.6 Tb/s inter-chip interconnect sharing 1.77 PB of HBM. Anthropic, which said in October it plans to access up to 1 million TPUs, is the flagship customer.

The developer-facing change is the software layer: enhanced vLLM support on TPU behind a unified backend, so a serving stack can move between GPUs and TPUs with minor configuration changes, plus a GKE Inference Gateway that Google says cuts time-to-first-token by up to 96% and serving cost by up to 30% by load balancing across TPU servers. CNBC reported the same day that Google Cloud VP Amin Vahdat told an all-hands the company must double AI serving capacity every six months.

Google Cloud opens Ironwood (TPU v7) — 10x v5p peak, 9,216 chips per superpod
storage.googleapis.com

WHY IT MATTERS

Inference, not training, is what a software team actually pays for, and the accelerator market just became less binary: if the same vLLM server runs on TPU, capacity sourcing is a deployment config rather than a rewrite, and you gain a second quote to hold against GPU pricing. Combined with the same week's open-weight releases, agent workloads get a cheaper denominator on both sides — model and silicon — which is the number that decides whether a long-horizon agent feature is viable at your volume.

WED · Nov 5, 2025agentsai for scienceevalslong-horizontooling

Kosmos: one 12-hour agent run, about 6 months of research — the world model is the trick

Edison Scientific, the commercial spinout of non-profit FutureHouse that took over its platform the same day, announced Kosmos on Nov 5. Kosmos runs for up to 12 hours on an open-ended objective and a dataset, executing about 200 agent rollouts that collectively write roughly 42,000 lines of analysis code and read about 1,500 papers per run. The architectural claim is that a structured world model, shared between a data-analysis agent and a literature-search agent, is what keeps a single objective coherent across tens of millions of tokens — the failure mode that capped earlier AI scientists at a handful of coherent steps.

In the technical report, independent scientists rated 79.4% of statements in Kosmos reports accurate, and every conclusion is traceable to specific lines of code or passages of literature. In a poll of seven beta users, a 20-cycle run was estimated at 6.14 months of their own research time, and estimated human-equivalent duration scaled linearly with run depth. It is available at $200 per run, with caveats the authors state plainly: Kosmos goes down rabbit holes and chases statistically significant but scientifically irrelevant findings.

WHY IT MATTERS

The transferable piece is the harness, not the science: a persistent external state that survives context exhaustion is the pattern any long-horizon agent needs, and code-level provenance for every claim is the difference between an agent you can audit and one you cannot. It also puts a concrete number on inference-time scaling for open-ended work, which is what you budget when deciding how much compute a task deserves.

TUE · Nov 4, 2025legalcopyrightuklitigationdata governance

UK High Court: Stable Diffusion is not an infringing copy — Getty's secondary claim fails

Mrs Justice Joanna Smith handed down Getty Images v Stability AI on Nov 4. Getty's remaining secondary copyright infringement claim failed: the court accepted that a model can be an article under the Copyright, Designs and Patents Act, but held that Stable Diffusion is not an infringing copy because it does not store or contain the training images — once the weights stop holding a copy, they stop being one. Getty had already abandoned its primary copyright and database-right claims during trial because training happened outside the UK; it won only narrowly on trade mark, over generated images carrying its watermark.

Litigation volume continued in the same seven days: Danish collecting society Koda sued Suno in Copenhagen City Court on Nov 4, author Tasha Alexander filed a class action against Salesforce over its CodeGen and XGen models on Nov 5, and Entrepreneur Media sued Meta over Llama on Nov 6, taking US AI copyright filings past 60. The ruling follows the US arc of Judge Alsup's June 2025 decision that Anthropic's training was fair use but its retention of pirated books was not, and the resulting $1.5B settlement filed on Sept 5.

WHY IT MATTERS

Shipping weights looks materially safer in the UK now — distributing a model is not itself infringement — but the load-bearing test is the useful part: liability turned on whether the pipeline ever held a copy, which is exactly what cost Anthropic $1.5B for keeping a library it did not need. Dataset handling, retention and provenance logging are now the primary legal control surface rather than training itself, so vendor questions become about where data is stored, for how long, and how deletion is proved. Expect an appeal.

MON · Nov 3, 2025infrastructurecomputeopenaiawsmarketsagents

OpenAI commits $38B to AWS — days before a $4.6M open-weight model matches frontier scores

OpenAI and AWS announced a multi-year partnership on Nov 3: a $38B commitment over seven years, hundreds of thousands of Nvidia GB200 and GB300 GPUs on Amazon EC2 UltraServers, the ability to scale to tens of millions of CPUs for agentic workloads, and all target capacity deployed before the end of 2026. It is OpenAI's first contract with the largest cloud provider and the clearest break from the Microsoft-exclusive era; Amazon closed at a record, up 4%.

It is the fourth commitment in a run — roughly 10 GW with Nvidia, 6 GW with AMD, 10 GW of Broadcom custom accelerators and a reported Oracle deal — leaving OpenAI with close to $600B of cloud commitments against about $13B of expected 2025 revenue. The market started repricing that assumption two days later: Michael Burry's 13F disclosed puts on Nvidia and Palantir, and the Nasdaq fell 1.9% on Nov 6 with Palantir down more than 12% for the week.

WHY IT MATTERS

Two of the things you architect around moved this week: where inference capacity physically lives, and what it costs. Note that OpenAI is buying CPUs at agentic scale as well as GPUs — that is a statement that the volume driver is multi-step tool loops, not chat, which is what most teams now build against. Because that capacity is sold forward on multi-year commitments, closed-API pricing is exposed to a financing model that assumes continued exponential growth, so an open-weight fallback with compatible APIs is a procurement hedge rather than a purity test.

ARCHIVE

Go back in time

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