mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-06-15 09:21:36 +00:00
fa2aba90b4
The Multi-profile section never explained how to reach more than one profile from outside the container, and distinguishes the two surfaces that people conflate: - Hermes Desktop's Remote Gateway connects to a `hermes dashboard` backend (port 9119), and a single dashboard serves every co-located profile via its profile switcher (the target profile is sent per request; the backend opens that profile's HERMES_HOME). No per-profile port or second connection is needed for Desktop. - OpenAI-compatible API clients (Open WebUI, LobeChat, /v1) talk to each profile's API server, which binds 8642 for every profile with no auto-allocation. Reaching a second profile from such a client needs a distinct `API_SERVER_PORT` in that profile's own `.env` (and the port must NOT go in the container-wide `environment:` block, or every profile collides on it). Adds the create -> set port -> restart flow, the bridge port-publishing note, and clarifies the default profile's connection is untouched. |
||
|---|---|---|
| .. | ||
| features | ||
| messaging | ||
| secrets | ||
| skills | ||
| _category_.json | ||
| checkpoints-and-rollback.md | ||
| cli.md | ||
| configuration.md | ||
| configuring-models.md | ||
| desktop.md | ||
| docker.md | ||
| git-worktrees.md | ||
| multi-profile-gateways.md | ||
| profile-distributions.md | ||
| profiles.md | ||
| security.md | ||
| sessions.md | ||
| tui.md | ||
| windows-native.md | ||
| windows-wsl-quickstart.md | ||