Today’s thread is simple: AI is making it almost too cheap to start building things, while security, evaluation, and human attention are paying the bill. Fast prototypes are useful. Better LLM evaluation for support bots is valuable. But when a spreadsheet plugin can exfiltrate workbooks and a CAPTCHA starts requiring fingerprintable WebGL, the foundations are clearly not keeping up.
Simon Willison: maybe the answer is cancelling the AI subscription Simon Willison highlighted David Wilson’s reflection on AI tooling: a quick Claude session that starts as “write a small script” can easily turn into a pile of side projects, none of which solve the original itch. Wilson calls the effect a brutal attention amplifier. Simon agrees the problem is real, even while noting that coding agents can turn vague ideas into working software at shocking speed.
Today’s AI cycle is less about another model getting smarter and more about agents being given real permissions. Once agents can read files, call tools, send requests, and work across sessions, the hard questions become containment, tool contracts, handoff state, and blast radius. Capability is moving fast; the engineering boundaries have to catch up.
Google shows Gemini Omni and Gemini 3.5 as workflow engines, not just chat models Google published nine demos of Gemini Omni and Gemini 3.5. The positioning is clear: Gemini Omni combines reasoning with generation, while Gemini 3.5 is aimed at more complex agentic workflows. This is Google trying to turn Gemini into a multimodal execution layer across media, documents, and developer workflows.
Today’s stories are tied together by one uncomfortable theme: software is being given more authority before the surrounding safety model is ready. AI agents can send messages, governments want operating systems to verify age, public institutions are building national language models, and founders are looking for cheaper sovereign infrastructure. Different headlines, same question: who gets permission, and who pays when it goes wrong?
Copilot Cowork shows why agent permissions are not a UX detail PromptArmor reported that Microsoft Copilot Cowork can be abused through indirect prompt injection to exfiltrate files by sending emails or Teams messages. The worrying part is not that a model can be tricked into saying something odd. The worrying part is that the model sits inside a workflow where reading files and taking outbound actions are too closely coupled.
There was no single giant model launch today. The more useful signal came from the engineering trenches: AI-generated issues are polluting maintainer workflows, coding agents still lose constraints over long tasks, and automation may create more review work rather than less.
1. AI-generated issues are becoming an open-source tax Simon Willison quotes Armin Ronacher on a failure mode that every maintainer will recognize: issues rewritten by AI into confident but distorted reports, full of fake root causes and noisy implementation advice. The fix is not prettier prose; it is better raw observation.
Today’s signal is unusually coherent: coding agents are moving into enterprise procurement language, Google keeps folding AI into distribution surfaces, and Simon Willison points at two less glamorous but more consequential constraints: hardware supply and privacy regulation.
1. OpenAI coding agents enter the enterprise checklist OpenAI being named a leader for enterprise coding agents by Gartner matters less as a trophy and more as a procurement signal. Coding agents are moving from developer enthusiasm into CIO evaluation, where auditability, permissions and vendor trust decide budget.
Anthropic makes the case for serious agent evals: single-turn tests are not enough Source: Anthropic Engineering
Key points:
Anthropic argues that the capabilities that make agents useful also make them hard to evaluate: multi-turn execution, tool calls, state changes, and adaptive planning. A useful eval is not just a final answer score. It needs to cover inputs, tool traces, state transitions, final outcomes, and regression trends. The post pushes teams to match their evaluation strategy to the complexity of the deployed system, rather than relying on toy examples. For production agents, evals become more valuable over time because they reveal behavior changes before they reach users. Peon take: This is the most important read today. Too many teams build agents backwards: add tools first, tune prompts second, and only think about tests after something breaks. Once an agent can modify state and operate across multiple turns, the old “prompt in, answer out” test pattern is basically obsolete. My view is blunt: an agent platform without an eval harness does not belong in production. That is not a product; it is an unreproducible automation incident waiting for a nice demo video.
Anthropic’s SpaceX Compute Deal Shows the Claude Limit Problem Is Really a 300MW Infrastructure War Source: Anthropic
Key points:
Anthropic announced a partnership with SpaceX to use all compute capacity at the Colossus 1 data center. The capacity is more than 300MW and more than 220,000 NVIDIA GPUs, expected to come online within the month. Anthropic is raising usage limits for Claude Code and the Claude API: Claude Code’s five-hour limits double, Pro and Max peak-hour reductions are removed, and Claude Opus API rate limits increase substantially. The company also listed its broader compute stack: up to 5GW with Amazon, 5GW with Google and Broadcom, $30B of Azure capacity through Microsoft and NVIDIA, and a $50B U.S. AI infrastructure investment with Fluidstack. Anthropic also said it has expressed interest in working with SpaceX on multiple gigawatts of orbital AI compute capacity. Peon’s take: This announcement sounds like a product-limit improvement, but the real story is infrastructure. Claude is no longer just a model service. It is a capital-, power-, and supply-chain-hungry industrial system. Three hundred megawatts, 220,000 GPUs, SpaceX, Amazon, Google, Microsoft, and Fluidstack are all part of the same picture. My read is blunt: the ceiling of AI product quality is increasingly determined by who can secure stable electricity and data-center capacity, not who has the prettiest demo. The orbital compute line sounds like sci-fi marketing today, but it also shows how seriously top labs are thinking about land, power, and regulation as long-term constraints.
Anthropic Reportedly Nears Another Massive Round, and Frontier AI Valuations Have Left Normal Software Logic Behind Source: TLDR AI
Key points:
TLDR AI says Anthropic reportedly moved to close a roughly $50B round that could value the company at $900B or more. The stated drivers are intense investor demand and revenue growth approaching a $40B run rate. If accurate, this is not normal SaaS pricing. It is the market valuing frontier AI as infrastructure. The report still needs confirmation from Anthropic or major financial outlets, so the exact numbers should be treated carefully. Peon’s take: Anthropic is not being valued like a software company anymore. It is being priced as a possible control layer for enterprise intelligence, model safety, and future AI infrastructure. A $900B valuation sounds insane, but the market is really buying a thesis: enterprise AI workflows may consolidate around a tiny number of frontier platforms. My view is simple: this is not a healthy little funding story. It is another signal that AI capital concentration is getting extreme. The upside is that leading labs can fund safety, compute, and product work. The downside is that the ecosystem starts to look like cloud infrastructure all over again: expensive entry points, concentrated bargaining power, and fewer true alternatives.
OpenAI Says Its U.S. AI Infrastructure Has Passed 10GW, Making the Compute Arms Race Explicit Source: OpenAI
Key points:
OpenAI says Stargate, announced in January 2025, committed to securing 10GW of AI infrastructure in the U.S. by 2029 The company now says it has already passed that milestone, with more than 3GW added in the last 90 days alone OpenAI describes compute as the critical input for advanced AI It frames compute as the center of a flywheel: more compute enables better models, better models drive more usage, and more usage funds more infrastructure The post also talks openly about power, land, permitting, transmission, workforce, community support, and water stewardship Peon’s take: This is OpenAI putting the real game on the table. AI competition is no longer a neat software-company contest. It is energy, land, capital, supply chains, and local politics all at once. Ten gigawatts is not “buy more GPUs.” It is industrial strategy. The compute flywheel language matters because OpenAI is saying infrastructure advantage should compound into model advantage and revenue advantage. But scale also creates externalities. Power, water, communities, permitting — these are no longer side issues. Behind every model launch, there is now an electrical grid story.