Fleet manages multiple Dockerized Hermes agents from one local console
Fleet is a local web console for creating, configuring, watching, and operating that run in Docker. It is meant for people who run more than one agent on a workstation, home server, VPN, or trusted LAN. The console brings noisy daily tasks into one place, including service health, provider defaults, shared , chat sessions, browser sidecars, VNC, , local web publishing, backups, restores, clones, remote nodes, and setup checks.
Standard are the default path, and Nemo are supported when the nemohermes runner is available or automatic installation is enabled. Setup needs Node.js 20 or newer, npm 10 or newer, Docker with v2, and git if Fleet should automatically clone the Hermes source. The quick start is `npm run setup`, then `npm start`, then opening `http://127.0.0.1:5180`.
Fleet keeps runtime data and secrets local by default, requires an access token when exposed on a LAN, and excludes secrets from backups unless the operator deliberately includes them.
Key points
- Fleet can create, start, stop, restart, update, delete, clone, back up, and restore from one dashboard.
- It stores shared provider defaults and locally, then syncs them into selected agents.
- It opens chat, session history, dashboards, VNC, , and local web previews for each agent.
- The basic startup path is `npm run setup`, `npm start`, then `http://127.0.0.1:5180`.
- For LAN access, Fleet expects an access token; for local-only use, bind it to `127.0.0.1`.