Problem
The default profile cannot be renamed (correctly blocked by Hermes: Cannot rename the default profile), but it also has no way to set a human-readable display name or label. In the Profiles section of the workspace UI, it always appears as default, which is not descriptive in multi-profile setups.
Use case
Users running multiple agent roles (e.g. CEO, CTO, CMO as separate Hermes profiles) want the workspace UI to reflect meaningful role names. Named profiles (under $HERMES_HOME/profiles/<name>/) can be renamed freely, but the root default profile is permanently labeled default.
Proposed solution
Support a description or display_name field for the default profile — either via:
config.yaml — add a display_name key that the Profiles UI reads as the label (falling back to default if unset), or
SOUL.md first line — parse the first heading of SOUL.md as the display name (already present in every profile dir)
This would not require renaming the profile or changing any s6/gateway internals — purely a UI label change.
Environment
ghcr.io/outsourc-e/hermes-workspace:latest
nousresearch/hermes-agent:latest
- Multi-profile setup: default (CEO) + named profiles (CTO, CMO)
Problem
The
defaultprofile cannot be renamed (correctly blocked by Hermes:Cannot rename the default profile), but it also has no way to set a human-readable display name or label. In the Profiles section of the workspace UI, it always appears asdefault, which is not descriptive in multi-profile setups.Use case
Users running multiple agent roles (e.g. CEO, CTO, CMO as separate Hermes profiles) want the workspace UI to reflect meaningful role names. Named profiles (under
$HERMES_HOME/profiles/<name>/) can be renamed freely, but the root default profile is permanently labeleddefault.Proposed solution
Support a
descriptionordisplay_namefield for the default profile — either via:config.yaml— add adisplay_namekey that the Profiles UI reads as the label (falling back todefaultif unset), orSOUL.mdfirst line — parse the first heading ofSOUL.mdas the display name (already present in every profile dir)This would not require renaming the profile or changing any s6/gateway internals — purely a UI label change.
Environment
ghcr.io/outsourc-e/hermes-workspace:latestnousresearch/hermes-agent:latest