Every tool the agent writes stays deployed

Your agent builds its own tools. Asked to reconcile two CSV formats, it writes a converter. Asked again next week, it reuses it. Over a quarter it accumulates 200 small scripts.

On a function platform, 200 scripts is 200 deployments, each with a footprint: a cold start when touched, a charge when invoked, and a temptation to garbage-collect the ones nobody calls.

On Hoody the agent drops each script into the hoody-exec scripts folder, and the script is an endpoint at a URL the moment it lands. The 200 scripts are 200 files on the container's disk. The ones never called again cost what an unread file costs on a server you already pay for. The ones called daily run on cores in the same box.

Nothing gets deployed. Nothing gets pruned.

On a flat-rate server, an endpoint nobody calls is a file nobody reads.