Hoody Daemon

The Hoody Daemon is the local background service that powers the Hoody platform on your machine. It manages runtime processes, orchestrates agent workflows, and exposes a local HTTP API that the Hoody dashboard, CLI, and SDKs communicate with. Every command you run from the Hoody interface — launching an agent, managing containers, reading logs, or syncing state — is ultimately handled by the daemon running on localhost.

When to use the Daemon API

The Daemon API is intended for:

Local integrations — building tools, scripts, or automations that interact with a running Hoody instance on the same machine.
Custom clients — constructing alternative UIs or CLI frontends that need to talk directly to the daemon without going through the official dashboard.
Agent orchestration — programmatically starting, stopping, and monitoring agent processes and their associated resources.
Diagnostics and observability — reading logs, inspecting container state, and querying the health of Hoody-managed services.

API structure

The Daemon exposes its endpoints over a local HTTP server. All requests are served from the loopback interface and use standard REST conventions:

Requests and responses are JSON.
Authentication is handled via a locally-issued bearer token generated on first launch.
Endpoints are grouped by resource (agents, containers, logs, workspaces, etc.).

Refer to the individual endpoint reference pages in this section for the full list of available operations, their parameters, and example responses.

Base URL

By default, the daemon listens on:

http://127.0.0.1:<port>

The port is assigned at startup and can be found in the daemon’s log file or by running hoody status from the CLI.