How AI agents manage homelab services, and what’s not yet automatable.Documentation Index
Fetch the complete documentation index at: https://docs.augustin.ai/llms.txt
Use this file to discover all available pages before exploring further.
Approach
Each service directory has anAGENTS.md describing its management interface. Agents discover ports, URLs, and env var names at runtime from compose files and .env files — nothing is hardcoded.
Preference order:
- CLI via
docker execor host-installed tools - REST API via
curl - Config file edits + container restart
Host Dev Environment
Node.js is managed via fnm (installed to~/.local/bin), keeping the OS clean. Node versions and global packages live in ~/.local/share/fnm/.
Globally installed tools:
wrangler— Cloudflare CLI (Workers, DNS, tunnels, etc.)kuma— Uptime Kuma CLI (monitors, notifications, tags, maintenance)
Gaps
Services that can’t be fully managed by an agent today:| Service | Issue | Workaround |
|---|---|---|
| Miniflux | No API key configured | Generate one in UI: Settings → API Keys |
| Uptime Kuma | Session-cookie auth only, no API key | kuma CLI installed on host |
| Yamtrack | Session-cookie auth only, no API key | None — UI only |
| Chaptarr | No API or CLI | UI only |
| Draw (Excalidraw) | No API or CLI | UI only, data in filesystem |