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.
Two things collided this month. On July 31 DeepSeek shipped V4 Flash 0731 — an open-weight model that beats its own Pro on agent benchmarks at $0.14/$0.28. On August 31 Claude Sonnet 5's $2/$10 introductory price expires and jumps 50%. If bulk agent work is your biggest line item, this is the decision to make before the cliff.
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.
The August 4 build extends sandbox credential masking from environment variables to files on Linux and WSL — a sandboxed command reads a decoy copy while the proxy swaps in the real secret on egress. Here's the mechanism, the one setting it depends on, and where it quietly falls back to a hard deny.
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.
Three experimental endpoints — generate, improve, and templatize a prompt — return an error after August 17, and the legacy Workbench that held your saved prompts and evals goes with them. Here's what to export today and a copy-paste replacement that no vendor can deprecate.
On August 5, calls to claude-opus-4-1 stop working — no grace period. And on Opus 4.7 and later, setting temperature, top_p, or top_k at all now returns a 400. Both are one-line fixes if you catch them before your users do.
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.
Wiring the three memory layers is the easy part. Keeping them healthy over weeks of real traffic is where agents fall over. Here are the four ways memory rots — unbounded growth, stale retrieval, no forgetting, and poisoning — and the specific fix for each.
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.
OpenAI open-sourced its Codex Security CLI in late July, and it emits SARIF — the same format GitHub's Code Scanning tab already reads. Here's the copy-paste pipeline that turns an AI scanner into a real, blocking PR gate, plus the one setting that stops it from crying wolf.
The gap between 'send' and the first visible token is where users decide your product feels fast or broken. Here's the end-to-end SSE path — backend to browser — and the buffering bug that silently un-streams it.
One command starts the server. The VRAM formula tells you which open models you can actually run on a founder budget — and the cost-per-million math tells you when self-hosting beats just paying the API.
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.
There are now ~60 tools for running Claude Code and Codex in parallel. The choice that matters isn't the tool — it's the control surface. Here's the decision.