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.
The AI-hardware story has been about matmul for a decade. Tenstorrent's new RISC-V core is a bet that the agentic bottleneck is quietly moving back onto the CPU's branch-heavy control plane.
The industry is treating 'agent identity' as a new frontier. It's actually two old, solved problems bolted together — and the interesting failure lives exactly at the seam between them.
A frontier mixture-of-experts model has 671B weights but touches only ~37B per token. That gap is why you can serve DeepSeek-scale models on a single consumer GPU — if you split by tensor role, not by layer.
Money and talent are pouring into 'RL environments' — the training gyms where agents learn by doing. The catch is that an environment is only as valuable as a reward you can't hack, and for the tasks that matter most, that reward is provably hard to build.
A system prompt is a broadcast: every rule you add competes with every other rule for the model's attention, on every turn. Parlant's bet is that reliability is a context-assembly problem, not a prompt-writing one.
The three multi-agent shapes aren't ranked best-to-worst — they're a single axis. Pick by one question: how much context can you afford to lose between agents?
The managed cross-region inference you turned on already solved availability. It did it by dissolving the region boundary you may be legally required to keep — and by throwing away your prompt cache at the exact moment you're already degraded.
MemPalace tops the long-term memory benchmark by refusing to summarize. That's not a trick — it's an argument that the field spent two years solving the wrong half of the problem.
Five real, self-hostable gateways that put one endpoint in front of many MCP servers — and why the stateless spec is about to change what a gateway is even for.
Liquid AI's smallest model yet fits in under 400MB and runs on a Raspberry Pi. The interesting part isn't how small it is — it's what a model this size is actually for.
Every checkpoint a long-running LangGraph agent writes re-serializes its entire state. DeltaChannel, per-node timeouts, and the v2 stream in 1.1–1.2 are the runtime quietly admitting the naive durability model doesn't scale.
Schema-constrained output gives you a valid object. It can't tell you whether a value was read from the document or invented to satisfy the schema. Google's LangExtract returns the exact character span each field came from — which turns extraction from a trust exercise into a verification one.
On GAIA, the best base model sits near 45% while orchestrated agent systems clear 92% — matching humans. That 47-point gap isn't noise. It's the benchmark quietly telling you the model was never the thing under test.