Use case
I run several Hermes profiles — a Chief-of-Staff on the default profile plus a maverick (CMO) profile, with more "Chief" profiles planned — each with its own gateway (hermes -p <profile> gateway). I'd like to talk to each agent from a single Workspace instance: e.g. separate entries in the left sidebar (chat: Pacey, chat: Maverick) or a per-chat agent selector — rather than running one Workspace per profile.
Current limitation
Workspace is single-gateway (HERMES_API_URL → one gateway). Selecting a different profile re-points the whole instance, so there's no way to have a default chat and a maverick chat side-by-side, each routed to its own profile's gateway. Today the only robust multi-agent setup is one Workspace instance per profile (separate URLs/ports).
Already scoped in-repo
docs/multi-gateway-pool-spec.md (Status: "Design Document — PR Proposal") describes exactly this — a gateway pool (one gateway per active profile), a sessions aggregator, a global profile selector, and the composer routing to the active profile's gateway. This issue asks whether that can be prioritised / tracked.
Ask
- Is there a tracking issue or rough timeline for the multi-gateway pool?
- Happy to test against a real multi-profile deployment (
default + named profiles, each on its own gateway/port).
Related: #648 (display name/label for the default profile) pairs naturally with this — labelling each chat by agent name.
Env: hermes-workspace @ d04e1f3, hermes-agent v0.16.0, multiple profiles each with its own gateway.
Use case
I run several Hermes profiles — a Chief-of-Staff on the
defaultprofile plus amaverick(CMO) profile, with more "Chief" profiles planned — each with its own gateway (hermes -p <profile> gateway). I'd like to talk to each agent from a single Workspace instance: e.g. separate entries in the left sidebar (chat: Pacey,chat: Maverick) or a per-chat agent selector — rather than running one Workspace per profile.Current limitation
Workspace is single-gateway (
HERMES_API_URL→ one gateway). Selecting a different profile re-points the whole instance, so there's no way to have adefaultchat and amaverickchat side-by-side, each routed to its own profile's gateway. Today the only robust multi-agent setup is one Workspace instance per profile (separate URLs/ports).Already scoped in-repo
docs/multi-gateway-pool-spec.md(Status: "Design Document — PR Proposal") describes exactly this — a gateway pool (one gateway per active profile), a sessions aggregator, a global profile selector, and the composer routing to the active profile's gateway. This issue asks whether that can be prioritised / tracked.Ask
default+ named profiles, each on its own gateway/port).Related: #648 (display name/label for the default profile) pairs naturally with this — labelling each chat by agent name.
Env: hermes-workspace @
d04e1f3, hermes-agent v0.16.0, multiple profiles each with its own gateway.