An agent stands up the whole stack with curl

Your local agent needs a staging stack: database, API, worker, nightly job. It has no Hoody SDK installed and needs none: its bash tool speaks curl, and every Hoody primitive is an HTTP endpoint.

So it works down the list. One call creates the container. Terminal calls install and configure. Daemon registrations turn the API and worker into long-running programs with boot priorities. A cron entry schedules the nightly job. SQLite is already a URL. Twenty minutes of HTTP later the stack is up, and the agent's last call is a snapshot named staging-v1: the assembled machine, saved, for anyone to restore.

No SDK to teach, no MCP server to stand up, no plugin. The orchestration layer was HTTP all along.