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.
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 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.
Three places to get an RL environment, and they don't compete on the axis you think. The dividing line is where step() runs — a cheap function call or a network trip to a live machine.
Loading the right MCP tools on demand is a solved problem. Removing the wrong ones over a long conversation is not — and a new benchmark finds that letting the agent do it itself only works if the model reasons.
Google open-sourced a text diffusion model that reads documents better than the autoregressive Gemma it's built on — and does multi-step math worse. That split tells you exactly where to wire it in.
CrewAI 1.14 lets you swap the default memory, knowledge, RAG, and flow backends for your own. It reads like a config change. It's actually the framework conceding that batteries-included storage was a production liability.
Anthropic's new research workbench isn't a smarter model — it's two orthogonal layers, an independent reviewer agent and a reproducibility package, that any agentic pipeline can steal.
Subagents can now spawn subagents five levels deep. The number that decides whether you should is not the depth — it's how much billed work happens at branches the root never reads.
Seven real, self-hostable RL frameworks for post-training tool-using agents — and why the one you pick should be decided by the environment, not the algorithm.
Letta's .af format serializes an agent's memory, tools, and history into one JSON file. The pitch is portability. What it delivers best is something quieter — a savefile — and that distinction decides whether it's useful to you.
The ground-up Beta that becomes mainline in AG2 1.0 replaces the chatty ConversableAgent with a MemoryStream — a per-channel append-only event log. It's the framework conceding that an agent has to survive its second concurrent user, not just the demo.
Per chip, Google's Ironwood and Nvidia's B200 are now within ten percent of each other on every number that used to decide this. The real fork is the interconnect — and vLLM just deleted the reason you couldn't cross it.
SGLang v0.5.14 reports 5x throughput serving DeepSeek-V4 on GB300. The lever isn't Blackwell Ultra — it's a per-batch linear program that reroutes tokens across expert replicas. Static replication plans for the average; no batch looks like the average.