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.
Anthropic ships two agent-memory primitives with nearly identical names. One is an interface you back yourself; the other is managed, versioned state you rent. The deciding question isn't which remembers better — it's who runs your agent loop and who should own the bytes.
MAI-Realtime — spotted in a hidden preview this week — gives Microsoft a native listen-and-speak voice model. With OpenAI and Google already there, full-duplex just stopped being a differentiator. Here's where the moat moved.
Both give an agent memory that survives across sessions. One is a primitive you write to; the other is a layer that decides what to remember for you. That single difference — who does the extraction — is the whole decision, and it's the one the comparison tables never name.
Three genuinely self-hostable eval-and-tracing platforms, three different licenses. The choice that decides your lock-in isn't a feature — it's the LICENSE file. Here's who picks which.
The headline '$/1M tokens' number is the one you'll budget on and the one that's wrong. Here are the six things a model's pricing page hides — and the questions that turn a sticker price into your actual bill.
The technique that cuts RAG retrieval failures by two-thirds isn't one trick — it's four, stacked. Here's the whole build: contextualize each chunk, index it two ways, fuse the rankings, and rerank. With code.
A copy-paste walkthrough: the Cloudflare Agents SDK puts each agent in its own Durable Object — its own compute plus its own SQLite file — so memory lives inside the agent at the edge, with zero infrastructure to run.
Project Think is Cloudflare's opinionated base class for long-running agents: durable turns that survive an eviction, sub-agents with their own SQLite, and a code sandbox — wired together. Here's the whole loop, from empty folder to a turn that resumes after a crash.
Google shipped Agents CLI on August 3. The interesting part isn't a new terminal agent — it's that Google is distributing its Cloud-deploy playbook as skills you drop into Claude Code, Codex, or Antigravity. Here's what it actually is, and the wedge it opens.
Microsoft made Foundry's hosted agents generally available — and the interesting part isn't the runtime. It's that the old 'which framework?' decision is finally decoupled from 'where does it run?', and every deployed agent now gets its own Entra identity. Here's what actually changed for a solo builder, what it costs, and where the lock-in hides.
Google's Agents CLI shipped August 3. Here's the whole loop — install, scaffold, run locally, evaluate, deploy, publish — with the real commands, so you can take an ADK agent from an empty folder to a Google Cloud runtime in one sitting.
Four open-source tools now give Claude Code, Codex, and Cursor one shared memory. They don't disagree on recall — they disagree on what your agent's memory *is*: files you own, a tool your agents call, a local service, or a second-brain agent.
Cline's July 31 build routes native MCP tool calls by server name instead of a random in-memory id, so routing outlives restarts and server-list changes. It landed three days after MCP's spec dropped sessions entirely — the same lesson, on both sides of the wire.
Existing agents keep running, but the model catalog is frozen at July 30 and new accounts get a 403. The real decision isn't Classic vs AgentCore — it's whether your agent logic is portable enough that AWS's next retirement doesn't become your next rewrite.
July's funding wave bet on controlling the agents or owning a regulated vertical. On August 3, capital jumped one layer lower — to the reactors that power the models, the light-based chips meant to run them cheaper than a GPU, and the autonomous hackers that defend against other autonomous hackers. Here's the day's board and the one line each raise writes for a team of one.
Nine models, four price tiers, one decision. A founder's reference for what to run each agent workload on this month — with real per-token prices, the caveats that make them lie, and the one config change that lets you switch.
Every 'give your agent memory' course collapses three different problems into one word. They aren't the same problem, and they don't use the same code. Here are the three tiers, the one call that wires each, and the rule for when a fact should climb from one tier to the next.
Once an agent's memory store is large, the question stops being what to keep and becomes what to surface right now. Three signals compete for that decision — and using any one alone breaks in a predictable way.
This week the two biggest AI markets finalized opposite bets. The White House met the top labs on August 4 with a safety framework it finished on August 1 and won't publish. Two days earlier, the EU's transparency duties switched on — binding, specific, and public. For a solo founder, only one of these is a checklist you can act on today; the other is a black box that still moves your release calendar.
Last week the story was capital and access. This week it's the model tier you actually run agents on. An open-weight budget model started out-benchmarking flagships, a managed model's introductory price is about to jump 50%, and the EU's transparency duties quietly switched on. For a team of one, your default agent backend is now the decision worth an afternoon.
This week's throughline is money and machinery — a token bill that jumps 50% on September 1, agentic security graduating from demo to preview product, and venture capital concentrating on the agent control plane.
Comparing hourly GPU prices first is the rookie mistake — half these clouds don't sell you the thing you think you're buying. Here's the product shape of each, and the utilization math that decides between renting by the hour and paying by the token.
Agents that run for hours need retries and checkpoints that survive a crash or a deploy. Temporal gives you that with a cluster to run; Hatchet gives you the same on the Postgres you already have.
What goose is, who it's for, how to start in one command, what it costs, and the honest catch — the on-machine agent that connects to any tool over MCP and any model via your own key, now a Linux Foundation project with ~29K GitHub stars.
OpenAI shipped a login button on August 2, so the SSO menu now has a fourth option. But the three you already know are not interchangeable, and adding ChatGPT is a distribution bet, not a UX tweak. Here is the decision, by audience, cost, data, and lock-in — with the one rule Apple will reject your app for missing.
OpenAI is rolling out a login button — Airtable, GitLab, HubSpot, Notion, Supabase, and Vercel are first. The convenience is real, but the actual move is bigger: your signup can now start inside ChatGPT and Codex, where a growing share of builders already live. Here's what it does, what partners get, and whether you should add it.
Working memory, session memory, and long-term memory solve three different problems. Most agents that 'forget' are using the wrong one — or paying for all three when they needed one. A founder's decision guide, with the tools mapped.
A tenant_id column keeps your rows apart. It does nothing for your vector store, your prompt cache, your agent memory, or your trace logs — four leak surfaces classic SaaS never had. Here's how to close all five.
Software approval gates stop the agent that asks nicely. They do nothing about the one that's been prompt-injected. Here's the hands-on way to require a physical key press — bound to one specific action — before your agent can spend money, ship a config, or sign a contract.