hermes - 💡(How to fix) Fix non-default profile gateway fails: /root/.ssh/config not found [1 pull requests]

Bug Description

When a non-default profile gateway (e.g. server-ops) starts via s6 supervision, SSH cannot find ~/.ssh/config because HOME is not properly set after s6-setuidgid hermes drops to the hermes user.

The run script is generated by _render_run_script in hermes_cli/service_manager.py (line ~622):

Current: lines.append(f"exec s6-setuidgid hermes hermes -p {shlex.quote(profile)} gateway run")

After fix: lines.append(f"exec s6-setuidgid hermes env HOME=/opt/data hermes -p {shlex.quote(profile)} gateway run")

Root Cause

s6-setuidgid hermes switches to the hermes user (uid=1000, home=/opt/data). However, when with-contenv is involved (the #!/command/with-contenv sh shebang), HOME can resolve to /root from the root-level environment before the UID switch. SSH client then expands ~ to /root, looks for /root/.ssh/config — which does not exist — and the kanban worker blocks.

Environment

• Container: nousresearch/hermes-agent:v2026.5.29.2
• Supervision: s6-overlay v3.2.3.0
• Affected profiles: any non-default profile with terminal toolset
• SSH config location: /opt/data/.ssh/config

Proposed Fix

Explicitly pass HOME=/opt/data inside the env command after the UID drop:

exec s6-setuidgid hermes env HOME=/opt/data hermes -p <profile> gateway run

Also fix the default profile variant: exec s6-setuidgid hermes env HOME=/opt/data hermes gateway run