Up And Running with Hermes Agent
Setting up Hermes Agent for multiple users and teams depends on whether you want a shared workspace (a single agent assisting a team via a messaging app) or a multi-agent system (specialized agents routing tasks amongst themselves).
[77cvca]
[0wm01r]
Option 1: Set Up a Shared Team Assistant (Messaging App)
To allow multiple people to interact with a single agent, connect Hermes to a messaging platform with access control.
[77cvca]
Option 2: Set Up Multiple Specialized Agents (Multi-Agent Fleet)
To create different AI agents that serve different teams (e.g., a coding agent for engineering, a research agent for marketing), use Hermes' profile management.
[0wm01r]
[0zlboh]
- Clone profiles: Use the --clone flag to create unique profiles for each specialist, ensuring each has its own memory and configuration.
hermes profile create marketing-agent --clone
hermes profile create engineering-agent --clone
- Assign specific models & skills: Customize the config.yaml and SOUL.md file for each profile to give them specialized roles.
- Run concurrent gateways: If multiple agents need to be online simultaneously (e.g., one agent per family member or one per Slack channel), start different profiles on isolated gateways using hermes profile install and configure independent messaging connections for each. [5qabl6] [0zlboh] [hsed5i] [7fdbvs] [n3tsai]
Option 3: Coordinate a Multi-Agent Team (Collaboration & Routing)
To build a true collaborative workflow where an orchestrator assigns work to worker agents:
- Use the Kanban board: Hermes supports a UI, allowing different agent profiles to route work and collaborate on tasks.
Yes, you start by SSHing in, but because Hostinger runs Hermes Agent inside isolated Docker containers, there are specific extra steps required to get full developer access. Depending on whether you want to use the command line, code remotely, or build apps on top of it, developer access is split into three methods:
[0y8ae1]
[j7du9a]
1. The Core SSH CLI Access (To Modify Files & Run Commands)
When deploying through Hostinger's 1-click template, the agent is containerized. Standard SSH only gets you to the host server, not inside Hermes.
[j7du9a]
[smz2eb]
- SSH into the Hostinger VPS as root:
ssh root@your_vps_ip
- Locate your Hermes container directory. Hostinger appends a unique 4-character suffix to the project folder:
cd /docker/hermes-agent-*
- Execute into the running Docker container to access the Hermes development environment directly:
docker compose exec hermes /bin/bash
From here, you have full developer CLI access to tweak your SOUL.md prompt files, configure multi-agent profiles, or run manual skill-testing sessions via the hermes interactive loop.
[j7du9a]
[t810x5]
[leo88o]
[o8axv9]
2. Browser Dashboard Access (The Visual Admin UI)
Hermes Agent includes a Browser-Based Admin Panel to visually track variables, execution chains, and jobs.
[0y8ae1]
[leo88o]
- The Problem: Hostinger secures these containers behind a firewall.
- The Developer Solution: Keep ports closed to the public internet and use an SSH Tunnel to safely map the remote UI port to your local computer.
ssh -L 8080:localhost root@your_vps_ip
Once run, leave that terminal open and open http://localhost:8080 in your computer’s browser to safely manage your system. (For a permanent connection without keeping a terminal open, developers typically install Tailscale on the VPS).
[0y8ae1]
[leo88o]
[fst3e4]
[u6qtvp]
3. Programmatic API Access (To Connect Your Own Apps)
If you are developing a custom frontend or wanting to trigger Hermes via your own scripts, you can utilize the built-in Hermes API Server.
[j7bypm]
[hk9t3p]
- Inside the container config, define your custom secret key:
bash
hermes config set api_server.enabled true
hermes config set api_server.key your_dev_secret_token- You can then interact with the agent programmatically from any external development app by passing a standard Bearer authentication header:
Authorization: Bearer your_dev_secret_token