Kitesurf throws out Chromium and runs the whole browser in V8 isolates on Workers. It's 3–7× cheaper on CPU and memory and ~1.7× slower per page. For an agent firing thousands of short page loads, that trade is the point.
Every tool you register rides in the model's context on every turn, so verbose schemas quietly inflate your input bill. Trim each description to its load-bearing job, measure the drop, and A/B for accuracy — the same move that cut a Deep Agents turn's input tokens ~65%.
The complaint is never that skills give bad instructions — it's that they never fire. The one field that decides whether a skill loads is the description, and most are written too vague and too polite. Here's how to write one Claude reliably picks up.
Claude Code's August build moves any main-conversation MCP tool call that runs past two minutes into a background task, so a slow database query or deploy call stops locking up your shell. Here's exactly what changed, the one environment variable that controls it, and when to turn it off.
Qwen3.8-Max shipped on August 3 speaking both the Anthropic and OpenAI wire formats, so you can run your existing agent CLI on it by changing three environment variables. Here's the exact setup — plus the one Codex gotcha that will waste your afternoon.
llm 0.32 shipped a primitive that most agent frameworks make you build by hand: a tool can raise llm.PauseChain to stop the loop before it does something irreversible, hand control back to you, and resume later without re-running the calls that already finished. Here's the exact pattern — pause, persist, approve, resume — in about 40 lines.
Whole-value masking hides a bare token fine — but it corrupts a JWT your code decodes or an AWS key the SDK signs with. Claude Code v2.1.224 adds three structured fields (extract, decode: jwt, awsPairs) that keep the tool working while the agent still never holds the plaintext. Here's the exact config for each.
v2.1.224 (August 7) deleted the hard per-session ceiling that made long orchestrations fail at agent 201. It didn't make fan-out unbounded — it moved the real limits to concurrency, nesting depth, and a budget cap that finally halts running background agents. Here's the new mental model and the three env vars that set it.
OpenAI's Atlas browser stops working August 9 with no automatic data migration. If you wired an agent to it, here's the export checklist and the honest decision between ChatGPT's desktop app, Comet, Claude in Chrome, and the open-source escape hatch.
Sticker prices lie about coding-agent cost, because a single autonomous task burns one to three million tokens — and most of them are input. Here's the real per-task math across the models a founder would actually point an agent at, with verified prices, the two levers that move the bill 5–10x, and which model wins at each budget.
The whole decision comes down to duty cycle — how many hours a day your GPU is actually busy — and how much cold-start latency you can stomach. Here's the break-even line.
Meta's new 'contributor' price for Muse Spark 1.2 is roughly an order of magnitude cheaper than standard — because you pay the difference in training data. Here's the actual math, and a five-question test for whether that trade is fine or a mistake on your codebase.
Two model names that live in older Kimi and Moonshot integrations stop resolving at the end of August. The fix is one string per call — but the like-for-like replacement isn't K3, it's the model you probably overlooked.
On August 5, Meta dropped its first terminal coding agent — Muse Code, powered by the new Muse Spark 1.2 — straight into the space Claude Code and Codex CLI already own. Here's the what, the install line, the benchmarks, and the pricing catch that's getting the most attention.
K-EXAONE 2.0 is Korea's largest model — 750B parameters, 262K context, 10 languages — and the lab that used to ship the most restrictive license in the business just made it Apache 2.0. That's the first frontier-class open weight you can legally fork, fine-tune, and sell without asking anyone. Here's the self-host math and when to actually use it.
On August 5, 2026, Anthropic hard-retired Claude Opus 4.1 — requests to it now error. DeepSeek did the same to deepseek-chat and deepseek-reasoner on July 24. If a model ID is hard-coded in your app, a provider's calendar is your outage calendar. Here's the runbook that keeps a retirement from becoming a page.
Your agent emitted eight tool calls in one turn. Running all eight at once is how you turn a fast turn into a 429 storm. The fix is a bounded semaphore, backoff that honors Retry-After, and returning every result in one message — about 30 lines.
You rewrote the tool descriptions and cut the tool list. Did it work? A tool-selection eval turns that guess into a number you can watch — here's the 30-line harness that measures which tool your agent reaches for, and a confusion matrix that tells you why it's wrong.
DeepSeek open-weighted a million-token, MIT-licensed model on July 31. Before you 'just self-host it,' here's the number nobody puts on the launch slide: the memory floor. The context window is the cheap part.
Between August 4 and 6, every major agentic coding CLI shipped a security release, and the Claude Code one closed a real permission-bypass: a command could hide part of itself from the approval dialog. If you run any of these against a live repo, this is a bump-your-version week.
Launched August 5, inference hooks route every enterprise prompt through your own HTTPS server for an allow-or-deny verdict before the model ever sees it. Here's the wire protocol, a working server, and the fail-open gotcha that quietly lets prompts through.
Qwen3.8-Max's headline demo — 16 days, 265 commits, 127 PRs, every commit auditable on GitHub — is real and worth studying. But the thing that survived 16 days wasn't the model; it was a state machine, a watchdog, and a CI gate wrapped around a model that remembers nothing between steps. That harness is the part you can build on a far cheaper model.
A coding agent that asks 'run this command? [y/N]' feels safe. This month, the most-audited agent CLI shipped a fix for a bug where the command in that very prompt could be spoofed. Here's the defense-in-depth model that holds when the prompt doesn't — sandbox, allowlist, least privilege, in that order.
A $0.14 model doesn't fail by throwing an error. It fails by getting slightly worse at every step until, forty turns in, it returns a confident wrong answer that passes your shallow check. Here are the four ways it happens and the four cheap guards that catch each one.
NVIDIA's August container ships B300, GB300, DGX Spark, and Jetson Thor support behind a single pinned tag. The news isn't a faster kernel — it's that your serving image now spans a $3,499 desk box and a $300k rack without a rebuild.
Kimi K3 tops the open coding boards, but self-hosting a 2.8-trillion-parameter model is a data-center project. Here's the fast path: rent it through an OpenAI-compatible endpoint and wire it into Claude Code, Cline, or opencode today — with the caching gotcha that decides your bill.
Claude Code's July–August 2026 releases turned it from a single-agent chat into a bounded fan-out engine. Four caps and one isolation flag are the guardrails you set before you let it self-parallelize on a real repo.
A model card is a model's spec sheet, and most builders skim the benchmark table and close it. The parts that actually determine whether you can put the thing in production are the four sections nobody reads: intended use, out-of-scope use, training data, and the license. Here's how to read a card like it's a contract, because for compliance it nearly is.
You built an MCP server. Now make it discoverable in the one catalog Claude, VS Code, and every subregistry pull from. Three commands, one server.json, and a namespace you have to prove you own — the whole flow, end to end.
You added a reranker and quality barely moved — or your latency doubled. Almost always it's two miscalibrated numbers: how many candidates you fetch before reranking, and how many (or which) you keep after. Here's how to set both from your own data instead of copying a blog's defaults.