看来自己部署是主流啊。现在还有一个 Hermes Workspace 的前端UI,类似官方的对接,功能很多。我在Github上看了一下安装,好像要进行SSH对docker进行部署拉取,复制在下面看大家看看能不能成功:
The Docker setup runs both the Hermes Agent gateway and Hermes Workspace together. Prerequisites
- Docker
- Docker Compose
- Anthropic API Key — Get one here (required for the agent gateway)
Step 1: Configure Environment
git clone https://github.com/outsourc-e/hermes-workspace.git
cd hermes-workspace
cp .env.example .env
Edit .env and add at least one LLM provider key — whichever provider you want hermes-agent to use: # Pick one (or more). You do NOT need all of these.
# ANTHROPIC_API_KEY=*** # Anthropic
# OPENAI_API_KEY=sk-... # GPT / o-series
# OPENROUTER_API_KEY=sk-or-v1-... # OpenRouter (free models available)
# GOOGLE_API_KEY=AIza... # Gemini
Using Ollama, LM Studio, or another local server? No key needed — just point hermes-agent at your local endpoint via the onboarding flow. Heads up: hermes-agent needs to be able to reach some model. If you don't configure any provider (API key or local server), chat will fail on first message.
Step 2: Start the Services
docker compose up
This pulls two pre-built images and starts them: - hermes-agent → nousresearch/hermes-agent:latest on port 8642
- hermes-workspace → ghcr.io/outsourc-e/hermes-workspace:latest on port 3000
No local build. First run takes a minute to pull; subsequent starts are instant. Agent state (config, sessions, skills, memory, credentials) persists in the legacy-named claude-data Docker volume, so containers can be recreated without data loss.
Step 3: Access the Workspace
Open http://localhost:3000 and complete the onboarding. Verify: Check the Docker logs for [gateway] Connected to Hermes Agent — this confirms the workspace successfully connected to the agent.
Building from source
Want to hack on the workspace and have local changes hot-built into the container? Use the dev overlay: docker compose -f docker-compose.yml -f docker-compose.dev.yml up --build
The base docker-compose.yml stays untouched — the overlay adds a build: block for the hermes-workspace service so the local repo is compiled instead of pulled. The Hermes Agent service still uses the canonical nousresearch/hermes-agent:latest image; if you need a custom agent build, tag it locally and override image: in your own compose.override.yml.
Using a Pre-Built Image (Coolify / Easypanel / Dokploy / Unraid)
Deploying Hermes Workspace to a PaaS or home-lab stack? Pull the image directly from GitHub Container Registry: ghcr.io/outsourc-e/hermes-workspace:latest
Available tags: [td]| Tag | What it is | | latest | Latest main commit (stable; recommended) | | v2.0.0 | Pinned semver tag | | main-<sha> | Specific commit |
Minimal Coolify / Easypanel config: service: hermes-workspace
image: ghcr.io/outsourc-e/hermes-workspace:latest
port: 3000
env:
HERMES_API_URL: http://hermes-agent:8642 # point at your gateway
HERMES_API_TOKEN: ${API_SERVER_KEY} # if gateway auth is enabled
The image is built for linux/amd64 and linux/arm64. Pair it with either a nousresearch/hermes-agent:latest container (what our docker-compose.yml does by default) or an existing gateway on another host.
|