Hermes Agent that keeps its memory, with its dashboard behind a sign-in
Run Hermes Agent on your own computer for free. Its web dashboard needs a username and password that Badgr generates, and its memory and workspace survive restarts.
On your computer: available
Free. Opens only on this computer, and the dashboard asks you to sign in.
On Badgr cloud: not available
Not available on Badgr cloud, because hosted apps have no storage that is kept and Hermes Agent must keep its memory and workspace.
Problems this handles
A dashboard anyone can open
The dashboard is bound to your own computer only and refuses to start without a username and password. Badgr generates a long random password and saves it in an owner-only file. It is never printed or written to logs.
Losing memory and settings on restart
Hermes keeps everything under one data folder, which Badgr stores in a named volume. Stop, start and remove keep it, and deleting it needs a separate confirmation.
Two copies fighting over one data folder
Only one local copy runs at a time, and Badgr checks that no other container already uses the saved data before it starts.
Slow installs and failed builds
Badgr runs a pinned, prebuilt image. Nothing is built or installed on your computer.
Try it
badgr login badgr launch hermes badgr apps stop <app-id> badgr apps start <app-id>
Local runs need Docker and no Badgr account. Cloud runs show the hourly rate and ask you to confirm before anything starts.
Good to know
- Local only.
- Hermes Agent needs a model provider key set up inside the app after you sign in.
- Badgr starts the dashboard. The agent's own behaviour is not changed or fixed by Badgr.
- Badgr runs the pinned version digest-pinned. It does not change the app itself, so bugs inside Hermes Agent itself are not fixed by Badgr.
- Source and licence: https://github.com/NousResearch/hermes-agent (MIT).