Zscaler ThreatLabz caught two live campaigns that hide payment instructions where a human never looks — off-screen CSS and, worse, the JSON-LD metadata your agent treats as trusted fact. Here's the attack, and the four defenses that actually hold.
China's persona law went live July 15; GDPR already demanded erasure. Together they make 'prove your agent forgot' a requirement — and memory tooling is now competing on auditability, not recall.
The largest MCP revision since launch goes final on July 28. Here's the hands-on checklist for server authors — what to change, what to delete, and the two edits that are genuinely breaking.
The July releases graduated the Skills API out of experimental and added message-injection middleware — you can now correct a live run without killing it. Here's what actually shipped and what it changes.
Enable one flag and Letta spins up a background agent that reworks your primary agent's memory off the critical path — better recall, zero added user-facing latency.
Flows give you an event-driven graph without writing threading or a state machine. Here's the whole control-flow vocabulary — @start, @listen, @router, and_, or_ — with copy-paste code for fan-out, join, and conditional branching.
The 2026-07-28 spec removed tasks/list — in a stateless protocol the server can't enumerate 'your' tasks. So you carry the claim ticket. Lose the id and the work is orphaned. Here's the client-side store that stops that happening.
A deep agent is a plain tool-calling loop plus four batteries: a planner, a filesystem, subagents, and context management. Here's create_deep_agent end to end — a working research agent in ~15 lines, then how to add a custom subagent.
CrewAI 1.14 made memory a backend you own instead of a black box it ships. Here's the copy-paste path from the bundled default store to your own Qdrant — and the one config field whose name will confuse you.
A multi-agent run that dies at step 4 shouldn't restart at step 1 — and pay for steps 1–3 again. Here's the copy-paste code to checkpoint Flow state, kill the process, and resume exactly where it stopped.
The 1.15 line moved flow authoring from decorated Python classes toward data you can load, version, and review — plus one small feature that finally answers 'what did this agent run cost me?' Here's what actually shipped and whether it's worth the upgrade.
You've ruled out running a server. Now it's Chroma or LanceDB — and the choice isn't recall quality. It's whether you're optimizing for the fastest path to shipping or for the shape of the data itself.
On the same July that Doubao and Qwen switch their companion agents off to comply with Beijing, the U.S. approach is visible in a different shape entirely — laws that keep the product legal and instead fence the harm, especially to minors. Same product, opposite bet.
Microsoft and Anthropic ship lazy tool loading as a config flag. Here's the same discover/load/unload loop in ~40 lines over a plain MCP client — no framework, and you keep the allow-list as your security boundary.
ARD's technical story is a discovery layer. Its guest list is a distribution story — and for a solo founder, distribution is the part that decides whether an agent ever finds you.
Two of the biggest agent rounds of the summer didn't fund another horizontal framework. They funded governed, vertical agents in regulated finance and human-supervised enterprise software — a signal about where the value is actually accruing, and what's left for a solo founder to build.
The July 11 release deletes the original PagedAttention implementation and makes Model Runner V2 the default for every dense model. The innovation didn't die — it dissolved into the standard path.
vLLM deleted the CPU–GPU sync in the model runner; SGLang deleted it in the speculative-decoding scheduler. The frontier of serving throughput in mid-2026 isn't a faster kernel — it's the war on the stall.
Vercel's ephemeral compute primitive for untrusted, AI-generated code is generally available. Firecracker isolation, up to 32 vCPUs, and a pricing model that charges only while a CPU is actually working — here's what it is, who it's for, and how to start.
Pydantic AI v2.9 shipped a /usage command for cumulative token tracking and — the real upgrade — exposed the run's usage_limits to your tools. Here's how to set a hard budget, read what's left from inside a tool, and stop a runaway agent before the bill lands.
A code-forward walkthrough for getting every memory out as structured JSON you control — add, get_all, re-import — so no vendor's shutdown can delete your users' context.
OpenAI audited SWE-Bench Pro, found ~30% of its 731 tasks mismark correct code as wrong, and pulled its own recommendation. If you pick a coding model on a two-point benchmark gap, you're routing on noise.
In three releases across five days, the OpenAI Agents SDK made GPT-5.6 the default and quietly added 'hosted multi-agent beta support' — a path to run agent fan-out on OpenAI's infrastructure instead of your own. Here's what's actually in 0.18, and the decision it forces.
The 2026-07-28 spec deletes the handshake and the session. Here's the concrete diff — drop `initialize`, read capabilities from `_meta`, and replace held-connection elicitation with Multi Round-Trip Requests — with old-vs-new code for each step.
Mem0's token-efficient rewrite stops doing UPDATE and DELETE when it stores a memory, and pushes the hard part — reconciling contradictions — to read time. That's not a free win. It's a bet about where you can afford to spend.
The 2026-07-28 spec kills server-initiated sampling but keeps elicitation — and adds a URL mode built for exactly the flows you couldn't do before: OAuth, credential entry, and payment setup that must never touch the model context.
The release candidate everyone read for the deprecations buried the bigger change: MCP is no longer a session. It's a stateless request/response protocol you can put behind a plain load balancer — and that quietly rewrites how you deploy every server you own.