This month's interesting work was in the machinery around the model: who checks the output, what runs above the agents and who pays for it all.
Practitioners published their bills
Simon Willison shipped a release of a library he has maintained for years and wrote down the cost: $149.25 of API spend, 37 prompts, 34 commits, most of the code written by Claude Fable. The main session was $141.02. Five review agents cost between $0.32 and $2.40 each, and one found a connection-poisoning bug that had survived his own testing. Having GPT-5.5 review Fable's work surfaced further transaction edge cases. Cross-model review costs almost nothing and catches things the author doesn't.
Verification is now the bottleneck, and Addy Osmani makes the case best in Own the Outer Loop: the inner loop (investigate, implement, verify) goes to the agent, while the outer loop (quality signals, the ship-or-block verdict, answerability for it) stays with a human. He cites 42% of committed code now AI-generated or AI-assisted per Sonar, and 73% of people in a Wharton study accepting incorrect AI output and feeling more confident afterwards.
Hamel Husain tested automated trace analysis against real production data. It spots issues humans miss, and misses anything that needs domain expertise or taste. His recommendation is iterative use with a human in the loop, the same shape from a different direction.
Two things stayed contested:
- Whether coding is finished. Boris Cherny said on Lenny Rachitsky's podcast that coding is "largely solved" for the work he does. Osmani answers that "the last mile, edge cases, architecture, taste, is the whole game". The two are not in dialogue, and Cherny's remark is months older. The gap is really about which part of the job you're counting.
- Whether better models are better tools. Armin Ronacher found that newer Claude models, on tool schemas unlike the shapes they trained against, invent extra fields in the call: roughly a 20% failure rate in one Opus 4.8 session, eliminated with strict tool invocation mode.
Worth trying:
- Run a review agent on a cheap model against your own diff before a human sees it.
- Have one vendor's model write and a different vendor's model review.
- Turn on strict tool invocation if your provider has it.
- Write down who owns the verdict for each class of change, and what evidence they need to see.
The repos were all parts around an agent
This month's movers on GitHub are mostly parts around an agent, and they fall into four categories.
Packaging. microsoft/apm is a dependency manager for agent configuration, with a manifest and a lockfile covering skills, plugins, instructions and MCP servers. NVIDIA/skills publishes agent skills for NVIDIA's own products, which makes skills a distribution channel rather than a user convenience. The quotable version came from Google DeepMind's Philipp Schmid at the AI Engineer World's Fair, via Latent Space: "Agents are just files."
Portability. lidge-jun/opencodex points Codex or Claude Code at any model. oomol-lab/open-connector puts 1,000-plus SaaS providers behind an MCP interface.
Fleet supervision. stablyai/orca, herdrdev/herdr and omnigent-ai/omnigent all answer the same question: what runs above several agents at once. That is Osmani's outer loop, being built in public. orca's 2,880 open issues are the number to look at; on a bookmark-bait repo that is near zero.
Context economy. MinishLab/semble returns ranked code chunks to an agent instead of whole files, and self-reports about 98% fewer tokens than grep-and-read on its own benchmark. It installs without an API key and the claim is falsifiable on your own repository in about a minute, so it was the one to clone.
The one to skip was DietrichGebert/ponytail: 93,370 stars in fifty days, the biggest AI repository of the month, shipping no software. It's a set of markdown rules, with one author, one repo and one benchmark.
MCP also got interesting again because it got simpler. After the 28 July spec revision, Willison, who had drifted away from the protocol, built three implementations in a week. His stated reason is the security story, not the ergonomics.
The money narrowed, and buyouts left software
Nvidia appeared on three sides of the capital market inside four weeks. It led Safe Superintelligence's $5 billion round, joined Together AI's $800 million Series C, and is reported to be in talks to guarantee roughly $250 billion of OpenAI financing. Reuters could not independently verify that last one, so treat it as reported and unconfirmed. Even on that reading, the largest supplier in the market is funding its own demand. Whether that is ordinary vendor financing at a new scale or a circular arrangement is open, and both readings fit the same facts.
PitchBook puts US venture funding at $412.7 billion for the first half, with AI taking $355.9 billion of it, 86 cents in every dollar. Crunchbase finds 60% of global funding went into rounds of $1 billion or more. That is a narrow market with very large cheques in it. Abu Dhabi's MGX closed Fund I at $49 billion, the largest dedicated AI fund raised.
Private equity did close to the opposite. US platform buyouts in software fell to a decade low: $16.24 billion in the first five months, a run rate around a quarter of 2025's record $156 billion. The figures come via syndication, so treat the precision with a little caution; the direction isn't in doubt.
The money went into people-heavy services businesses instead. GTCR-backed Experity acquired Exdion Healthcare with an explicit AI thesis: sponsor owns a platform with distribution, buys the automation, applies it to a back office that already has the customers. General Catalyst has allocated $1.5 billion to AI-enabled roll-ups, claiming agents can automate 30 to 70% of workflows in fragmented services; no independent verification of that range exists. Grant Thornton Advisors agreed to acquire CBIZ for $5 billion, but the release is about scale in professional services and doesn't present it as an AI deal. Anyone telling you it is one is inferring.
Watching
Whether the Nvidia and OpenAI arrangement ever appears in a filing; until then it's only reported.
Consolidated from the engineering, open-source and venture briefs my research agents compiled at the time, so it reflects what was known on 1 August.