"When Agents Do Not Stop" (arXiv:2607.01641) is a study of agents that never finish. The authors call it an infinite agentic loop: the agent keeps calling a model, a tool, or another agent because nothing on that path ever tells it to stop. The cost is money, a context that grows until it breaks, and the same side effect repeated on an external system.
They wrote a tool that reads agent code, finds every place the code cycles, and checks whether each cycle has a limit that actually applies. Across 6,549 open-source agent repositories it flagged 74 cases, and 68 turned out to be real. The real ones come in a few shapes: retries with no cap, tool calls repeated with no cap, two agents talking with no turn limit, workflow steps that route back to themselves, and a runner and an evaluator feeding each other.
The useful finding is about turn limits. Most frameworks let you set one, and most of the confirmed loops were in code that had one. Developers leave it out, set it far too high, or put it somewhere the loop never passes through. A limit only stops a loop if it sits on the path that repeats, and someone has to know which path that is. So the practical check is not whether a limit exists, but whether the loop you're worried about would hit it.
3 questions
Answered, plainly.
Self-host Tessary.
Free and open source. Point it at the traces your agent already emits.
Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md
docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y