Profiles for Client and Worker Isolation

Profiles help Rocky keep separate worlds separate. That matters when one setup is for personal work, another is for a client, and a third is for an autonomous worker.

Official Hermes Agent docs: https://hermes-agent.nousresearch.com/docs/user-guide/profiles

Isolation model

• Each profile can have its own config, skills, plugins, cron jobs, and memories.
• Use profiles when credentials, delivery channels, or standing instructions should not mix.
• Do not modify another profile’s durable state unless the user explicitly directs it.
• Use clear profile names that describe the operating context.
• For workers, keep the tool and delivery set narrower than an owner profile.

Client-safe checklist

• Confirm which profile is active before configuration changes.
• Keep client-specific memory out of a public or default profile unless it is genuinely reusable.
• Separate preview/build work from production notification channels.
• Avoid using one profile’s skills as authority for another profile without review.
• Document handoff commands in public-safe language.

Pitfalls

• Assuming a tool is enabled in every profile.
• Writing cron jobs or plugins into the wrong profile.
• Mixing client secrets with general operator memory.
• Using worker profiles with broad write access when read-only review is enough.

Verification steps

• Run the documented profile command when profile scope matters.
• Check the active profile before editing durable files.
• Verify the destination channel for any automated delivery.
• Report profile assumptions in the handoff summary.