Willison says coding agents mean pay‑per‑use services need hard spending caps
Simon Willison argues cloud services should cut off at a set bill by default, since agents make surprise bills of thousands of dollars easier. AWS and Google Cloud only just added caps.
Developer Simon Willison argued on 3 October that pay-by-usage services and APIs should ship with default hard budget caps, a setting that stops service and returns errors once a monthly limit is reached. His post says soft caps that only send warning emails fail, because people sleep through them while bills grow.
https://x.com/simonw/status/2106528704902164855
Willison ties the proposal to coding agents. In his telling, they make it easier to deploy applications that can generate large, unexpected charges. He puts the typical damage at several hundred or several thousand dollars, with surprise bills above $10,000 the point where it becomes serious, and says some developers avoid AWS for personal projects out of fear of exactly that.
He credits two providers with moving. AWS launched spending limits on 16 September, he writes: when usage reaches the cap, the project pauses for the month, though he says the feature is limited to select customers. Google Cloud added Spend Caps in July, letting users cap spending on specific services inside a project.
Willison proposes that turning a cap off should need explicit wording: "Remove the budget cap. My application will not be shut down if I exceed the configured budget limit, and I will be responsible for subsequent charges." The post is opinion, not a vendor announcement. Neither AWS nor Google has commented, as far as the sources show.
The argument may matter most to people running agents unattended. A hard cap could turn a runaway loop into an error message instead of an invoice, but it also takes the service down, which is why Willison says it should be the default. He does not say which other providers lack such limits.