How-To Series · Episode 10 / 59 · Module 2: Daily Driver

Hermes · Profiles

Multiple independent agents on one machine. Each its own brain, keys, and memory.

After this videoYou can now run a fleet of agents on one box · cleanly separated.

A profile is a separate HERMES_HOME. hermes profile create coder builds it and drops a coder command alias on your PATH — every Hermes subcommand works as coder <subcommand>. Three create modes (blank, --clone config-only, --clone-all full snapshot). Three targeting modes (alias, -p flag, sticky hermes profile use). Each profile gets its own gateway service and its own bot tokens, with duplicate-token detection. Profiles are not a sandbox — set terminal.cwd explicitly if you need a project pin.

About these resources. Every command in this video comes from the single Profiles user-guide doc. The Profile Distributions doc is referenced as further reading for sharing an agent across machines.

Sources · What this video distills

1 docs page · every command below traces to it
Primary · create variants, command aliases, -p, sticky default, per-profile gateways, the sandbox clarification
Profiles · Running Multiple Agents
Read ↗

Commands shown · Copy and paste

each shows the source doc it came from
Create + setup + startfrom Profiles ↗
hermes profile create coder && coder setup && coder chat
Config-only clonefrom Profiles ↗
hermes profile create work --clone
Full snapshot clonefrom Profiles ↗
hermes profile create backup --clone-all
Sticky default (like kubectl context)from Profiles ↗
hermes profile use coder
Per-profile gateway servicefrom Profiles ↗
coder gateway install
Pin a profile to a project folderfrom Profiles ↗
coder config set terminal.cwd /absolute/path/to/project

Going deeper · Related Hermes docs

further reading · not sources of facts shown above

Next in the series · Episodes that build on this

E13
SOUL.md · Give It a Personality
E16
AGENTS.md · Project Brain
E24
Hermes on Telegram