AGENT INFRASTRUCTURE

Vercel added Hermes Agent to AI Gateway and made Vercel Sandbox a terminal backend for the open-source agent. Hermes is now fully BYO: your own model routing through 200+ models at no markup, and your own cloud microVM for every agent command. Here is what that unlocks and why the agent control plane is consolidating.

Cloudflare is merging Workers AI and AI Gateway into one control plane: unified /ai/ REST API, auto-created default gateways, AI Gateway credits spendable on Workers AI, and model-first routing that picks the provider for you. Here is what changes and what stays.

Vercel's Chat SDK can now suspend a Workflow SDK run until someone clicks Approve in a chat thread. One requestApproval call replaces the approvals table, the onAction handler, and the polling loop - with verified decisions, scoped approvers, and a wait that survives deploys.

DeepSeek V4 Flash routed to Novita on Vercel AI Gateway is 90% off for Pro customers through August 11, dropping the effective rate to $0.014 input / $0.028 output per million tokens. Here is the verified before/after math, the provider-pinning setup, and what a 10x cheap agent loop means for routing decisions.

The v0 API is now generally available: programmatic, headless access to v0's app-building agent. Send a prompt, get a running app with a live preview URL you can embed, then deploy to Vercel in one call. Here is what changed, how the sync/async/streaming model works, and how it fits in an agent loop.

AI Gateway spend budgets now scope to teams and projects, with hard dollar limits that reject requests, email alerts at 50/75/100%, and CLI-managed defaults. Here is how the three scopes compose and where it fits your cost stack.

A July 2026 paper from Tencent Hunyuan turns agent harnesses into behavior-level maps. The useful lesson for builders is simple: code search is not enough when one behavior spans prompts, tools, state, permissions, and runtime policy.

A Show HN project claims large agent-cost cuts by rendering bulky context as images. The useful lesson is not the trick itself. It is that compression needs evals, byte-safety rules, and per-request accounting.

AI agents are getting their own computers. Here is how to choose a sandbox architecture: filesystem isolation, network policy, secrets boundaries, snapshots, and when shell access is overkill.

Aharness, LangChain's custom harness pattern, and OpenAI's code-first migration all point to the same next step: agent processes need typed gates, validated evidence, and controlled transitions.

Oak is an early bet that AI coding agents need version control shaped around sessions, virtual workspaces, and token budgets. The idea is risky, but the pressure on Git workflows is real.

The Bayer and Thoughtworks PRINCE case study is a useful reminder that reliable agentic AI comes from context routing, traces, evals, monitoring, and human review, not from a better prompt alone.

As coding agents get easier to delegate to, the scarce resource shifts from code generation to review capacity, CI minutes, environment reliability, and merge discipline.

Hex's data-agent lab shows the practical eval pattern AI teams should copy: compare candidates against stable baselines, keep receipts, and judge changes by task behavior.

GitHub's latest agent workspace trend points at a boring but important primitive: agents need explicit filesystem contracts before they get more tools.

Anthropic's June 15 Agent SDK credit split is not just a pricing tweak. It is a signal that autonomous coding workflows need separate budgets, lanes, and receipts.

Ruflo turns Claude Code and Codex into a larger agent harness with plugins, memory, swarms, MCP tools, and federation. The useful question is not the star count. It is how much harness you actually need.

DD shipped six paid products in a single day. The thesis is simple: agent infra for small teams. $20 a month each, $50 for the bundle. Here's what we shipped, what's alpha, and what's still being wired.

Ten private tools shipped overnight - observability, skills, hooks, prompts, and evals - aimed at the agent infrastructure gap small teams keep falling into.