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.
Forcing JSON can cost a reasoning model 10–15% — but the tax is paid during thinking, not from structure itself. The fix is where you put the reasoning, not whether you constrain.
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.
tool_choice looks like a switch for making a model use tools. It's really the decision of whether a turn is allowed to end the conversation — and leaving 'required' on traps the agent loop with no way out.
TeleMem ships as a one-line replacement for Mem0 — import telemem as mem0 — and claims a 16-point accuracy edge. Read where that number comes from and you learn exactly which agent it's for.
The DELETE call is the easy five percent. A user's data has already fanned out into the index, the chunk store, the cache, your trace logs, and maybe a fine-tune — and in most vector engines the delete is a tombstone the graph keeps walking until compaction.
They all scale now, and they all do hybrid search. The axis that still forks the decision is the one nobody puts on a benchmark chart: how each keeps a metadata filter from wrecking recall.
Three critical 2026 CVEs — in ModelScope's MS-Agent, Microsoft's Semantic Kernel, and Cursor — share one root cause. The agent filtered the command it was about to run. It never controlled the ground that command would run on.
A new .well-known discovery file lets clients read an MCP server's identity, transport, and auth requirements without a handshake — and it pointedly refuses to list the tools.
A 1988 access-control bug is the shape of 2026's worst MCP breaches. Understanding the confused deputy tells you why 'just add OAuth' doesn't fix your agent — and what the spec actually changed.
Function-calling leaderboards test a model against a handful of curated tools. A real MCP host hands it thousands — and that is a different benchmark, with a different failure mode.
The invoice arrives and no one can say which customer spent the money. Cost attribution isn't a report you run later — it's a schema decision you make at request time, and for agents the gateway total lies about where the spend went.
Firecracker gives each agent a whole Linux to boot — 125 ms of it. Hyperlight keeps the hardware wall and throws away the OS behind it, and that deletion is what makes per-tool-call isolation affordable.
A new automated auditor didn't just flag risky code in Model Context Protocol servers — it wrote the prompts to prove the holes were real. 67 already carry CVE IDs, and almost none are AI-specific.
M, ef_construction, and ef_search decide whether your vector search is fast, accurate, or neither. Only one of them can be changed after you build the index — and it's the one most teams never touch.
Map-reduce's 'reduce' step quietly re-creates the exact overflow you were escaping. Refine can't parallelize. And in 2026 the fastest-improving option is often to stop summarizing and put the whole document in a million-token window — if you can pay the middle.
A cut-off completion isn't an error your code catches — it's a 200 OK whose only tell is a stop-reason field most callers never read. And on reasoning models, the fix everyone reaches for can hand you an empty response.
Public leaderboards answer 'which model is smartest,' not 'will it fix my bugs' — the only test that predicts your outcome is a private eval built from your own repo.
A web server drains its in-flight requests in 30 seconds and restarts. An agent's in-flight request is a multi-hour, side-effecting loop — so graceful shutdown stops being a deploy setting and becomes an architecture decision you had to make weeks earlier.
Every serious agent-memory system is really a forgetting system. The hard part was never storing what the agent learns — it's pruning the contradictions and stale facts that quietly poison retrieval.
GPT-5.5 and Claude Opus 4.8 are tied on SWE-bench Verified at ~88.6%. That means the leaderboard number stopped being the answer — and your agent's scaffolding started being it.
Round-robin is the wrong way to route an LLM request. Kubernetes now has a GA'd standard that lets the gateway pick a model server by live KV-cache pressure and queue depth instead — and it changes what a load balancer is.