Reflection, Kimi K3, GLM — the open-weight frontier is getting loud, and it's tempting to make one of these models load-bearing in your product. Before you do, run the bet through four gates: is it shipped, is it callable, what's the license, and what's your fallback. Here's the framework, with the three staging patterns that let you get the upside without betting the company.
Skip the framework. An agent is an LLM calling tools in a loop — here's the ~40 lines that run it, the three context moves that keep it from rotting, and how to hang a real MCP tool off it.
The 2026-07-28 MCP spec deleted the handshake and put standard OAuth 2.1 in charge of who gets to call your server. WorkOS AuthKit flips into an MCP-compliant authorization server with one config value — here's what it does, who it's for, and where the free line sits.
Microsoft Execution Containers put the sandbox where the operating system already enforces boundaries — a policy-driven jail for model output and tool calls that runs on Windows, Linux, and macOS. It's MIT-licensed, on npm, and GitHub Copilot CLI already ships on it.
Huawei Cloud put its CodeArts coding agent into open beta and took the launch abroad at its Thailand summit. It runs open-weight models you already know, indexes your whole repo to cut ~30% of tokens, and starts free — here's what it is, who it's for, and where the free line sits.
Your agent scores ~77% on SWE-bench Verified and then stalls on a real feature. SWE-Marathon measures the gap: 20 tasks that run to 27 million tokens each, where even the best model clears only 42%.
Blender, Unreal, Adobe, and Houdini all shipped MCP servers at SIGGRAPH this week. The integration surface for creative tooling just consolidated onto one protocol — and the interesting design choice is that the artist still decides.
The 2026-07-28 spec makes statelessness the default, and the whole ecosystem is telling you to wait for the beta v2 SDKs. You don't have to. The stable SDK already runs stateless — one flag flips it. The real work is moving your state out of the transport, and that you can do right now.
One reasons and acts in a single pass. The other retries the same task, writing itself a note on what went wrong. The difference isn't which is smarter — it's whether you have a success signal and can afford the second attempt.
Pydantic AI's V2 rewrite bets the whole framework on one primitive — the capability — and hides the loop. LangGraph makes the loop the product: nodes, edges, and a checkpointer you own. Here's which bet fits which team.
Microsoft's open-source Execution Containers add a third option to the agent-sandbox decision: enforce a policy on a process instead of renting a whole virtual machine. Here's the one axis that tells you which you actually need.
The 2026-07-28 stateless spec is final and a stable v2 SDK is targeted for the same day — but the official README still says 'v1.x for production, don't use v2 yet.' Here's the version to start a new server on this week, and the signal that tells you to move.
The final spec froze every feature into an Active, Deprecated, or Removed state with a 12-month removal guarantee. Here's the one-screen map of what to adopt today and what to design around.
Three tools keep winning the 'how do I see what my agent did' question — and they're not really competing. Each answers a different question. Pick by the one you actually have.
You've been watching token counts. The number that actually moves your bill and your latency is the share of your prompt that hits cache — and most agent designs quietly wreck it.
The open weights that landed July 27 aren't a full-precision checkpoint you shrink to fit — they're the model as trained. MXFP4 quantization-aware training changes two self-hosting reflexes, and getting them wrong costs you quality or memory.
The download is one click and the terms are not MIT. The Kimi K3 License lets you sell what you build — until a Model-as-a-Service crosses $20M, or your app crosses 100M users. Here's the clause that decides whether 'open' means open for you.
The scariest agent bug isn't the call that fails. It's the call that succeeds — but the response gets lost, so your retry logic runs it again. One key, generated once and reused, is the fix.
ChatGPT and Perplexity increasingly send your first visitors — but only to pages they can parse. An llms.txt is a 20-line map that tells an AI engine what your site is and which pages matter. Here's the exact format, a copy-paste template, and the honest caveat about what it does and doesn't do.
A copy-paste walkthrough from an uninstrumented agent to a live multi-agent timeline in Honeycomb — using standard OpenTelemetry GenAI spans, so the same code also works with Langfuse or Phoenix later.
Every re-index, every retry, every duplicate document quietly re-embeds text you already paid to embed. An embedding cache is the boring, near-zero-risk optimization that a semantic cache gets confused with — and it's the one you should ship first.
Most multi-agent routing is a lookup you already know at author time, billed back to you as a model call. Here's how to route with plain conditions, and spend a token only on the one branch that's genuinely ambiguous.
One comes from production APM and correlates your agent with the whole system; the other is LLM-native and lives in prompts, cost, and eval scores. Here's which to standardize on — and why the choice is really about your daily workflow.
Both are the newest budget flagships from the two biggest US labs, both land within a point of each other on intelligence, and both are fast. So the decision isn't capability — it's price and which cloud you already live in.
Flash-Lite lands at $0.30 / $2.50 per million tokens — three times under GPT-5.6 Luna and Claude Haiku 4.5 on input. For the high-fan-out calls that don't need reasoning, it's the new cost floor. Here's the one job it's for, and the two where it will bite you.
Your agent doesn't fail because the model got dumb. It fails because you let its context window rot. Here is the four-move playbook — with the exact Claude API calls under each move.
You don't need Temporal to stop losing hours of work to a crash. Here's the minimum viable durability: serialize the loop's state to S3 after every step, resume from the last good one — and the one caveat that decides whether it's safe.
The moment a task outlives one context window, builders reach for a bigger prompt — and it fixes neither failure. A long-running loop dies two unrelated deaths, and each has its own cure.
The '3 kinds of memory' talk ends the moment you have to pick a backend for tier three. Managed service, memory library, or your own vector DB — the fork is really about who writes the hard 80% you don't see.
The passkey proved who logged in. It never signed off on what happened next. YubiKey 5.8 extends the same hardware to authorize a single action — so an agent can draft the payment, but a human presses the key before it clears.