hermes - 💡(How to fix) Fix [Feature]: Multi-User Team Mode — Centralized Agent Management

Problem or Use Case

Right now Hermes is a fantastic single-user agent. But for small businesses and teams, there's no way to centralize agent management.

Our situation:

• Only two people on staff can build and maintain agents (outside of frontier lab harnesses)
• Other team members build small agentic workflows on their own machines
• When something breaks, we can't see what happened — no centralized logs, no shared visibility
• Troubleshooting means getting on a call and screen-sharing
• No clean way to build a specific agent for a specific business use case and hand it to a team member to use

We looked at deploying Hermes on Railway and connecting via the Desktop App's remote backend. It almost works, but everything is shared — one set of memory, sessions, no separation between users. No "builder" vs. "user" roles.

Proposed Solution

What Would Make This Work

A lightweight multi-user layer. Not a full enterprise platform — just enough for a small team (5-15 people):

1. User accounts with separate sessions and memory — multiple people connect to the same backend, each gets their own history
2. Shared agent templates — a builder creates an agent (skills, personality, tools, model) for a use case, team members select and use it without configuring anything
3. Centralized visibility — admins can see all sessions across users, check what broke without being on someone's machine
4. Role separation — Admin/Builder creates agents and sees everything. User picks an agent and uses it.

Nice-to-haves: per-user usage limits, session sharing for troubleshooting, per-agent tool permissions, SSO or invite-link onboarding.

Why This Matters

Plenty of tools let you build your own agent. Almost zero let a small business deploy and manage purpose-built agents across a team without everyone becoming a power user. Hermes has the best agent core we've found. The missing piece is the team layer.

Alternatives Considered

We have built this internally. However, Hermes is a superior self-evolving system that we've tested individually.

We've also been asked to implement our solution into other businesses. We've been resistant to do so because of the intimate knowledge one must have to know how to fix the system.

Feature Type

New tool

Scope

None

Contribution

• I'd like to implement this myself and submit a PR

Debug Report (optional)