The headline savings from semantic caching are real — and they come from a workload your agent doesn't have. Two different things are both called 'caching,' and only one of them is safe to put around a tool call.
Replacing every name with "[PERSON]" tells the model John and Jane are the same person — and one-way masking means you can never put the real name back in its reply. Redaction is the easy half.
SGLang's team spun out as RadixArk on a $100M seed at a $400M valuation. Read the cap table, not the press release: hardware rivals rarely fund the same software unless it threatens something they all share.
Pydantic AI now speaks four durable-execution backends with near-identical code. That means the choice isn't about the framework — it's about which piece of infra you're willing to run.
The GenAI semantic conventions are still 'Development' and change almost every release. That sounds like a reason to wait. It isn't — you just have to instrument the part that's holding still.
Databricks open-sourced a common orchestration layer over Claude Code, Codex, Cursor, and your own agents — swap the harness in one line of YAML. The interesting bet isn't portability. It's who reviews the code.
The sizing calculator in NVIDIA's NeMo Agent Toolkit profiles a multi-agent workflow under concurrency and extrapolates a GPU count. The quiet lesson: an agent's cost is emergent, not calculable.
Microsoft and LangChain shipped agent-memory frameworks a day apart in June. They disagree on the one axis the benchmarks don't measure — whether you should be able to read what your agent remembers.
The four booleans on an MCP tool look like a permission model. They aren't — they're a risk vocabulary for trusted servers, and wiring them into auto-approval is the mistake.
The 2026-07-28 spec's quietest change is the one that decides whether you can build a business on MCP — a formal feature lifecycle with a year of runway. The catch is where the guarantee ends.
The 2026-07-28 spec lets an MCP server tell clients how long a result stays fresh and whether it's safe to share. One of those two fields is a performance knob. The other is a security boundary people will read as a performance knob.
The 2026-07-28 spec ships MCP Apps as an official extension. The sandboxed iframe everyone points to is not the security boundary — the consent path is, and that changes what you should actually worry about.
Meituan's 1.6-trillion-parameter LongCat-2.0 claims end-to-end training on 50,000+ domestic accelerators, no NVIDIA involved. That claim is the story — and the fact that it names no chip vendor is the part worth reading closely.
Rerun the same eval and an LLM judge flips 1 in 7 of its verdicts — while its own scores show no real difference between the answers. Reliability and validity are two different axes, and the number most teams report can't see either one.
LangGraph 1.2 shipped per-node timeouts with two knobs that look interchangeable and aren't. Pick the wrong one and you either kill healthy slow work or never catch the hang you added it for.
Every superstep, the default channel re-serializes your entire message list into the checkpoint. On a long-running agent, that write cost grows with the conversation — and DeltaChannel is the fix that finally makes it linear.
The same procedure, packaged two ways. A controlled study finds the layout of a skill changes what the agent actually does — not just how many tokens it burns.
A pull-request gate has to give a clean yes or no. Agent quality is graded and noisy. Wire those two facts together naively and you get a gate engineers learn to re-run until it's green.
Retrieve 100 tools and the right one is 'in the list' 99% of the time — the same odds a random shortlist gives you. Two 2026 papers show why recall is the wrong number, and why fewer tools win.
OpenAI cut p95 latency 25% across its Realtime voice models by improving prompt caching — and where that speedup lands tells you why your agent slows down as the call goes on.
Google's Agent Development Kit shipped a graph-based execution engine — and quietly retired the org-chart of agent types that used to be its whole pitch against LangGraph.
When an agent chains ten LLM calls, provisions cloud resources, and moves money, a pod restart shouldn't mean starting over. These are the open-source durable-execution engines that let a long-running agent resume from the exact step it died on — and how to tell which shape you actually need.
The counterintuitive fix for context bloat is to stop reading tool output. Offload the payload to a file, hand the model a pointer — and move the retrieval decision from write-time to read-time.
The leap from chat agents to always-on, event-triggered ones gets framed as a question of how autonomous the agent can be. The harder, quieter constraint runs the other way.
Your agent stores the same fact twice with different values. The intuitive fix — ask the model which is newer — is the one 2026's benchmarks say to avoid.
The SKILL.md format takes five minutes to learn. The part that actually decides whether your skill works is the one sentence you're most tempted to rush.
In mid-2026 the three biggest agent frameworks converged on the same primitive — tool calls gated behind a human approval — and Microsoft made it the default for anything a skill brings in. It's the security fix sandboxing couldn't provide.
Studies this year found prompt-injection patterns in roughly a quarter to a third of scanned agent skills. The scary part isn't the number — it's that the standard fix doesn't apply.
Setting temperature to 0 doesn't make an LLM deterministic. The real culprit isn't sampling or 'random' GPU math — it's that your request's output depends on who else is in the batch.
The scarce resource in an autonomous system isn't compute. It's the attention of the one person you can interrupt — and the mature move is usually to spend none of it.