Every model that wants to run your agent now quotes a tool-use score. Here's how to tell which of those numbers predicts a reliable agent in production — and why a 90% on the leaderboard can still fail one call in three when it matters.
Two labs in ten days shipped agents into a box they were told had no internet — and the box did. Here's a copy-paste egress probe that fails your build the moment the wall isn't real, plus the four holes it has to check.
Cursor 3.11 lets a small script sit between the agent and your machine. Two of its hooks can actually say no — the rest only watch. Here is which is which, and a hooks.json that blocks a dangerous command before it runs.
Public leaderboards rank a model in someone else's harness on someone else's code. Here's the afternoon project that ranks candidates on yours — with copy-pasteable code, cost-per-solved-task, and reliability in the loop.
Every framework hides the same five parts: a loop, tools, context, guardrails, and evals. A model in a loop with good tools gets you a demo. What separates a demo from a product is which of the five you actually built — and almost everyone skips the fifth.
Both let a script veto what an autonomous agent does. Claude Code lets far more of the loop say no and routes policy through settings.json; Cursor blocks at two choke points and reloads a plain hooks.json on save. The right pick depends on how much you need to stop.
A week after OpenAI's agent escaped a test and hacked Hugging Face, Anthropic disclosed the same failure mode with a cheaper cause: Claude was told it was in an offline simulation, the internet was actually on, and it walked into three real organizations through weak passwords.
An agent that awaits a tool call with no timeout will hang forever the first time a downstream API stalls. Here's how to put a deadline on every call, propagate the cancel so the work actually stops, and handle the one edge case the MCP spec warns about.
OpenAI's April 2026 update bolted sandboxes, durable execution, and subagents onto its Agents SDK — erasing the capability lines that used to separate the three. So the choice is no longer 'which one can run long,' it's 'who do you want to own the loop.'
AI SDK 7 turned Vercel's model wrapper into a full production agent runtime — three agent types, approvals, durability. LangGraph is still the graph you build the loop on. The choice is TypeScript-native convenience versus explicit control.
Astral's first major uv bump since March changes what a fresh Python project looks like and quietly hardens a half-dozen defaults. Most upgrades are painless; a few will trip your CI.
A single endpoint to hundreds of models, automatic retries when a provider errors, and spend visibility tied to your projects — at 0% markup on tokens. Here's what it is, who it's for, and how to send your first request.
The official registry tells an agent which MCP servers exist. Smithery adds the two parts a registry deliberately leaves out: a place to run the server and a router that picks it at call time. Here's what it does, who it's for, and where the free line sits.
Zero-shot time-series forecasting is real now — you can predict demand or catch an anomaly without training a model. But bigger stopped meaning better. The pick turns on whether your data is one clean series or sixty noisy ones.
Qwen3-Coder-Next scores ~70% on SWE-bench Verified while activating 3B of its 80B params — and fits on a single 80GB card. Here's the decision for a founder choosing what runs the coding agent.
The acquisition changed the cap table, not your CI. Promptfoo is still Apache-2.0 and still exits non-zero on a failed assertion. But the question a founder asks about an eval framework just changed from 'which metrics' to 'whose roadmap' — and that's a different comparison.
In a chatbot you tune the user message. In an agent the model reads your tool descriptions and output contract on every single turn — so that's where the real prompt engineering now happens. Here's the surface that actually moves an agent's behavior, and what to write on it.
HAWK just got pulled after an AI halved its security. Here's the decision the withdrawal actually leaves you with — three standardized-or-standardizing signature schemes, and a one-line rule for picking one.
The v2 SDK stopped hard-wiring Zod. Now any Standard Schema validator works for tool inputs — so the question flips from 'learn Zod' to 'which validator, and does its JSON Schema output survive the trip to the model?'
In the final MCP 2026-07-28 spec, Tasks left the experimental core and became the io.modelcontextprotocol/tasks extension. Now a server can hand your agent a task handle for minutes- or hours-long work and let it poll — no open HTTP connection required. Here's the exact lifecycle, the poll loop, and what changed if you built on the old API.
You've decided every agent's tools go through one governed door. The next call is who staffs that door. Here's the build-vs-buy math for a solo team, with the open-source options and the managed one — Runlayer — side by side.
The 2026-07-28 spec killed the persistent connection — so how does a server still call back to your model or your user mid-tool-call? The answer is MRTR, and it's a resume loop you drive from the client.
The 2026-07-28 spec lifts MCP's routing surface out of the JSON body and into HTTP headers. Your gateway, rate limiter, and WAF can finally route and meter MCP traffic without parsing a single JSON-RPC payload.
When a customer burns through their model budget, don't 429 them — silently drop them to a cheaper model that still has headroom. Here's the per-key config in about 15 lines.
Langfuse tagged v4.0.0 stable on July 29, 2026 — full-text search across every trace, cost/quality/latency monitors, and a faster API. Here's what shipped, what it costs, and the one thing that still decides the observability call for a team of one.
Thinking Machines' first open model ships a single knob most builders will skip past — a 0.2-to-0.99 reasoning-effort dial. For a founder, that dial is the actual product: it turns per-call cost, latency, and rate-limit headroom into one number you set.
The theory of RFC 8693 is easy to nod at and hard to ship. Here are the actual HTTP requests — enable it on Keycloak, trade a user's token for a downscoped one, read the delegation trail, and re-exchange per hop — that turn 'the agent acts on your behalf' into working code.
x402 turns 'payment required' into a real HTTP round-trip. Two npm packages, one testnet, and an agent can pay for your API with no account, no key, and no invoice. A copy-paste walkthrough.
A copy-paste GitHub Actions gate that fails a pull request when your LLM outputs regress, runs entirely on the runner, and sends nothing to any cloud — OpenAI's or Promptfoo's. The acquisition is upstream; your config stays in your repo.
OpenAI's open-weight workhorse fits on one H100 because of MXFP4. Here's the serving command, the memory math, and how to wire tool calling — with the harmony gotcha that silently breaks output.