Mac: Hermes sandbox keeps its container and finds Chromium

Podman reports the sandbox image as docker.io/nousresearch/...; Hermes
compares image names as text, so the short name made it delete and
recreate the sandbox on every reuse. Use the full name.

Hermes 0.23.1 looks for Chromium in chrome-linux/, but the ARM64 image
ships chrome-linux-arm64/ (hermes-agent #153626), so browser tools said
there was no Chromium. Mount a folder with a chrome-linux/chrome script
that runs the image's Chromium. Tested in a fresh sandbox: the probe
finds it and browser_exec loads pages.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
PhilandClaude Opus 5.5 committed 2026-11-11 15:18:12 -07:00
1 parent 20258e04f8
commit 2376f4284c
4 files changed
+39 -2

No files matched your search

+9 -2
View File
@@ -40,8 +40,15 @@ Manages cogitator-02, an Apple Silicon Mac on the tailnet (`mac.yml`,
Hermes has no command for it. Cua's skill pack is read through
`skills.external_dirs`, and the `cua-driver` symlink in `~/.hermes/skills`
is removed (a symlink there empties running sandboxes' skills,
hermes-agent #53630). After changing `terminal.cwd`, remove the old
`hermes-*` Podman containers: running ones keep their old mounts.
hermes-agent #53630). After changing `terminal.cwd` or
`terminal.docker_volumes`, remove the old `hermes-*` Podman containers:
running ones keep their old mounts.
The sandbox image is set by its full name (`docker.io/…`): Podman reports
that form, and with the short name Hermes deleted the sandbox on every
reuse. For the browser, `~/.hermes/sandbox-chromium`
(`files/sandbox-chromium`) is mounted where Hermes looks for Chromium; its
`chrome-linux/chrome` script runs the ARM64 Chromium the image ships
(hermes-agent #153626). Remove the mount once Hermes finds it by itself.
- **MCP servers and secrets** (also tag `hermes-settings`): MCP servers are
`mcp_servers.<name>` entries in `hermes_settings`, each running in a
throwaway Podman container. Secrets they need are in `hermes_env_secrets`
@@ -0,0 +1,10 @@
#!/bin/sh
# Hermes 0.23.1 looks for Chromium in chrome-linux/; the ARM64 sandbox image
# ships it in chrome-linux-arm64/ (hermes-agent #153626). Mounted at
# /home/pn/.cache/ms-playwright, so this runs the image's own Chromium,
# whichever version it is.
for c in /opt/playwright/chromium-*/chrome-linux-arm64/chrome; do
exec "$c" "$@"
done
echo "no Chromium under /opt/playwright" >&2
exit 127
+9
View File
@@ -21,6 +21,15 @@
when: hermes_cua_skills_link.stat.islnk | default(false)
notify: [Restart Hermes gateway, Restart Hermes dashboard]
# Before the settings, so the folder exists when a sandbox mounts it.
# Changing the mount only affects new sandboxes: remove the hermes-*
# Podman containers to pick it up.
- name: Chromium launcher for the sandbox's browser
ansible.builtin.copy:
src: sandbox-chromium/
dest: "{{ hermes_sandbox_chromium }}/"
mode: preserve
# Secrets go in first, so servers and settings that reference them
# (${VAR}) find them when the gateway restarts.
- name: Secrets in Hermes's .env