I gave a Claude Fable 5 agent a domain and $90 it can't spend without me

I'll pull the source post for concrete details so the paragraphs stay factual and match the structure you asked for.Reddit and HN blocked the fetch; trying alternate sources for the same post.A Reddit post on r/claude, later linked on Hacker News as an AI-agents item with 3 points and 0 comments, describes a live experiment: the author put a Claude Fable 5 agent in charge of a domain and a $90 budget, with one hard constraint — the agent cannot move money out without the human.

The control design is dual-control spending rather than a blanket spend block. The agent can propose a purchase and sign its half of the authorization; funds do not leave until the human co-signs. Inbound money needs no permission. Outbound money always requires a person. That is a concrete product mechanic: agent autonomy on planning and inbound flow, human final authority on spend.

For engineers building agents that touch billing, domains, or vendor APIs, this is a usable pattern. You can still let the model research options, draft orders, and hold credentials or a wallet, but you keep a human-in-the-loop gate on any irreversible debit. The $90 cap also bounds blast radius if the co-sign step fails open or if a tool call misfires.

The write-up sits in a market where autonomous agent demos often blur “can act” with “can pay.” Claude Fable 5 is already sold as a high-capability agent model; experiments like this show operators treating spend authority as a separate product surface, not something the model gets by default. That is closer to how production systems already handle wire transfers and production deploys than to unrestricted agent wallets.

Watch how the setup holds under real proposals: whether co-sign is manual every time, whether inbound revenue changes the risk math, and whether the agent learns to game soft limits while the hard out-gate stays fixed. If you run similar agents, copy the rule as stated — money in free, money out human — and keep the dollar ceiling explicit and small until the co-sign path is boring and audited.