Choosing the Right Hermes Profile Structure

Profiles let Hermes run with separate configuration, sessions, skills, and memory. They are useful when different work should not share context or settings.

When to create a profile

Create a separate profile when you need separation for:

• Client work
• Production versus experiments
• Personal versus business tasks
• Different model providers or budgets
• Different tool access policies
• Gateway bots with separate audiences

Common commands

hermes profile list
hermes profile create client-a
hermes profile show client-a
hermes --profile client-a

Recommended structures

Solo builder

default: personal and general work
prod: production automations
lab: experiments and risky testing

Small agency

default: internal operations
client-name: one profile per client
sales: lead and proposal workflows

Memory boundary

Do not rely on memory to separate sensitive client contexts. Use profiles, folders, credentials, and explicit source-of-truth inventories.

Verification

Before running a sensitive task, check the active profile and confirm the working directory. If a task belongs to another profile, start the right profile instead of mixing context.