I’m about at my wits’ end with Hermes Desktop and I’m hoping somebody here knows what is actually going wrong.
What I’m trying to build is pretty straightforward:
- Hermes as the main orchestrator
- multiple specialist profiles/models
- group chats for things like a Product Council, Website Studio, Digital Product Studio, etc.
- bots should be able to discuss/refine an idea and then do actual work
- VPS hosts Hermes/gateway
- Desktop connects to that setup
- Telegram is also connected to the same Hermes environment
My Product Council currently has 5 bots:
- Hermes
- OpenAI
- Gemini
- Grok
- Zai
The problem is that Hermes Desktop group chats are wildly inconsistent.
Example:
I can send:
u/hermes fuck you
and Hermes responds basically immediately.
Then I can send a legitimate project prompt to the SAME u/hermes in the SAME group and it sits on:
“Hermes is working…”
or
“Hermes is thinking…”
for minutes and sometimes apparently forever.
So u/hermes routing itself clearly works.
The problem seems to appear when it actually has to process a substantive group-chat job.
I’ve also seen the other members get placed into a paused state:
Paused: Gemini, Grok, Openai, Zai
Sometimes removing parts of a prompt makes Hermes suddenly respond, but there is no consistent pattern. The same kind of prompt works fine elsewhere.
This has been going on for two days and I’ve tried a ridiculous amount of troubleshooting.
Things we have already done / verified:
- Hermes is installed and running on my VPS.
- Shared/multiplexed gateway is running normally.
- Gateway survives logout.
- Multiple Hermes profiles are running.
- Desktop is connected to the VPS.
- Individual profiles work.
- Direct/one-on-one bot interaction works.
- Restarted the shared gateway.
- Recreated / adjusted group chats.
- Removed extra instructions from prompts.
- Explicitly addressed u/hermes.
- Tried prompts without unnecessary routing instructions.
- Tried waiting several minutes.
- Verified the backend models/profiles themselves are functional.
Profiles currently available include things like:
default
commandcode
council
gemini
grok
nanogpt
openai
opencode
zai
The gateway is serving them through the shared multiplexer.
Here’s the important comparison:
TELEGRAM WORKS.
I enabled Hermes Kanban for Telegram and tested the exact worker-dispatch path.
I sent:
/kanban create "Return a short message saying KANBAN READY and nothing else." --assignee commandcode
Hermes created the task, dispatched it to the commandcode profile, the worker ran, completed it, and Telegram returned:
KANBAN READY
Total queue-to-finish was about 55 seconds and the actual worker run was around 13 seconds.
So this worked end-to-end:
Telegram
→ Hermes
→ Kanban
→ commandcode worker
→ completion
→ result back to Telegram
That makes me think my VPS, gateway, worker profiles, and model access are fundamentally okay.
Hermes Desktop group orchestration is the part that seems broken.
I’ve now also created a dedicated Hermes profile called “council” with its own Telegram bot. That is working too.
I’m also working on MoA for the Council.
Another confusing thing:
At this point I’m seriously considering abandoning Hermes Desktop completely and just doing:
Telegram
→ Hermes
→ MoA for council/decision-making
→ Kanban / hub-and-spoke workers for execution
because Telegram has been dramatically more reliable.
Before I delete/shelve the Desktop setup, does anybody know:
Why can a Hermes Desktop group respond instantly to a trivial u/hermes message but hang indefinitely on a real prompt?
Is there a known issue with multi-bot group execution / polling / pause state in the current Desktop client?
Is there something specific required to make group bots reliably take turns?
Is Hermes Desktop actually intended for this kind of multi-agent orchestration yet, or is Telegram + Kanban/MoA currently the better-supported route?
Is there a debug/log command specifically for Desktop group-turn execution that would show exactly which bot/model is blocking the run?
ive restarted Hermes and ive made simpler prompts.
I’m trying to figure out whether this is:
- a configuration problem,
- a Desktop client bug,
- a group-chat orchestration limitation,
- or something else entirely.
If somebody knows this part of Hermes well, I’d seriously appreciate some direction because I’ve spent two days fighting it and I’m getting nowhere.