emon Manager
The Hoody Daemon is a local process supervisor built on top of supervisord. It runs inside a Hoody container and is responsible for managing user-registered long-lived daemon programs as well as short-lived ephemeral programs launched on demand. The daemon supervises process lifecycle, exposes status and logs, and provides a standardized health endpoint for monitoring.
The daemon is intentionally narrow in scope: it supervises programs. It does not orchestrate agent workflows, manage containers, or expose a workspaces resource. Agents are handled by a separate namespace, and container management lives outside the daemon entirely.
The Daemon is an in-container Kit service reached through the Hoody Proxy. It is not part of the management/control-plane Hoody API. All daemon endpoints are served from the container URL:
https://{projectId}-{containerId}-daemon-1.{server}.containers.hoody.icuReplace {projectId}, {containerId}, and {server} with your project’s values before issuing requests. Endpoints are mounted under /api/v1/daemon/....
The daemon itself has no authentication of its own. It sits behind the Hoody Proxy, which authenticates and authorizes every request. The container URL is the credential boundary — if the proxy is configured to require a Bearer token, attach it as Authorization: Bearer <token>; otherwise the proxy authorizes the request based on the routing context alone. The daemon does not mint or issue per-launch tokens.
Endpoints are grouped by the resource they act on:
/api/v1/daemon/programs)/api/v1/daemon/status)/api/v1/daemon/quick-start)/api/v1/daemon/health)Program management
Register, inspect, edit, remove, and reset custom daemon programs. List registered programs, fetch a single program by ID, add a new program to the supervisord configuration, edit its configuration, remove it, or reset it to defaults.
Program control
Lifecycle actions for a registered program: enable, disable, start, and stop. These endpoints delegate directly to the corresponding supervisorctl commands.
Status & monitoring
Aggregate status across all programs, per-program status, and per-program log streaming. Use these endpoints to build dashboards, alerts, and log viewers on top of the supervised process tree.