multi-team-hermes-architecture

Configure isolated Hermes agent team deployments with PM2 or systemd.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill multi-team-hermes-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-team-hermes-architecture
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/archive/skills/multi-team-hermes-architecture
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill multi-team-hermes-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the operational chaos of running multiple Hermes agent teams on the same server by giving each team isolated profiles, state, credentials, and process management. It reduces context leakage, duplicate work, identity confusion, and deployment mistakes across teams.

Core Features & Use Cases

  • Profile isolation: Separate each agent’s HERMES_HOME so sessions, memory, skills, and runtime state do not collide.
  • Multi-number WhatsApp setup: Run distinct WhatsApp bridges per team or anchor agent with separate ports and session paths.
  • Process orchestration: Deploy agents through PM2 or systemd with startup, restart, logging, and hardening guidance.
  • Operational troubleshooting: Handle common pitfalls like token masking, memory contamination, path confusion, and timeout mismatches.
  • Use case: A team lead can provision a second Hermes team on the same server, connect one agent to WhatsApp, delegate work to Slack-only specialists, and keep the environments separated.

Quick Start

Ask for a step-by-step plan to create an isolated Hermes team with separate profiles, WhatsApp bridging, and systemd or PM2 deployment.

Frequently Asked Questions about multi-team-hermes-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multiple Hermes agent teams on the same server without context leakage?

Running multiple Hermes agent teams on one server requires isolating each team's HERMES_HOME directory so sessions, memory, skills, and runtime state do not collide or leak across environments.

How do I set up a multi-number WhatsApp bridge for separate agent profiles?

Setting up a multi-number WhatsApp bridge requires configuring separate profile directories and distinct bridge ports per agent team to ensure session paths and credentials remain fully isolated.

Should I use PM2 or systemd for Hermes production process orchestration?

Hermes production process orchestration supports both PM2 and systemd service setup, providing startup, restart, logging, and hardening guidance for managing isolated agent team runtimes.

How do I fix memory contamination and token masking issues when deploying multiple Hermes agents?

Troubleshooting memory contamination and token masking in multi-agent Hermes deployments involves verifying profile isolation, checking HERMES_HOME paths, and resolving timeout mismatches across team configurations.

Can I deploy a second Hermes team on the same server and delegate work to Slack-only specialists?

Deploying a second Hermes team on the same server allows connecting one agent to WhatsApp while delegating work to Slack-only specialists, keeping both environments fully separated.