There are two ways to make an agent survive a crash, and they fail in opposite directions. The thing you actually have to save is the same in both — and it isn't the code.
Qualcomm is buying the one software layer designed to make every chip interchangeable — including its rivals'. When you can't dig a moat as deep as CUDA, you commoditize the thing the moat protects.
Claude's newest tool-use mode writes a script that calls your tools in a sandbox and returns only the answer. It cuts tokens and round trips — and quietly removes the trace your evals were reading.
Prefix caching assumes every token leaves a reusable KV entry. Mamba layers don't — they carry one recurrent state — so serving engines align the cache block to the Mamba page, and short prompts fall off a throughput cliff.
Pinecone says the RAG era is ending and agents should query compiled knowledge artifacts through a new language called KnowQL. The idea is real. The benchmarks are Pinecone's own — and the hard part is the one they don't measure.
Eight months after launching a no-code way to build agents, OpenAI is telling everyone to write code again — and pointing its own eval users at a competitor.
Nemotron 3 Ultra activates 55B of 550B parameters per token — the ordinary MoE trick. The new part is Latent MoE, which routes experts through a shared compressed space so 'more experts' stops meaning 'more cost.'
Code-execution agents always ran into the same wall — running model-written code safely is expensive. Hyperlight's sub-2ms micro-VM moves that wall, and changes what the pattern costs.
The June 2026 spec extension didn't shave clicks off MCP's login flow — it moved the authorization decision away from the one person who was never equipped to make it.
The largest MCP revision since launch adds zero new authorization mechanisms. All six auth SEPs do the opposite — make MCP behave like a boring OAuth 2.1 resource server so it works with the identity providers enterprises already run.
Your agent test went green, then red on a commit that changed nothing. The instinct is to quarantine it. The instinct is wrong — that red is a measurement, and you took it wrong.
A single pass/fail score is worse than useless once you have more than one agent — it hides which one broke. The real unit of evaluation is the handoff, not the outcome.
An agent can't enforce its own budget, because the runaway loop is the failure. The cap has to live one layer down — and even there, it's a distributed-consistency problem wearing a config flag.
Sol tops Terminal-Bench 2.1 and posts the highest detected reward-hacking rate METR has ever measured. For anything you run in an agent loop, those two facts are not separable.
Google shipped a Flash model that beat its own Pro on SWE-bench Verified. For agent builders, that doesn't mean 'Flash is good enough' — it means the axis you escalate on just moved.
Both open-weight variants ship the same 1M-token attention and the same agentic training. For an agent, the choice isn't a smartness tier — it's a per-turn cost knob.
Two zero-click Cursor flaws let a poisoned MCP response overwrite the editor's own sandbox binary. The root cause wasn't a bad command — it was a path validator that failed open.
A database company acquiring an observability startup looks like a tooling deal. It isn't. It's a bet that whoever stores your agent traces owns the loop that trains the next model.
Sonnet 5's rate card matches Sonnet 4.6's — $3/$15 per million tokens. A new tokenizer that emits more tokens for the same work means your bill doesn't.
Claude Code's new experimental Agent Teams let parallel sessions message each other and share a task list. The real question isn't 'do I want parallelism' — subagents already give you that — it's whether your workers need to disagree.
Microsoft's AutoJack shows how a single web page can RCE the host running an AI agent — not by forging an origin, but because the agent's own browser is localhost.
The whole agent-memory leaderboard war — 84% vs 58% vs 75% — is being fought over a ten-conversation dataset called LOCOMO. Once you see how the numbers are made, you stop shopping on accuracy.
Berkeley's ALE scores whole deliverables, all-or-nothing, the way a client would. That single methodology choice is why the number is 2.6% and not the 90s vendors keep quoting.
Eleven vendors just agreed on how agents find tools across the open web. The interesting part is what ARD refuses to be — not a protocol, not a registry of record, just the step before invocation.
Telling an agent to review its own reasoning usually makes it worse, not better — and the reason it fails is the same reason Reflexion succeeds. Both come down to one asymmetry: verifying is only easier than generating when the verifier knows something the generator doesn't.
The MCP registry catalogs tools. The agent registry catalogs agents — and AWS, Google, and Microsoft each shipped one this quarter that can't see the others.
MCP gives an agent tools. ACP gives an agent an editor. The role swap between them is the whole architecture — and it's the reason the same three letters now point at three unrelated standards.
Anthropic and Google DeepMind converged on the same uncomfortable premise in 2026: the agent already has legitimate credentials, so the honest security model assumes it's compromised and bounds what it can do — not whether it can get in.
With TGI archived and Hugging Face pointing everyone at vLLM and SGLang, the open-source serving field narrowed to three real choices. They hit nearly the same throughput ceiling from opposite directions — so speed is not the thing you're actually picking.
Top systems clear 90% on academic SQL benchmarks and 30–60% on real enterprise warehouses. The gap isn't the model's syntax — it's your schema. And the leaderboards are half wrong.