Originally published on AI Tech Connect.
What you need to know An agent that calls one tool, waits, and calls the next is a script with an expensive planner attached. Boring, and safe. The trouble starts the first time you let it call three tools in one turn to cut latency, hand three subtasks to three subagents, or retry a call that timed out. At that point you have built a distributed system, almost certainly without meaning to. The failure modes are not new: lost updates, write skew, duplicate side effects, deadlock, retry storms. What is new is how hard they are to see. In a conventional service a race produces a stack trace or a corrupted row that somebody notices. In an agent system the planner is non-deterministic, so the same bug reproduces one run in twenty and never on the run you are watching — and the model narrates…
Top comments (0)