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.
Gartner says purpose-built agent software more than doubles to $206.5B this year. The same firm says 40%+ of agentic projects get canceled. Both numbers are true, and they're the same story.
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.
The query assumes three live standards fighting for the agent-to-agent layer. Two of the three answers are already settled — and the third isn't even in the same race.
The choice isn't speed versus security. It's whether the model is writing code that orchestrates your tools or code that needs the whole operating system — and that picks the security model for you.
SWE-bench hands an agent a broken test and a healthy repo. Terminal-Bench hands it a live machine and lets it break things. That's why a top SWE-bench score tells you almost nothing about the second number.
The number on the spec sheet is a memory allocation, not a comprehension score. A needle test passing at 1M tokens tells you the model can find a string — not that it can use the context. Here's the benchmark that measures the difference.
A new benchmark replays an agent's failures into a corrupted environment and asks a fresh model to fix them. The leaderboard reorders — recovery is not the same skill as solving.
You can freeze an agent run and play it back in CI — but there are two layers you can record at, and picking the wrong one means your tests stop catching the bug you actually care about.
A classifier that blocks 98% of injections sounds like a fix. Against an attacker who can retry, a nonzero bypass rate isn't a wall — it's a toll. The defenses with real guarantees don't detect the bad instruction at all; they cap what any instruction is allowed to cause.
The reflex is to wrap everything in JSON because it's 'structured.' On the way into a prompt that's a token tax; on the way out it's an accuracy tax. The right answer is split, not single.
Every provider now sells the same ~90% discount on repeated context. The number on the brochure is not where the bills actually diverge — three quieter terms are.
OWASP now has a third Top 10 — one scoped to a single protocol. The surprise isn't a new class of AI attack; it's that connecting an agent to MCP servers re-exposes 2010-era web and supply-chain bugs through a channel that auto-executes them.
One of these isn't an inference engine at all — it's a wrapper around the other two. Sorting that out is the whole decision, and it just got simpler because one contender quietly left the race.
The number at the top of the MTEB leaderboard has quietly stopped meaning what you think it means. Here is which board to read, and why the newest one hides half its test set on purpose.
The 2026-07-28 release candidate kills the session and the handshake, graduates Tasks and Apps to extensions, and deprecates Sampling. The real story isn't statelessness — it's a shrinking core.
Decode is memory-bandwidth bound, so a GPU's TFLOPs barely predict serving capacity. What caps concurrency is the KV cache. Here's the actual arithmetic, with a worked example.
They ship the same orchestration patterns now, so stop comparing them on patterns. The real fork is where your production agent actually runs — in code you hold, or in a cloud you rent.
The provider's per-user field won't give you an invoice, and raw token counts lie. The honest unit of attribution is the priced token — after caching, batching, and hidden thinking.
You can't script a conversation, so you hand the user's seat to a second LLM. That move doesn't solve your measurement problem — it relocates it into a simulator you never validated, and the default one grades on easy mode.