#ai-agents
Every post tagged "ai-agents".
303 posts · showing 241–250
-
The Verifier in the Loop: Designing an Oracle Your Agent Can Iterate Against
Coding agents work as well as they do because compilers exist. In other domains the oracle is something you build — and most tasks have one hiding in them if you spend ten minutes looking.
-
What a System Prompt Should and Shouldn't Contain
Five things belong in a system prompt. Most of what accumulates there — tool instructions, deterministic rules, incident patches, data — belongs somewhere it would actually work.
-
Where Agents Don't Belong (Yet)
Six task shapes where the agent architecture is the wrong fit regardless of model quality — each with a tell you can check in an afternoon, before committing a quarter to it.
-
Queueing and Backpressure for Agent Workloads
A run can take four seconds or four minutes, and you can't tell in advance. Size the pool to the provider's rate limit, split queues by shape — and check the one timeout relationship that silently runs your task twice.
-
Observability for Agents: What to Log Beyond the Trace
A trace explains one run and nothing about your system. The two layers above it — run records and aggregates — plus three agent-specific signals that standard APM will never suggest.
-
The Code-Review Agent That Commented on Everything
Nine comments on a twelve-line PR and the team muted it. Any agent asked to find things will find them — the fix is a hard cap that forces ranking, and pointing it at what humans actually miss.
-
Sandboxing Code Execution: What a `run_code` Tool Actually Needs
One tool replaces dozens — and hands a model that reads untrusted text a general-purpose mechanism for doing anything the process can do. Four boundaries, four isolation levels, and the one people leave open.
-
Canary Releases for Prompt Changes
A sentence added to fix one behavior routinely changes three others. Ship prompts like behavior: versioned by rendered hash, split by stable key, and compared on tool distribution — the row nobody collects.
-
Chunking for Agents Is Not Chunking for Search
Search results are read by a person who fills in the gaps. An agent doesn't — it acts on the fragment. That one difference changes how you chunk, how many you return, and what "no results" should mean.
-
Agents That Wait: Callbacks, Webhooks, and Long-Running Tools
A twenty-minute export breaks the assumption that tools return quickly. Handles, in-loop polling, and true suspension — plus the expiry field that stops suspended runs leaking forever.