Multiple Profiles

19.4. Multiple Profiles — Many Profiles, Many “Personalities” in Parallel

Why you need multiple profiles

Each profile is its own HERMES_HOME — meaning a completely separate set of SOUL.md, MEMORY.md, skills, and model configuration. Use this when you need the agent to play several different roles: a personal bot, a bot serving your team, an agent dedicated to a specific project — each with its own personality, memory, and permissions, with nothing bleeding into the others.

Connections to earlier chapters

• Each profile has its own SOUL.md (mentioned in 7.1) — changing one bot’s personality never affects another bot.
• Each profile has its own MEMORY.md/USER.md memory (20.1) — the team-serving bot does not “know” personal things from your private bot.
• You can put them on the same VPS (chapter 1) or on entirely different servers, depending on the isolation level you want.

Notes

• Do not share one profile for both personal use and sensitive work — separate profiles are the cheapest way to keep clear boundaries between contexts, instead of relying on channel overrides (7.3), which only separate system prompts/models, not memory or skills.
• For each new profile, backups (1.6) also need to be separated per HERMES_HOME — do not bundle one backup schedule and then forget that multiple profiles are running in parallel.