The CrewAI demo worked. Then the tool call retried 913 times. Here is the agent failure mode nobody shows in the demo. The CrewAI flow works on the first run. The agents are named well. The tasks are clear. The tool call returns the right data. Then production input changes. The vendor API returns a 429. The search tool returns the same empty page. The file tool cannot find the path. The agent does what agents do. It tries again. Why this gets expensive One retry is fine. Ten retries might be fine. Nine hundred retries is not a bug report. It is a bill. The problem is not CrewAI. The problem is shipping an autonomous loop without runtime limits. If the agent can retry, the runtime needs to know: How many times did this action repeat? Did the tool input actually change? Is cost rising faster than expected? Has a human approved this path? Should the run stop now?…