Menu

The Agent That Polled 55 Times to Learn Nothing
📰

The Agent That Polled 55 Times to Learn Nothing

#hackernoon#technology#lead#sleep#went
Reading 0:00
15s threshold

When one agent waits on another, something has to tell the waiting side that the work is done. In normal backend code, that's a solved thing; nobody writes a loop that sleeps for four minutes and then checks a table. With coding agents it comes back again, because the agent decides how to wait by itself, and for a model with a shell the easiest option is just to sleep and look again. And it works; it's easy to read in a transcript too. The catch is the cost, and you only see it once you actually count the turns.

I found this in my own multi-agent delivery pipeline, in one of the branches I was exploring: a deeper hierarchy of agents. I didn't take that branch much further and went back to a flatter structure, but this case is what made me adapt the logic and the harness around it. Below you will find how it looked in the logs, what it cost, and what changed after.

The Setup: an orchestrator, a Lead, and the teams under it

The pipeline runs on a production codebase, and in that branch it had three layers.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.