Using Profiles to Separate Rocky Work Contexts

Hermes profiles let different agent environments keep separate configuration, memory, skills, plugins, and sessions. For Rocky, profiles are useful when one context should not inherit another context’s assumptions or credentials.

When profiles help

• Separate personal experiments from production operations.
• Keep client-specific workflows isolated.
• Run a locked-down profile for scheduled/public publishing jobs.
• Test new model or tool configurations without changing the default environment.

What belongs in a profile

• Model/provider configuration.
• Enabled toolsets.
• Gateway or platform settings.
• Profile-specific skills and memories.
• Session history for that context.

Use the current official docs for commands and behavior: https://hermes-agent.nousresearch.com/docs/user-guide/profiles

Boundary checklist

• Do not modify another profile’s skills, plugins, cron jobs, or memories unless that is the explicit task.
• Keep public-site jobs scoped to public assets.
• Avoid cross-profile assumptions about credentials or tool availability.
• Label profiles by purpose, not by vague status names.

Pitfalls

• Debugging the wrong profile.
• Saving a workflow lesson as memory when it should be a reusable skill.
• Copying secrets between profiles manually.
• Assuming a tool enabled in one profile is available in another.

Verification steps

• Check the active profile before changing configuration.
• Inspect the profile path when editing profile-owned files.
• Confirm the intended toolsets are available in a fresh session.
• For scheduled jobs, verify delivery and logs under the correct profile.