Install Hermes Agent Locally — or Deploy Faster with FlyHermes
Install Hermes Agent locally, handle common brew/mac install searches, configure a provider, run hermes doctor, and choose FlyHermes when you want managed cloud instead.
Quick answer
Install Hermes Agent locally if you want the open-source self-hosted path: run the installer, reload PATH, configure one provider/API key, run hermes doctor, then verify one hermes chat -q smoke test. If you searched for brew install Hermes Agent because you just want the outcome, FlyHermes is the managed cloud alternative with API costs included and no VPS maintenance.
GSC shows install intent clustering around macOS and Homebrew-style searches such as “hermes agent brew,” “brew install hermes agent,” and “hermes agent install mac.” The practical answer is to give both paths clearly: install the open-source CLI if you want control, or use FlyHermes when setup friction is the problem.
Managed cloud · API costs included · Skill library · Cancel anytime
Before you start:
- ☑Linux, macOS, or WSL2
- ☑Git installed and available on PATH
- ☑One model route: Nous Portal login, OpenRouter/OpenAI/Anthropic API key, or a local provider such as Ollama
- ☑Terminal access to reload your shell profile after install
Steps
- 1
Choose local install or managed cloud
Use local Hermes if you want the open-source CLI and full control. Use FlyHermes if you want the cloud version running faster without VPS, Docker, provider-key, or dashboard maintenance.
- 2
Run the official installer
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
- 3
Reload your shell PATH
Run source ~/.zshrc or source ~/.bashrc, then verify with hermes --version. If you searched for brew install hermes agent, this installer path is the reliable route unless a maintained Homebrew formula exists.
- 4
Choose a model provider
Run hermes setup or hermes model and configure Nous Portal, OpenRouter, Anthropic, OpenAI, or a local provider.
- 5
Check config and health
Run hermes config path, hermes config env-path, and hermes doctor before adding integrations.
- 6
Run the first smoke test
Run hermes chat -q "Reply with one sentence confirming Hermes works."
- 7
Add one next layer
Only after the CLI works, add Docker, Telegram, Discord, cron, webhooks, Notion, or VPS hosting one at a time. If that sounds like ops work you do not want, switch to FlyHermes.
Pro Tips
- 💡Use hermes setup or hermes model instead of hand-editing config on the first run
- 💡Use hermes config path and hermes config env-path to confirm which profile Hermes is reading
- 💡Run hermes doctor before blaming Telegram, Docker, Notion, or cron
- 💡Search demand includes brew/mac install phrasing, but the safest public path is the official installer plus PATH reload
- 💡Keep provider keys in .env/config files, never in prompts or committed repositories
- 💡If setup feels too infrastructure-heavy, use FlyHermes as the managed cloud version instead of self-hosting
- 💡After the CLI smoke test passes, open the Hermes Agent dashboard / Web UI guide so teammates can monitor sessions without learning every terminal command
Troubleshooting
❌ hermes command not found after install
✅ Reload your shell with source ~/.zshrc or source ~/.bashrc, then run which hermes and hermes --version.
❌ Installer fails because git is missing
✅ Install git first with brew install git on macOS or sudo apt install git on Debian/Ubuntu, then rerun the installer.
❌ Provider/API key rejected on first run
✅ Run hermes config env-path and verify the active profile is reading the .env file where you placed the raw provider key or OAuth login.
❌ Gateway setup fails immediately
✅ Do not debug the gateway first. Run hermes doctor and one hermes chat -q smoke test locally, then return to hermes gateway setup.
FAQ
Can I install Hermes Agent with Homebrew?
The common search is “brew install hermes agent,” but the safest documented path is the official installer, then reloading PATH and running hermes --version. If a maintained Homebrew formula appears, verify it against the official NousResearch repository before using it.
When should I use FlyHermes instead of installing locally?
Use FlyHermes when you want the cloud Hermes outcome faster: managed setup, API costs included, skill-library workflows, dashboard access, and no VPS, Docker, gateway, or provider-key maintenance.
What should I test before adding integrations?
Run hermes doctor and one hermes chat -q smoke test before adding Telegram, Discord, Notion, GitHub, cron, Docker, or a VPS.
Related setup and cost guides
FlyHermes pricing comparison
Compare the managed cloud path against owning a self-hosted Hermes setup.
Hermes Agent GitHub repository
Verify the official NousResearch source before installing.
Hermes Web UI / dashboard
Add browser-based visibility after the CLI smoke test passes.
Deploy Hermes on a VPS
Use this when you want always-on self-hosting instead of FlyHermes cloud.
Notion integration
Connect workspace automation after the base Hermes install is healthy.
OpenClaw migration
Switch from OpenClaw to Hermes when that is your starting point.