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.
You press stop. Your socket closes. The GPU keeps decoding, the bill keeps climbing, and a half-finished tool call is still out there. Cancellation isn't a button — it's cooperation.
The speedup was never the bottleneck — the well-matched draft model was. DeepSpec ships the whole draft-training pipeline, MIT-licensed, with Qwen3 and Gemma as the default targets.
The dead-letter queue is a solved pattern — for messages. An agent task isn't a message, and the two places that assumption breaks are exactly where your reliability and your token bill live.
The axis that actually separates the open-source memory engines isn't graph vs vector — it's how much structure each one commits when it stores a fact, and that quietly decides which questions your agent can answer later.
The first Five Eyes guide for agentic AI names five risk categories. Read them as a builder and something jumps out — only one requires an adversary. The other four are your own architecture failing quietly.
A new law takes effect July 15 governing what an AI may pretend to be. Both Chinese giants chose to switch the feature off rather than retrofit it — because persona is the product, not a setting.
An agent is a chain of steps that each depend on the last, so a 24-hour batch window can't sit on the critical path. You can't batch the loop — but the token-heavy work around it is exactly what batch was built for.
Foundry and Vertex now let a model generate the rubric it will grade your agent against. That closes a loop — and the loop has no fixed point outside itself.
A reported deal to rent Azure servers full of Microsoft's inference silicon isn't about capacity. It's a tell about which half of an AI lab's compute is actually up for grabs.
A public Sentry key is all an attacker needs to plant a command where your coding agent will read it — and run it. The attack doesn't touch the tool or the server. It rides in on the data you trust.
Prompt injection dies when the context window clears. Memory poisoning writes the payload into the store the agent trusts — so it fires in every future session, with the attacker long gone.
Both let an agent return interface instead of text. One ships executable HTML in a sandbox; the other ships JSON to your native components. The gap between them is the whole decision.
Whole-task routing picks a model before the work starts. Agents need something harder: to notice, mid-trajectory, that they're now out of their depth — and three 2026 benchmarks say they can't be trusted to notice it themselves.
Every LLM router you know picks a model. This one runs inside Envoy's data plane and turns reasoning off — and on MMLU-Pro that raised accuracy 10 points while halving tokens.
You can change a tool's schema in a fully backward-compatible way and still break your agent. The contract has two consumers that version differently — your code, which you can pin, and the model, which you can't.
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.