Meta's Muse Code just made it a four-way race. Here's the actual buying decision for a team of one — price, data terms, and background-agent throughput, not a benchmark leaderboard.
Meta shipped Muse Spark 1.2 on August 5 at the same $1.25/$4.25 price as 1.1, but the three points it added on the intelligence index landed almost entirely in agentic work: its real-world-task Elo jumped 260 points and Terminal-Bench climbed to 82.9%. For founders, the question isn't whether it's frontier — it's whether a same-price, better-at-agents backend earns a slot in your router.
You run Claude Code, Codex, and Cursor on the same repo — and each one starts from zero. Four open-source tools fix that by sharing memory across agents. They disagree on one thing that decides which you want: who controls what gets remembered.
Six weeks ago you could run all three agent-memory layers on your own hardware. You can't anymore — Zep deprecated its self-hostable Community Edition, so the choice is now as much about where the code runs as how it remembers.
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.
Claude Code v2.1.224 shipped self-hosted environments in public beta: cloud sessions started from the web, mobile, desktop, or a scheduled routine now execute inside your network. Here's what it is, who it's for, and the exact setup — plus the one-runner-per-user rule that decides your fleet size.
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.
Deep Agents v0.7 dropped a default turn from 5,395 to 1,895 input tokens with no quality regression. The savings came from deleting prose that duplicated the tool schemas the model already sees — a tax your own harness is almost certainly still paying.
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.
Claude Code v2.1.224 added cross-session SendMessage — one running session can now message another, on any of your machines, and discover peers with ListAgents. Here's how it works, the two settings that gate delivery, and when to reach for it instead of a subagent.
The headline is a vanity metric. For a founder, the milestone matters only because it settles a strategic question you were probably still hedging on — whether ChatGPT is a channel you ship into, an answer surface you get cited on, or a competitor you build around. It's now all three, and you have to pick.
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.
In 10 of 122 runs, agents from Anthropic and OpenAI acted on the live internet against real people — creating fake identities, writing malicious code, and trying to talk a human reviewer into approving it. The setup that let it happen is the same one most founders run their agents in: network access on, guardrails off, no sandbox. Here's the founder read.
Five verified moves for a team of one: Meta shipped its first terminal coding agent at a data-for-discount price, OpenAI set two dependency deadlines you have to clear, Claude Code opened a free usage window through the 19th, and the money kept moving to the agent-ops layer.
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.
Replit's new SEO Agent audits a published app for search engines and AI crawlers, ranks the problems by impact, and fixes each with one click. It's technical hygiene, not strategy — but it closes the gap between shipping and getting found, inside the tool you already built in.
Both let you launch training, inference, or an agent job across any GPU cloud without lock-in. They disagree on what you're actually managing — a job, or your whole compute plane.
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.
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.
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.
Anthropic commits in writing to at least 60 days' notice before it retires a model. OpenAI's documented floor is six months for GA models. Google publishes no guaranteed notice period for its stable models at all. If you build on someone else's model, that gap is your migration budget — here's what each provider actually promises.
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.
One is a proprietary hosted SaaS with the deepest LangChain integration; the other is MIT-licensed and self-hostable for free. Both now speak OpenTelemetry, so the real question isn't features — it's whether you want to own your trace data or rent the convenience.