Design and operation of capabilities that models or agents invoke to interact with software, data, or external environments.
Tagged articles
17 articles in this tag.
The demo worked because the agent was running on your laptop. It had your credentials, your network, your home directory, and your shell history. Move it…
Read tutorial
The demo agent works. It reads the file, runs the test, patches the bug. Then it ships to a second tenant, the session runs for six hours, the process dies…
Read tutorial
A user reports a wrong answer. You pull the trace. Every tool call succeeded, every span is green, latency is normal, and no error was logged anywhere. The…
Read tutorial
Every agent builder hits the same wall. The first working agent is small: a system prompt, a few tools, a loop. Then someone needs release notes. Someone…
Read tutorial
The demo works. The agent books the flight, summarizes the repo, files the ticket. Then you point it at a task with one extra branch, and it calls the same…
Read tutorial
The agent writes the function, re-reads it, decides it looks correct, and stops. The code is wrong. This is the most common failure in autonomous coding,…
Read tutorial
The demo works. The agent reads the queue, drafts the update, and posts it. Then someone asks who approved the change, which run produced it, and how to…
Read tutorial
A research agent runs for twenty minutes. It pays for dozens of model calls, executes a dozen tool calls, and commits three external side effects. Then the…
Read tutorial
The agent worked yesterday. Today it burns forty thousand tokens before it reads your first instruction, and the hook that used to register identity with a…
Read tutorial
The redesign did not delete state. It relocated it — and everything downstream follows from where it landed.
Read tutorial
A team wires up an MCP server, watches the tools appear in the client, and concludes the integration works. Then a tool gets renamed upstream, a resource…
Read tutorial
Your agent has thirty tools, four MCP servers, and a plan-mode toggle. It still fumbles a routine refactor, and when it does, you cannot tell whether the…
Read tutorial
An agent that acts without reasoning is not reasoning. It is guessing with a tool schema.
Read tutorial
That is the shape of the failure I keep seeing in agent systems that look governed and are not. A team writes a planner prompt, a coder prompt, a reviewer…
Read tutorial
Two teams run the same model on the same task. One ships reliably. The other drowns in tool-call latency, context bloat, and incidents nobody can explain…
Read tutorial
A failed agent run rarely looks like an interface problem. It looks like a model problem: wrong tool, malformed arguments, an error swallowed and retried…
Read tutorial
Two teams ship the same model, the same prompt, the same tool list. One agent finishes a multi-step task. The other stalls, loops, and quietly corrupts its…
Read tutorial