The same SKILL.md that works in Claude Code can quietly break on the API — no network, no package install, and it isn't even uploaded there. Here's what changes per surface before you ship.
Google, Microsoft, and AWS now speak the Agent2Agent protocol natively. Here's the honest line on when that matters for a team of one — and when it's plumbing you can safely ignore.
An event-driven durable execution engine for background jobs and long-running agent steps — for solo founders who don't want to run their own queue and worker fleet.
Keep LangGraph for orchestration, get a React streaming chat for free. The rewritten adapter turns a graph stream into an AI SDK UIMessage stream in a few lines.
Kimi K3 landed July 16 with dated open weights; Qwen3.8-Max previewed July 19 claiming 'second only to Fable 5.' One is a shippable artifact, the other is a claim. Here's the founder's read on both — access, price, openness, and what's actually verified.
The July 20 release folds durable execution into the same 'capabilities' system V2 introduced. Temporal, DBOS, and Prefect now attach in one line — and the wrapper-agent classes you may have shipped are on the way out.
The July 8 NemoClaw blueprint makes self-hosting open agents a real option — but for a team of one, the deciding factor is token volume, not vendor benchmarks.
The Python 1.12 and .NET 1.14 releases landed July 21 — and the headline isn't a new agent trick. It's that your agent becomes an MCP server, and its memory stops dying with the session.
The stateless spec is frozen and backward-compatible. The thing that bites you this week is the SDK upgrade — a TLS trust-store swap, a package split, and an opt-in cancellation flag.
The 2026-07-28 spec makes MCP stateless — but a stateless server still needs to ask the user 'are you sure?' mid-call. Here's how MRTR replaces the held-open SSE stream, and how the new Mcp-Method header lets a plain gateway route your traffic.
The stateless spec stopped being a PDF: real Python, TypeScript, Go, and C# betas landed June 29. Here's what shipped, the exact install lines, and the one week you have to validate a real server before the surface freezes.
The 2026-07-28 spec says you can drop sticky sessions — but a leftover in-memory map will still pin you. Here's the test that catches it before July 28.
LangGraph 1.2 shipped two new streaming APIs on top of the old stream_mode dicts. Here is what version="v2" and version="v3" actually change, and which one to reach for.
Moonshot's 2.8T giant and Thinking Machines' 975B base launched 24 hours apart. The decision isn't 'which open model' — it's rent a bigger generalist or own a specialized base.
Now that /fork spins off real background sessions, 'I'll just trust it' stops scaling. Here's how to make parallel Claude Code agents observable: the agents view, --forward-subagent-text, stream-json, and the 'Needs input' state that tells you which one is stuck.
A skill is a prompt in a folder, so a bad edit ships silently — no compile error, no failed test, just an agent that quietly behaves differently. Here's how to put skills under version control and get back to a known-good state in under a minute.
The stateless rewrite got the headlines; the auth hardening is what will break your integration on July 28. Three client-side fixes — validate iss, declare application_type, discover the server the right way — with the exact code.
You picked Kimi K3 for bulk and Claude Sonnet 5 for the hard tasks — now wire them behind one interface so switching is a config change, not a rewrite. Here's a ~40-line router with task-based selection and automatic failover, using the OpenAI SDK pointed at an OpenAI-compatible gateway.
Claude Code 2.1.212 shipped hard, session-scoped ceilings on subagent spawns and web searches — both default to 200. Here's what each one actually stops, why the spawn cap is a loop-breaker and not a spend cap, and how to tune the three knobs that really govern a runaway agent's bill.
Agentjacking hijacks your coding agent through data it already trusts — a poisoned Sentry error, a booby-trapped Jira ticket. No server is breached and no human approves anything. Here is the concrete config that breaks the attack, and why deny rules alone won't.
v0.19.0 (July 20) cut first-turn time-to-first-token ~80%, streams reasoning live, and adds an independent-LLM approval reviewer and a crash-proof delivery ledger. The coding-agent race is being run on the harness, not the model.
Three tools all promise 'describe it, ship it.' The real split isn't which writes better code — it's what happens the morning after launch, when the app is running your business and you still can't read the code.
Eight releases landed in two weeks. The two that change how you actually work: you can now chain up to five skills in one invocation, and the agent stops asking-then-guessing — decision dialogs no longer auto-continue.
In one week Claude Code stopped treating delegated work as throwaway. /fork now spins up a real background session, /subtask takes over in-session delegation, and a new EndConversation tool lets an agent close itself. Here's the new mental model for a team of one running many agents.
A single July 18 release made the Bash and Edit permission analyzer fail closed in six specific cases — including a broad glob rule that auto-approved writes far outside your project. What each fix means if you run the agent unattended.
They get pitched as rivals. They're not — they answer three different questions. A founder's decision guide to when you write a SKILL.md, when you stand up an MCP server, and when you spawn a subagent.
Google Cloud Run Sandboxes charge no premium — they run inside compute you already pay for. That single fact reframes the whole build-vs-buy question for running untrusted, LLM-generated code.
A day after we argued Go teams rarely need an agent framework, Microsoft put a first-party one into public preview. Here's what it covers, what it's still missing, and when a founder should reach for it instead of a forty-line loop.
The 2026-07-28 revision deletes the handshake and the session on the server side. For plain tool servers it's an SDK bump; the real work is replacing per-session state with explicit handles — here's the before/after, server-side.
Three ways to feed an agent what it needs to know — stuff the window, retrieve at read time, or compile context ahead of time. They fail differently and cost differently. Here's the one test that picks the right one for your workload.