Five verified moves for a team of one: a self-propagating npm worm that hunts AI-coding-agent credentials, DeepSeek warning it will raise the cheap-token floor, Claude Code turning auto mode on by default Aug 14, Rippling shipping a spend console after its own AI bill grew 80% a month, and the EU quietly slipping its high-risk deadline to 2027.
Alibaba's 2.4-trillion-parameter model is slated to open its weights this month. The headline is smaller than Kimi K3, but the number that sets your token bill — 95B active — is nearly double. Here's the serving math, and why it pushes the rent-vs-own line further toward 'just use the API.'
Within 48 hours in early August, OpenAI's Codex CLI and Anthropic's Claude Code both shipped installable plugins — and picked opposite defaults. Codex bets on a searchable catalog; Claude Code bets on a raw ZIP over HTTPS with a checksum. If you're publishing an extension, the choice decides who finds it and how they trust it.
The Agent Skills format is now an open standard that 30-plus tools read. So the same SKILL.md folder can run in five different coding agents — but only the frontmatter and body travel cleanly. Here's the install path for each, and the three things that quietly break portability.
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.
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.
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.
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.
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.
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.
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.
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.
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.
A logistics-agent startup just raised a $150M Series C at a $1.2B valuation to run insurance claims and energy scheduling, not to answer questions. That's the clearest signal yet of where applied-agent capital is going: agents that finish operational work inside one industry. Here's why the premium moved, and how to position if you're building one.
OpenAI told staff Anthropic's ~$30B run-rate is really ~$22B. Both numbers can be GAAP-legal. The gap is one accounting choice — and the same choice quietly inflates a lot of startup ARR.
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.
Anthropic confidentially filed for a possible October Nasdaq IPO at a ~$965B valuation — the first frontier lab you build on to face quarterly earnings. Four things change for founders.
The reactive-chatbot era is quietly ending. Four shipped products — Microsoft Scout, Google's Gemini Spark, BridgeApp, and Replit's SEO Agent — now run on a heartbeat, hold their own identity, or act inside your logged-in browser. Here's what each does and what it changes for a team of one.
In July the money split two ways — police the agents, or own a regulated vertical. By the first week of August the split had a winner: security, governance, ops, and observability rounds stacked up week after week, while the marquee vertical deals had already closed back in spring.
This week the White House finalized a voluntary frontier-model testing framework — behind closed doors, and it hasn't shown the text to industry. In the same stretch, a fourth trillion-scale open-weight model landed. The throughline for founders: capability keeps getting more downloadable while oversight gets more private.
🎧 Listen
The Wire
