Skip to main content
Hermes Agent is Nous Research’s open-source autonomous AI agent. Unlike a session-based chat tool, it runs as a persistent daemon: it keeps memory across sessions, runs scheduled tasks, and writes its own reusable skills from experience. You drive it from a web dashboard at your *.suji.fr address. Hermes is an orchestrator: it calls out to an LLM provider you choose (Anthropic, OpenAI, or OpenRouter) rather than running model weights locally, so it runs fine on a normal CPU VM. You bring your own model key. This page covers running Hermes on Suji end-to-end. Hermes is maintained upstream; Suji provides the marketplace packaging.
The Hermes workspace can approve and run shell commands. Suji always protects the dashboard with a mandatory sign-in (username + password are required at install), but choose a strong password and treat access like root on the VM.

​
Before you install

You need an API key for one model provider: Have the key ready for the install form.

​
Install

Dashboard → Apps → Hermes Agent → Install: Click Deploy. When the install is running, the dashboard is live at https://hermes-<random>.suji.fr over HTTPS through the tunnel.

​
First connection

  1. Open the install URL (https://hermes-<random>.suji.fr).
  2. You’re taken to a Hermes sign-in page: enter the dashboard username and password you set at install.
  3. You land in the Hermes workspace. Start a chat, set up cron tasks, or connect a messaging channel.
The provider key you supplied is already wired in, so the agent can reason immediately, no extra setup to start chatting.

​
What you can do with it

  • Persistent memory: Hermes remembers context across sessions, unlike a stateless chat.
  • Scheduled tasks: give it recurring jobs (cron) that run unattended.
  • Self-written skills: it turns successful workflows into reusable skills.
  • Messaging channels: connect Telegram, Discord, and other platforms so you can talk to it outside the dashboard. Configure these from the workspace after install.

​
Switching or adding a model provider

Hermes auto-detects the provider from whichever key is set. To change it, go to the install detail page → Edit Install, change Model provider and supply that provider’s key, then redeploy. You can also fine-tune model selection and add provider keys from inside the workspace settings.

​
Day-to-day management

Hermes ships frequently and upgrades can include breaking changes, so its upgrade policy is breaking-changes-flagged: the dashboard asks you to acknowledge before upgrading rather than applying silently.

​
Troubleshooting

Use the Dashboard username and password you set at install (username defaults to admin). Forgot the password? Set a new one via Edit Install → redeploy.
Check the API key for your chosen provider is valid and has credit, then look at the Logs tab. You can re-enter the key via Edit Install.
Hermes runs a 4 GB container plus bundled Chromium, so it needs a Medium (8 GB) VM for headroom. Move it to Medium or larger if it’s being OOM-killed.
The dashboard isn’t up through the tunnel yet, usually still starting (wait ~30–60 s). If it persists, the Logs tab shows why the container isn’t running.

​
Where things live

Uninstalling deletes the volume by default. That’s all the agent’s memory and skills. Choose keep data during uninstall to preserve it.
  • Medium (8 GB) or larger. Hermes runs with a 4 GB container limit and bundles Chromium for browser automation; an 8 GB VM gives the OS the headroom a 4 GB VM lacks.
  • The agent itself is light (it offloads reasoning to your LLM provider). Sizing is about the tools it runs, not the model.

​
Reporting issues