On July 22 OpenAI shipped Presence, a managed platform for running production agents — policies, guardrails, simulations, evals. The tell isn't the features. It's that you can't buy it with a credit card.
Machine identities now outnumber humans 109 to 1, and most of the new ones are AI agents. Here's the five-part playbook for governing them before it's an audit finding — and why Oak just raised $60M to sell you the control plane.
The old dance was create-then-send: one request to make the session, a second to hand it work. A July 22 change lets you pass the first events at creation and start the agent loop in a single round-trip.
Your agent writes code, then it wants to run it. Do that on your own host and one bad line reads your secrets. Here's the copy-paste path to a disposable sandbox in five minutes — in E2B and in Modal.
The static key in your agent's environment variable is valid forever and revocable only if you remember it exists. Here are three copy-paste patterns — cloud STS, Vault dynamic secrets, and a token broker — that swap it for a credential that expires on its own.
Your agent keeps calling the same web search, the same GET, the same DB lookup. Memoize the tool's output keyed on its arguments — but only for the tools where a stale answer can't hurt you.
On July 21, Harness put five new products around the AI agent lifecycle — evals as quality gates, prompts behind feature flags, OpenTelemetry traces, deployment governance. The bet is that agents ship through the same pipeline as your code.
Microsoft's Agent Framework for Go hit public preview weeks after Google's ADK for Go matured. The model labs whose APIs you actually call haven't followed. Here's what that split means for your backend.
The two model names every DeepSeek integration hard-codes stop resolving at 15:59 UTC on July 24. The fix is one string per call — plus one default that will quietly change your latency and bill.
Anthropic hasn't announced it, but the leaks, the Cursor sighting, and the prediction markets all point at this week. The tell isn't a new capability ceiling — it's that the whole story is cost-per-hour for long-running agents.
Tomorrow, a request to claude-opus-4-7 with speed: "fast" stops running and starts erroring. The fix is a single model id — and while you're in the console, four other July changes are already moving your bill.
Kimi, Qwen, GLM and DeepSeek are cheap, strong, and now politically radioactive. You don't need to pick a side in the distillation debate — you need a supply chain that survives an Entity List letter. Here's the checklist.
Three open-source ways to hand an AI agent a real browser — a Python autopilot, a TypeScript control surface, and an MCP plug. Here's how to pick the one that fits your stack instead of fighting it.
AWS shipped a dashboard for the question every founder paying per token has been guessing at: are the coding agents actually speeding us up, and who should get more access? It reads Claude Code, Codex, and Copilot over plain OpenTelemetry.
Google Cloud's new reference architecture gives an agent durable memory with no vector database and no embeddings — an LLM consolidates in the background and writes to SQLite. Here's the decision: when that beats retrieval-on-demand, and when RAG still wins.
Alibaba Cloud used WAIC 2026 to stake a category — a cloud rebuilt around agents, not VMs. There's no price and no GA date yet, so read it as positioning. Here's the part a solo founder should actually act on.
For two years, running your agent's code safely meant bolting on a third-party sandbox. In 2026 every layer shipped its own: OpenAI and Anthropic in their agent SDKs, Google in Cloud Run, Cloudflare at the edge. The build-vs-buy math just moved.
You wrote a perfect Skill and Claude ignores it. The body is almost never the problem — the description is. Here's how to write one that gets picked from a hundred.
Three open-source memory layers, three different answers to one question a regulator, a customer, or your own incident review will eventually ask: what did the agent know, and can you prove it? Mem0 optimizes recall, Zep optimizes change-over-time, Statewave optimizes proof.
You don't need a vector database server. Three embedded stores run inside your app — and the right one depends on one number: how many vectors you'll actually have.
The MCP Tasks extension gives your long-running tool a way to report progress without a held-open stream. It does not give you retries, durability, or scheduling. Here's which side of the line each one lives on.
The stateless spec got the headlines, but the same release ships MCP Apps — a standard way for a server to hand the host an interactive HTML interface. Here's how to wire one up.
The 2026-07-28 Model Context Protocol spec removes the handshake and the session. If you ship a remote MCP server, here's the one-week, do-this-in-order checklist — install the betas, kill sticky sessions, verify auth, load-test — with a link to the deep dive behind every step.
Four ways to build an agent on Claude, separated by two questions: who writes the loop, and who runs the box it executes in. A decision matrix for founders who've outgrown the hand-rolled while-loop.
Your agent needs to drive a browser. One option skips rendering entirely to run 11× faster, one renders everything for maximum fidelity, one just hands you managed Chrome. The choice is a tradeoff, not a winner.
LangGraph 1.0 is stable and durable — but the real MCP win is treating each tool as its own graph node. Most builders should not rewrite. Here's the line.
Your agent fires twenty tool calls across three MCP servers and one of them is slow. Which one? The 2026-07-28 spec fixes the trace-header names so the whole chain becomes a single span tree. Here's the wiring, client and server.
A code-first migration walkthrough — strip the session, read context from _meta, poll Tasks instead of SSE, and run behind a plain round-robin load balancer.
The startups getting funded this month sell one thing: a list of every agent running in the building. You can build that list yourself this afternoon — here's the registry schema, the scan, and the policy gate.