Profiles guides

How Hermes profiles separate projects, clients, credentials, memory, skills, and runtime settings for safer Rocky operations.

A practical guide to profile-safe paths in a verified Hermes/Rocky workflow.

How to use Hermes profiles to separate personal work, client work, experiments, production workflows, tools, skills, and memory.

How Hermes profiles help keep different Rocky work contexts, tools, memories, and credentials separated instead of blending every task together.

Use Hermes profiles to separate client work, worker agents, credentials, skills, memories, and delivery surfaces.

Package a reusable Hermes agent as a versioned Git repository while keeping installer secrets, memories, sessions, runtime databases, and local overrides private.

Keep several Hermes agents online with isolated credentials, sessions, memory, and services, or deliberately choose a single multiplexing gateway.

Give each Hermes profile a durable capability description so Kanban orchestration can route work by evidence instead of guessing from a profile name.

Create memorable profile wrapper commands and install shell completion without hiding which Hermes profile a command will use.

A safe method for refining Hermes identity while keeping project instructions, secrets, and profile-specific state in their proper boundaries.