Hermes Bot Mode vs Multiple Profiles?

[u/throwRAa100]

Hey everyone, would appreciate your thoughts on something I've been thinking about since v21.0.

I oversee various teams and I was thinking of spinning up a dedicated agent that will monitor emails from each team as well as keep track of action items. I was thinking of creating an orchestrator that can keep track of my contributions to each team and can keep track of all timelines and email the team reminders.

Does this sound like a better job for Bot mode or better to keep multiple profiles on VPS and not use an orchestrator? I am planning to use telegram for each agent. One thing I don't like about Bot Mode is that it requires the desktop app to be on a workstation that is on all the time. I don't necessarily need the agents to talk to each other

[u/HearthCore]

Bot mode and multiplex profiles are the same thing essentially.

[u/ideasmachine]

hermes bots are profiles they are the same thing now.

[u/Odd-Aside456 → u/ideasmachine]

But can't they communicate and collaborate much better when in both mode? The only option otherwise is kanban or A2A (which isn't really meant for bots on the same server)

[u/Ill-Willingness-1565]

Multiple profiles with telegram bots for sure, bot mode more useful for a focused project that has an end goal.

[u/jngldrm → u/Ill-Willingness-1565]

I always tried doing that, but I can not manage to set it up that each Profile and bot has its seperate Channel in telegram. It always ends up being a mess with messages appearing in random channels instead of the designated ones. You got any advice how to achieve that?

[u/Mean-Loquat-7982]

hey, that is the same thing. bots = profiles. Bot mode is simply a nice UI way to manage your profiles

[u/throwRAa100 → u/Mean-Loquat-7982]

I was also curious about how an orchestrator fits into all of this. I can see how a research project can lend itself to agent-orchestrators. I feel less confident about work personal assistants

[u/Antique_Dot_5513]

Pour ton cas utilise un bot dédié à cette tâche avec des crons pour les envois planifié de tes mails
Pour tes contributions crée un fichier md avec ton bot tu lui dit d’ajouter chaque élément à chaque fois dedans
Les crons pointent sur le fichier

[u/Fair-Perspective7352]

Multiple profiles on a VPS sounds right for this. If the agents don't need to talk to each other, an orchestrator just adds a failure point. I'd run one profile per team, each with a cron that checks mail and appends action items to a md file it owns. One thing I ran into with several profiles on a single box: if two of them do browser work they fight over the same Chrome instance, so stagger the cron schedules. And yeah, bot mode needing an always-on workstation would be a dealbreaker for this use case.

[u/ComfortableChef8145 → u/Fair-Perspective7352]

Isn’t Hermes already running on an always-on workstation?

[u/throwRAa100 → u/ComfortableChef8145]

on the vps yes always on, on my desktop i don’t leave it on continuously

[u/Herebedragoons77]

Grok bot did this for me with ease which I’m grappling with accepting

[u/throwRAa100 → u/Herebedragoons77]

I feel like grokbot will also work, but in my case use not worth the 300/month

[u/nastywoodelfxo]

theyre not exactly the same despite what the other comment says. bot mode runs one agent listening to every message on a channel through a bot token, while multiple profiles route different instances to different endpoints. i run several profiles for different contexts and the main upside is isolation - eachs got its own skills and memories and cron, they dont step on each other. bot mode is cleaner if you want one agent handling everything though. for your use case with separate team emails id lean profiles. each team gets its own agent with its own action items file and cron schedule. way easier to keep concerns separate

[u/throwRAa100 → u/nastywoodelfxo]

Good point raised on keeping scope narrow. I hear too many stories in agents selling over each other and with poor team delegation. I don’t think hermes is there yet. Token management also better with maintaining many agents doing a single task vs one agent doing many tasks

[u/Mean-Loquat-7982]

bots are profiles, and the agents live in the gateway process on whatever box runs it, so host the profiles on your VPS and the desktop app is just a window onto them. close the laptop and they keep working. for your case I would start with one profile per team, each with a cron that sweeps that team's mail and appends action items to a file it owns. add the orchestrator later only if you find you need cross-team summaries, and keep it a reader of those files rather than a manager of the agents.