Statelessness and the auth rewrite got the headlines. The quieter change is bigger: Extensions became first-class, MCP Apps let a server ship real UI, and Tasks moved out of the core — MCP stopped being a fixed protocol and became an extensible platform with governance.
The real split isn't feature lists or dashboards — it's whether the tool was designed around a single LLM call or around a whole agent run, and how you get alerted when the agent misbehaves.
A Kuaishou model most founders have never heard of now beats GLM-5.2 and GPT-5.5 on repository-level coding — at roughly a quarter of GLM's price. Here's whether it belongs in your routing table.
The 2026-07-28 spec made the core stateless — so how does a four-minute tool call survive when any request can hit any server instance? The Tasks extension. Here's the exact message flow, capability negotiation, and the client poll loop, protocol-level.
The whole terminal coding agent is now Apache 2.0 on GitHub. The reason it's newsworthy isn't the license — it's what security researchers found the closed version doing, and the one lesson every founder running a coding agent should take from it.
The tool-versus-companion split stopped being theoretical. Enterprise and productivity agents were left untouched; only the personas went dark — and the two giants chose opposite exits.
Oak came out of stealth on July 15 with $60M to give AI agents real identities — and the same week, MCP's spec made scoped agent auth mandatory. When the money and the standard point the same way, it's time to look at what your agents are actually allowed to do.
Four verified moves that change what a team of one ships this week — the stateless MCP release candidate, China's AI-companion law landing live, load-on-demand tool schemas in Agent Framework 1.11, and pluggable backends in CrewAI.
Strict mode kills the invalid-JSON problem you used to spend afternoons on. But three failures walk right through it — truncation, refusal, and a safety stop — and each one wants a different move, not another retry.
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.
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.