LangChain Deleted Its Agent's System Prompt and Todo List. The Evals Didn't Notice.
LangChain's Deep Agents v0.7 cut base input tokens 65 percent, from 5,395 to 1,895 a turn, by deleting its own system prompt, trimming tool descriptions that duplicated the schemas, and demoting the write_todos planning tool to opt-in after evals showed it was not earning its keep. The lean harness was not cheaper on every model, which is the part worth measuring before you copy it.
An Agent Took Astro's Issue Count From 200 to 30. Its Failures Were the More Useful Output.
Cloudflare drove Astro's open issue backlog from over 200 to roughly 30 with a four-phase triage agent, and the design choice that made it work was letting an isolated verification agent conclude there is no bug. The more durable result is what the failures revealed: every run the agent could not finish pointed at an opaque abstraction, a missing comment, or a thin test.
Google's Best Bug Hunter Is a Small Model Run Five Times. You Can't Have It.
On July 21 Google shipped Gemini 3.5 Flash Cyber, a small fine-tune that found 55 confirmed vulnerabilities in V8 against 36 for Opus 4.6, by being called up to five times inside CodeMender. The recipe is copyable. The model is not: it goes to governments and trusted partners only.
AWS Started Metering Coding Agents Like Infrastructure. The Metrics Came From the IDE Era.
On July 20 Amazon CloudWatch shipped Coding Agent Insights, ingesting OpenTelemetry metrics straight out of Claude Code, Codex and GitHub Copilot. The coding agent moved from the tools budget to the infrastructure budget, which is the right call. The metric set is not: tokens, cost, sessions, lines of code, commits and edit acceptance all measure the middle of the work, the part the agent took over.
AI Context Windows Got 10x Bigger. Nobody Changed Their Architecture.
Million-token context windows changed everything about what's possible, but most teams are still building for 4K limits.
The Pilot-to-Production Gap Is Where AI Projects Go to Die
GPT-5.4 can handle a million tokens. But most application architectures were designed for 4K-32K contexts, and the jump to 1M doesn't just expand capacity, it breaks fundamental assumptions about how you build.
Prompt Caching Is the Difference Between a Viable AI Product and a Bankrupt One
Claude Code treats prompt cache misses like server outages. The engineering behind that decision saves millions in API costs.
Your AI Stack Is Already Legacy
The frameworks and abstractions built twelve months ago are already getting in the way. The models got good enough that the middleware became the bottleneck.