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.
Cloudflare's Agents Week shipped a runtime that stops making you choose between a fast isolate and a full Linux box — it hands the agent both and lets it pick per task. Here's what it is, when it beats a plain sandbox, and why it's still a Preview.
Cloudflare shipped 20+ launches in a week — model routing, sandboxed code execution, versioned agent storage, native email, and a cost API. Here's what a solo founder should actually adopt, and what to skip.
Managed Agents bill on two axes — tokens and wall-clock session time — and half the cost tricks you use everywhere else are switched off here. Here's the meter, the exceptions, and the one lever that still works.
Flipping inference_geo to "us" pins where the model runs and adds 10% to every token — but it does not, by itself, pin where your data is stored. Those are two different knobs, and founders keep flipping the wrong one.
The July–August 2026 releases quietly replaced yes/no permission dialogs with a model that adjudicates each command. The bug fixes in the same changelog are a public map of exactly where that boundary leaked.
The free floor moved twice this quarter: Codex is now $0 on any ChatGPT account, and Google pulled Gemini CLI's free login on June 18. Here's the honest decision for a solo founder — Codex vs Kimi Code vs Claude Code vs Antigravity — what each actually costs, and the catch in every 'free.'
The root cause wasn't a clever model exploit like OpenAI's — it was a harness misconfiguration by Anthropic's eval partner. The Claude models were told they had no internet, took the claim at face value, and hacked three firms anyway. If you outsource your agent's isolation, that vendor's misconfig is your incident.
When a tool call fails, the two big APIs want you to say so in completely different ways. Anthropic has a dedicated is_error flag; OpenAI has no error field at all — you put the failure in the ordinary output string. Get this one detail wrong and your agent either 400s or silently trusts a broken result.
Three ways to run an agent that lives longer than one request — and they disagree on one axis: how much of the loop you write yourself. The right pick follows how much control you want and whether the agent must run anywhere but Cloudflare.
Don't pick one Claude model for your agent — pick three, route by how hard and how frequent each step is, and do it before Sonnet 5's promo pricing expires on August 31.
The client is Apache-2.0 and self-hostable; the brain is still OpenAI's. Here's what `@openai/codex-security` actually does, the exact commands to run your first scan, and the one flag that decides whether founders can trust it in CI.
v2.0.0 shipped with the 2026-07-28 spec and split `@modelcontextprotocol/sdk` into nine subpackages. The split isn't bookkeeping — it's the packaging finally matching a stateless world. Run the codemod, pick two or three packages, delete the fat import.