“Nothing existed”: a buyer went looking for a way to stop the agent
By The Lucidrail Team · 2026-06-29
A developer left an AI agent running, stepped away for about twenty minutes, and came back to a bill they had not planned on. It was not a large number. It was thirty-two dollars.
The amount is not what makes the story useful. What they did next is. They went looking for a plain control — a way to have the agent stop on its own once it crossed a dollar limit — and came up empty.
I left an AI agent running, walked away for 20 minutes, and came back to a bill I didn't expect. I searched for a tool that could just stop the agent when it hit a dollar limit. Nothing existed. — sahiljagtapyc, on Hacker News
A buyer walking to the shelf for a basic safety control and finding it bare — that is the part worth sitting with. The gap is not exotic. It is close to the first thing you would reach for.
Not $47,000. Just $32
The famous version of this problem is much larger. In one widely republished write-up, a team watched two agents get stuck talking to each other for eleven days and ran up a $47,000 bill before anyone pulled the plug. Set the two stories side by side and the shape is identical. No cap. The bill was the first real signal. The only thing that changed was how long the operator was away.
That is the uncomfortable part. When there is no cap, the size of the bill is set by luck — by how long it takes you to notice — not by any limit you chose in advance. Thirty-two dollars because someone came back in twenty minutes. Forty-seven thousand because a team came back in eleven days. Same missing part.
An alert is not a stop
Most of what is on offer today reports spend after it happens. A team running seventeen agents put it plainly when they described what passed for cost control:
The UI for all of that spending was our credit card statement. Once a month. After the fact. — peiyaooo, on Hacker News
A statement, an email alert, a dashboard you open later — all of these tell you the money is already gone. That is not what the developer above went looking for. They wanted a limit that acts on its own, in the moment the line is crossed, with no human needed to read a warning and rush to hit a button. A monitor watches. A cap acts. They are not the same tool, and only one of them stops the bill.
The caps that do not always hold
There is a harder version of this, and it catches the people who did try. On the CrewAI forum, an operator hit an infinite loop and asked for a setting to limit the crew's total token use so it would not keep spending:
This infinite loop can cause an insane high token usage. — Raja_Speet, on the CrewAI forum
The framework even shipped a limit for exactly this — a maximum-iteration cap — and operators have reported it failing to stop the loop anyway. So a limit in a config file is not automatically a limit that holds. A cap only counts if it survives the one case you bought it for: the runaway. If it can be skipped on error, or quietly ignored once the loop starts, it was decoration.
What “stop the agent” actually needs
Strip it down and the request is simple. Three things have to be true for a cap to mean what the buyer thought it meant:
None of that is advanced. It is close to the first thing anyone would ask for. The striking thing about the developer's search is not that they wanted something clever. It is that they wanted something basic and could not find it on the shelf.
This is the exact control we set out to build at Lucidrail: per-company budgets with live metering, and hard caps that stop a runaway before it bills — enforced outside the agent, not left to a warning someone has to catch in time. The aim is modest. Make the limit you set the limit that actually holds, on the day it matters.
- It acts instead of alerting — it trips on its own at the threshold, without waiting for a person to notice.
- It is enforced outside the agent — a wall the agent cannot spend past, not a number the agent is politely asked to respect.
- It holds on the bad day — the loop, the retry storm, the eleven-day night — because that is the only day it exists for.