The agent's answer is a cron entry

You ask the agent to make sure the database gets backed up. It looks. There is a backup script in the repo, a README that says "nightly," and no cron entry anywhere.

It doesn't write you a note telling you to schedule it. The cron kit is one of its fleet tools, so it creates the entry itself: a POST to the cron service, 0 3 * * *, the script path, a log target. Then it reports what it did, and the entry sits in the container's crontab for you to read, edit, or delete.

The conversation ends. The schedule doesn't. A month later the backup has run thirty times, and the agent that scheduled it has no session open.

On most platforms, the agent recommends infrastructure. On Hoody, it provisions it.