Forget the model launches for a second. This week the SDKs under your agent shipped real releases — new default models, cheaper tool-schema loading, a day-0 Gemini tier, and a promo price with an expiry date. Here's the upgrade checklist, each line sourced to a release note.
A 29k-star, Apache-2.0 canvas for wiring agents to 1,000+ tools — build them visually, conversationally, or in code, then self-host the whole thing on Bun and Postgres. What it is, who it's for, and how to start.
What Grok Build is, who it's for, how to start, what it costs, and the honest catch — xAI's new coding agent runs Grok 4.5 by default, drives from a terminal UI, headless, or embedded over ACP, and undercuts the frontier tier at $2/$6 per million tokens.
Fresh off a $60M Series A, Arcade is the 'secure action layer' for production agents: it runs the OAuth flow, holds the tokens, and injects credentials server-side so your agent can send the Gmail or update the Salesforce record — and the LLM never touches a secret.
All three frontier APIs now take a JSON Schema and hand you back guaranteed-valid JSON. But the same schema does not drop into all three unchanged — and the place it breaks is the one line most people copy from OpenAI's docs.
A LangGraph agent that dies mid-run doesn't have to start over. Compile with a checkpointer, invoke with a stable thread_id, and the graph rehydrates from its last checkpoint. Here's the copy-paste path from MemorySaver to Postgres.
V2 landed in June as a harness-first rewrite around one new primitive. V1 isn't dead — it's in long-term maintenance and still shipping security fixes. Here's how to decide which line your agent belongs on.
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.
Four methods — add, search, get_all, delete — turn a stateless agent into one that remembers a user across sessions. Here's the working code, the self-host-vs-managed choice, and the one setting that decides your bill.
E2B's mid-July SDKs (Python 2.32, JS 2.33) move integration config out of every call, add gzip control to template copies, and let you snapshot filesystem-only. Small changes that bite once you run untrusted agent code at scale.
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.