The try/except instinct that keeps a normal program alive is the one that kills an agent. A tool error isn't an exception to catch — it's the next message in the conversation, and where you put it decides whether the agent can recover.
A reranker can only reorder what your retriever already fetched, so the ceiling on its lift is your stage-one recall — measure that first, then judge the reranker as the latency and dollars you pay to convert recall into precision.
An agent isn't a stateless web service — it's a long-running, resumable process. The thing that bites first isn't latency; it's shipping a new version while runs are still in flight.
Static benchmarks freeze the world while an agent thinks. Meta's GAIA2 lets time run — and the smartest model, GPT-5, turns out to be the one that misses deadlines.
The first rigorous benchmark of repository context files is in, and the answer is uncomfortable: the auto-generated ones make agents slightly worse, the hand-written ones barely help, and both raise your bill ~20%.
The two halves of every LLM request fight each other on the same GPU. Disaggregated serving splits them onto separate hardware — and the win is real, but only past a certain scale.
An agent leaderboard that ranks only on accuracy is secretly ranking on willingness to spend. Add the cost axis and the board's #1 is often not even on the frontier.
For a year the question that stalled enterprise bets on MCP was 'what happens when Anthropic changes its mind?' In December that question got an answer — and the answer reveals what the standards war was really about.
Vercel's new agent framework treats an agent as a directory of files. LangGraph hands you a portable graph. The decision isn't the loop they run — it's who owns the production stack wrapped around it.
Trainium2 and Inferentia2 sell real price-performance and AWS capacity. NVIDIA sells CUDA. The decision is whether the Neuron SDK supports your model and serving stack — and how much engineering you'll spend finding out.
Prompt and semantic caches store the model's work and fail cheaply. Tool-result caching stores the world's — and it forces a question every agent codebase has dodged: which tools are safe to cache?
Most agent benchmarks hand the whole task to the model. τ-bench keeps the user in the loop, and τ²-bench gives the user their own hands — which is where frontier agents quietly fall apart.
A new benchmark drops the same models from ~73% to ~25% — not by making the bugs harder, but by taking away the one thing SWE-bench always handed over: a map to the change.
The same models that ace SWE-bench Verified collapse on its successor. The gap isn't difficulty — it's the size of an illusion, and the only durable fix turned out to be a software license.
Four ways to make an agent fix its own mistakes. Three of them quietly outsource the judgment to the world — and the one that doesn't is the one the research keeps catching in the act.
Builders keep wiring diarization into the live loop of a one-on-one voice agent. There, it solves a problem you don't have — because you already own one of the two voices.
Both pack weights into the same E2M1 four-bit float. The fight is entirely about the block scale — and that one design choice decides whether you keep your accuracy or hand it to the open standard.
Microsoft stopped shipping orchestration patterns and started shipping the runtime underneath them. The three Build 2026 launches are all below the framework — and one of them quietly retires the JSON tool-call loop.
The most common serious flaw in MCP servers isn't prompt injection. It's SSRF — the boring, pre-AI bug that sank Capital One — and we just installed it by the thousand.
The first official MCP extension lets a server ship an interactive interface into the chat, not just a string. The clever part is a flag that says who each result is for.
Reranking quietly split into three architectures in the last year. They make the same accuracy-for-latency trade in different places — and the newest, highest-scoring tier is the one you can least afford on a hot path.
Deep Agents isn't a fourth framework competing with LangChain and LangGraph — it's a preset of LangChain middleware on the same runtime. The choice is how much opinion you want pre-assembled.
Three of these throw tokens away to save memory. One keeps them all and just reads less — and for a long-running agent that revisits its own past, that difference is the whole game.
Nous Research's Hermes is the agent everyone's calling self-improving. It is — but the part that improves isn't the model. It's the harness writing its own skills.
Prompt engineering tuned the words. Context engineering managed the window. The discipline that decides whether an agent ships is the deterministic code around the model — and it is older than it looks.
The year's quietest architecture shift is agents moving their memory out of vector stores and into plain files. It isn't that memory got better — it's that teams stopped using a retrieval tool for a state problem.
Anthropic tried to give programmatic Claude usage its own bill, then reversed it on the day it was due. The retreat doesn't fix the problem it exposed.
The benchmarks for web-browsing agents split along a fault line the coding benchmarks never had — and the trick that makes one of them work quietly hides which half of your agent is actually good.
MCP standardized how agents connect and A2A standardized how they talk. The Agent Control Specification standardizes the part that decides whether you can deploy — what an agent is allowed to do — and its smartest move is what it refuses to standardize.