Full-text search tokenizes your text into words, so it structurally cannot match a fragment inside a token. LanceDB's new FM-Index indexes the raw bytes instead — the exact-match primitive code and log agents were missing.
Deployments assume fungible replicas; StatefulSets assume a numbered set. An AI agent session is neither — it's a singleton with a stable identity, one of a million uniques. The kubernetes-sigs Agent Sandbox project adds the primitive that was missing, plus a warm pool that hands one over in milliseconds.
The instinct is to rate-limit per user. An agent breaks that in one move: a single user's run fans out into hundreds of calls, and the ceiling that binds isn't yours — it's the API you're calling.
Durable execution saves the agent's work when the server dies. It does nothing for the user whose phone dropped Wi-Fi mid-answer — that's a different resume problem, on the other side of the wire, and the new stateless MCP spec quietly made it harder.
A working coding agent is a few hundred lines and four tools — a weekend. What separates a toy from Claude Code is everything that isn't the loop: the edit contract, what you keep out of context, and whether it runs the tests.
On xAI's own SWE-Bench Pro numbers, Grok 4.5 loses to Opus 4.8 by 4.5 points — and finishes the same task for roughly a seventeenth of the output cost. The interesting number isn't the price. It's the token count.
In Python, an agent framework sells you concurrency, cancellation, and retries. Go ships all three in the standard library — so the real question in Go isn't which framework, it's whether you need one.
DSPy's ReActV2 looks like a native-tool-calling upgrade. The real fix is deeper — the classic ReAct loop re-serialized its whole scratchpad into one prompt every turn, which silently defeated provider prompt caching. Moving to structured history cut cost up to 50%.
In early July, Deep Agents quietly split into three shippable packages: a model-agnostic harness, a terminal coding agent, and an ACP adapter. The library became a product line — and unbundled the coding agent from both the model and the editor.
The word 'cross-encoder' still means one query-doc pair, one relevance score. But the model underneath quietly flipped from a BERT encoder to a causal decoder — and it brought the LLM's failure modes with it.
CrewAI 1.15 shipped conversational flows, and it's easy to read that as "your crew can hold a conversation now." It can't. What shipped is a persisted, resumable flow behind a poll loop — and that distinction decides how you build.
Anthropic's memory tool gives Claude a /memories directory it can read and write across sessions. But the directory is a fiction, the store is your code, and so is every line of the security.
Subagents let Claude delegate a few tasks per turn. Dynamic workflows fan out hundreds. The line between them isn't how many agents you need — it's whether the plan is stable enough to freeze into a script.
For a decade the advice was "stop polling, use webhooks." The agent runtime quietly broke the webhook's core assumption — so the newest async surfaces ship polling first.
MCP's 2026-07-28 spec deletes the session handshake that ops teams quietly used to stitch an agent's tool calls together in their logs. The replacement is W3C Trace Context — and it doesn't do the same job.
The overflow that kills agents happens at the one boundary the MCP spec never paginated — the tool result. And the reflex fix, truncating to N characters, is the only option that's strictly worse than doing nothing.
A neocloud that owns none of the models it serves just booked $1.15B a year. The number that matters isn't the valuation — it's that open-model inference outgrew the labs whose weights it runs.
Mozilla shipped a one-call API that turns any URL into structured JSON, cited research, or a finished browser task. The pitch isn't the features — it's that it obeys robots.txt on purpose.
A cache that skips a duplicate chatbot answer is a savings. A cache that skips a duplicate agent step is a wrong action. New 2026 benchmarks show the standard tools score under 40% — and the fix is the opposite of what you'd guess.
Qdrant 1.18 shipped a Google Research quantizer that rotates your vectors before it compresses them. The rotation is the whole trick — and the reason it works on any embedding model.
V2's headline is the Harness. The change that will page you is smaller: the bare `openai:` prefix now resolves to a different OpenAI API, and no deprecation warning fires.
A 33B mixture-of-experts model that activates only 3B parameters per token now clears 63% on SWE-bench Multilingual — and ships under a Linux Foundation license. The active-parameter count and the license matter more than the score.
v0.17.8 added an `invalid_final_output` handler — a third failure layer that catches what the model itself produces at final output, not what your tools or guardrails do.
GLM-5.2, Kimi, and MiniMax all ship an Anthropic-compatible endpoint, so pointing Claude Code at them is a one-line base-URL swap. The model runs — but 'compatible' is a promise about the wire format, not about the harness features your bill and your speed depend on.
The vector-database benchmark wars are all fought on the read path — recall and QPS. Milvus 2.6 spent its headline engineering on the part nobody charts: the durability log, which it moved straight onto object storage.
LlamaIndex's new legal-kb reference app hands the agent findFiles, readFile, and grep — not a search() call. The quiet argument is that retrieval was never the model's job to outsource.
The Send API gives you the fan-out. Deferred nodes are how you get a correct fan-in — but only if you understand that defer=True is a queue-drain barrier, not a dependency resolver.
Choosing a checkpointer backend isn't a speed decision. It's a decision about what lifecycle you want your agent's state to have — a permanent ledger you can replay, or a searchable cache built to expire.
The parameter everyone reaches for limits the size of one reply. Agent bills don't blow up on reply size — they blow up on the number of replies. Cap the loop, not the token.