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.
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.
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.
The two best independent SDK generators got bought in 2026 — Fern by Postman, Stainless by Anthropic, which is retiring its shared generator. The layer that turns an API into agent-usable tools stopped being neutral infrastructure.
Qwen3-4B, Phi-4-mini, Gemma, Nemotron 3 Nano: the pick forks on a question no leaderboard prints — are you short on memory or short on tokens-per-dollar? And the score that decides an agent isn't MMLU.
V2 went stable on June 23 after seven betas, then shipped four releases in nine days. The real news isn't the version bump — it's a bet that the winning agent abstraction is a harness, not a graph.
Most coding agents open with a ~10,000-token system prompt. Pi opens with under 1,000 and lets the model write its own tools. The bet underneath: the model already knows how to be an agent, and every instruction token is a task token you don't get back.
The NSA's Security Design Considerations for MCP reads like every other threat list until you notice its signature control points the wrong way — at the outbound wire, not the untrusted server. That inversion is the whole document.
M3 claims to beat GPT-5.5 on SWE-bench Pro while running weights you can host yourself. The benchmark row is the least trustworthy thing in the release — and the architecture is the most.
The stateless rewrite got the headlines, but the quieter change is the one that tells you what MCP has decided to be. Three original primitives are on the way out — and they're the exact three where the server reached back into your runtime.
The 2026-07-28 revision closes the holes the protocol used to own. The same three headline features quietly relocate the security burden onto server code that mostly doesn't exist yet.
A North Korean crew republished 140+ Mastra packages in 88 minutes with a poisoned dependency. The scary part isn't the payload — it's that the whole attack ran before any of your agent's guardrails woke up.
A router picks a model before it sees the answer; a cascade tries the cheap one first and escalates only if a judge says so — and that judge, not the models, decides whether you actually save.
They get compared like rivals, but one is memory you program and the other is memory you call — and the benchmark leaderboard only measures one of them.
The point of thinking between tool calls isn't a smarter first plan — a model can plan up front without it. The point is that the model can notice a tool returned something wrong and re-plan on the spot, instead of barreling ahead.
Most 'agent budgets' are alerts wearing a brake's uniform: they tell you after the money is gone. Real enforcement is a prediction problem, because the cost of the next step is a bound you can only ever estimate — never a number you can look up.
The official MCP registry deliberately refuses to host code — so the hard part, trust, lands wherever the artifact lives. Docker's answer is to make that place an OCI image.
A Google PM's 'Always On Memory Agent' stores everything in SQLite and consolidates it with an LLM every 30 minutes. The 30-minute number tells you exactly what it's for — and what it isn't.
Sonnet 5 lands at 40% below Opus and beats it on terminal work — but a new tokenizer quietly inflates every token count by ~30%, so the rate card is not the price. Do the cost math in your own units.
Claude's new consolidation loop replays an agent's day and writes down what it learned. The same mechanism that lifted one customer's task completion ~6x is the one that makes a poisoned lesson permanent.
Every provider now sells the same deal — hand over your requests, wait up to 24 hours, pay half. The savings are real, but the reason to reach for batch is the thing nobody puts on the pricing page.
AWS WAF Bot Control can now return an HTTP 402 with a machine-readable price and settle USDC before the request ever reaches your origin. The real shift isn't crypto — it's that a web page finally has an enforceable price for a machine.
A Skill is a folder with a SKILL.md and an Apache-2.0 license — no server, no transport, no auth. That's why another runtime can adopt it in an afternoon, and why a Skill can't revoke, throttle, or contain anything.
Every multi-agent framework now has a handoff primitive, and they all look the same in the demo. The difference that bites you in production is what rides along when one agent passes the baton to the next.