The MTEB leaderboard is a prior, not an oracle. The model that wins your RAG system is the one you measure on a few hundred of your own labeled queries — here is how to build that eval.
A deep research agent hands you a long, confident, well-structured report. Grading it means measuring two different things at once — how good it reads, and whether a single sentence is actually supported.
An open-weight model is now within a point of Claude Opus on long-horizon coding benchmarks. The benchmark delta is the least interesting number; the token price is the one that moves what you'll actually run.
Deploy a LangGraph agent and it auto-publishes a /mcp endpoint, so any client can call it as a tool. Convenient — and lossy. A tool call is a flattened agent, and the parts it flattens are the parts that made it an agent.
Write the eval before the prompt. The test suite you build first is the only thing that lets you change models next month without praying — and in 2026, you will change models.
The Digital Omnibus pushed the high-risk rules to 2027 — and most builders read that as a reprieve. But the deadline that actually catches a typical agent never moved at all.
Both vendors shipped an official agent SDK, so the choice looks like a feature bake-off. It isn't. They sit at different layers and bet on different hard parts — and their defaults decide which one your problem is one line of code away from.
All three hyperscalers now sell a managed home for your agent. Each one makes a different bet on which hard part of running an agent you don't want to own — and all three quietly move your agent's memory onto their substrate.
The metric you'd reach for first — CPU, then GPU utilization — is the one that lies. A 70B pod can read 5% CPU and a calm GPU dial while its request queue backs up for miles. Scale on queue depth instead.
Mozilla's any-llm and LiteLLM get pitted against each other constantly, but they answer different questions — the only one that matters is whether you actually need a proxy.
Microsoft, Okta, and AWS all shipped the same first move against unmanaged agents — an inventory. It's the shadow-IT playbook again, except this time the thing you can't see replicates itself.
A new Senate discussion draft reads like a privacy bill, but its teeth are an interoperability mandate — the first U.S. attempt to give users a right to bring an agent onto platforms that would rather keep it out.
The Agent2Agent protocol now claims 150-plus organizations and a slot in every major cloud. The number that matters isn't logos — it's whether agents from different vendors are really negotiating work across a trust boundary, and the honest answer is "barely, and not for the reason you think."
Everyone tunes a tool's inputs — name, schema, description. The likelier production failure is the output: the right tool returns a payload that floods the model's context window.
Most agents summarize their context when a token counter trips. A 2026 result argues the counter is the wrong trigger — and that letting the model decide is both cheaper and more accurate.
SSE hands you a Last-Event-ID header that looks like free stream resumption. It isn't — it's a cursor with nothing behind it. The real fix is the one decision everything else follows from.
Every other latency fix speeds up the typical request. Hedging is the only one that attacks the slow tail — by firing a duplicate after your p95 and taking whichever finishes first.
RAG gives the model an open book; fine-tuning makes it memorize. RAFT does the thing neither does — it trains the model on bad retrieval, so it survives the wrong chunk your production retriever will hand it.
Every LLM-tracing vendor now sells the same promise — open, portable, OTel-native. The schema that makes that true isn't finished, and there's an env var to prove it.
A reranker and a diversity step look like the same 'advanced RAG' upgrade. They fix opposite failures — and the benchmark that everyone cites quietly shows that turning on diversity often does nothing at all.
Mixture-of-Agents wins by quality, not by variety — and a careful 2025 replication found that aggregating repeated samples from your single best model beats mixing different ones in most cases. Here's when an ensemble actually pays, and when it just adds latency.
The 2026-07-28 spec made MCP stateless. Long-running work and statelessness are in direct tension — and the Tasks extension resolves it by handing the bookkeeping to the client. The tell is what got deleted.
The next Model Context Protocol release stops adding features to the core and starts subtracting them. The Extensions framework is how — and 'in the spec' no longer means 'in the core.'
Both kinds of cache hit read at the same discount, so cost-per-hit is the wrong thing to choose on. The real split is a guarantee you pay for versus a freebie you can't shape.
A JSON object isn't valid until its closing brace — but your UI shouldn't wait for it. The trick is realizing a streamed object is a view, not a value, and validating it exactly once: at the end.
The SDK's 10-minute default times out one call; an agent makes dozens. You need a deadline the whole loop shares — and cancelling to enforce it still costs tokens and can corrupt state.
An agent has no ROLLBACK: when step three fails, the first two already happened in the world. The fix is a compensating undo for every tool — and putting the one you can't undo last.
Your agent can be HTTP-200, fast, and cheap while being completely wrong. The metrics that keep a web app healthy are blind to the ways an agent actually fails.
For an app built on a hosted LLM API, the wall you hit under load isn't the model's speed — it's the provider's rate limiter and your own retry policy. Test for the ceiling and the fall, not the throughput.
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.