Renting a bare H100 by the hour is the wrong model for bursty agent inference — you pay for idle. Serverless GPU scales to zero and bills by the second. Here's what the three big platforms charge, and the billing detail that decides your invoice.
Two months ago the rule was simple: Chat Completions for portability, the Responses API for OpenAI lock-in. This week a Chinese frontier model shipped Responses-native and an indie CLI added server-side tools. The wire format is converging — but the portability is shallower than it looks. Here's the line to build on.
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 picked serverless so you'd stop paying for an idle GPU. Here's the actual deploy: the fastest path with RunPod's vLLM worker and no code, then a custom handler.py for your own model — both scaling to zero when idle.
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.
The July 30 price cut dropped GPT-5.6 Luna to $0.20/$1.20 per million tokens — about 12x cheaper on output than Kimi K3 and 25x cheaper than GPT-5.6 Sol. Output tokens dominate a coding-agent bill, so the cheap tier just rewrote the routing table. Here's the recomputed math, and the one number you have to measure before you switch.
Two traps hide in the August leaderboard: the SWE-bench Verified winner (DeepSeek V4 Pro, 1.6T) needs a multi-node rig to serve, and it loses the harder SWE-bench Pro to GLM-5.2. Open weights aren't runnable weights — here's the field with Qwen's Apache-2.0 option in it.
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.
A brand-new launch in the hottest corner of dev tooling: run coding agents in cloud sandboxes without rebuilding your environment from scratch. Hoplite's pitch is local-to-cloud parity — your sessions, your MCP servers, your CLIs — plus triggers from Slack, Linear, iMessage, and Sentry. Here's what's confirmed, who it's for, and what to ask before you depend on it.
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.
You have one event — a new task, a finished run — and two or three workers that each need to react. That's fan-out, and for a solo builder the honest answer is almost never Kafka. Here's how the three tools you already have actually differ.
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.
Three small open-weight coders you can self-host on a single card. They aren't really competing on SWE-bench — they're competing on how much work a GPU can do per hour and how cheap that GPU is.
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.
Mintlify bought Helicone on March 3, and the open-source LLM observability tool now ships security patches and new-model support but no new features and no roadmap. Here's whether you have to move, and exactly where to go depending on what you used it for.
GPT-5.5 has a 1M-token window but a price step at 272K input tokens — and crossing it reprices the whole request, not just the overflow. Here's the trap that ambushes long-running agents, and four ways to stay under it.
Retries handle the transient failure. They don't handle the call that will fail every time — the poison task that retries forever, drains your budget, and blocks everything behind it. A dead-letter queue is the escape hatch.
If you're building the kind of product where an agent writes an app and then runs it, each of those apps needs storage — isolated, per-tenant, and not reachable by the generated code itself. Facets is Cloudflare's answer, and it's a supervisor pattern you can copy.