Mac: Hermes sandbox sees only ~/hermes; Cua skills via external_dirs

terminal.cwd "." resolved against each process's working directory, so
the dashboard's sandbox mounted / (the whole disk, writable) and the
gateway's mounted ~/.hermes (including .env). Point it at ~/hermes.

The cua-driver symlink in ~/.hermes/skills made Hermes give each sandbox
a temp copy of the skills and delete the previous copy, emptying running
sandboxes' skills (hermes-agent #53630). Read Cua's pack through
skills.external_dirs and remove the symlink.

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

No files matched your search

+15 -4
View File
@@ -25,6 +25,9 @@ hermes_dashboard_port: 9119
hermes_dashboard_url: "https://{{ ansible_host }}"
hermes_dashboard_username: admin
# The one host folder Hermes's sandbox sees (mounted at /workspace).
hermes_workspace: "{{ ansible_user_dir }}/hermes"
# Individual Hermes settings, set with `hermes config set`. The rest of
# ~/.hermes/config.yaml stays Hermes's own (its updates migrate that file).
hermes_settings:
@@ -33,10 +36,12 @@ hermes_settings:
# Never borrow Claude Code's login: subscription use outside Anthropic's own
# apps breaks its terms, and refreshing it can break Claude Code's login.
auth.adopt_external_logins: false
# Hermes's default. /workspace (a container path) made the host log a
# warning every few seconds (hermes-agent #140527); with the docker backend
# a host cwd never becomes the container's working directory anyway.
terminal.cwd: .
# The host folder mounted into the sandbox at /workspace
# (terminal.docker_mount_cwd_to_workspace). "." meant each process's own
# working directory: / for the dashboard (the whole disk) and ~/.hermes for
# the gateway (its .env with the API keys). A container path such as
# /workspace made the host log a warning every few seconds (#140527).
terminal.cwd: "{{ hermes_workspace }}"
terminal.container_memory: 3072 # MB; must fit in the Podman VM (podman_machine_memory)
# kanban: multi-agent boards (unused here); its 14 tools were 25 KB of the
# 65 KB of tool definitions sent with every message.
@@ -44,6 +49,12 @@ hermes_settings:
# rate-limited). Search and page fetching go through Kagi's MCP server.
agent.disabled_toolsets: [kanban, web]
skills.write_approval: true # skills Hermes writes wait for your approval
# Cua's skill pack, read in place instead of through the symlink
# `cua-driver skills install` puts in ~/.hermes/skills (removed by the
# settings tasks). A symlink there makes Hermes give each sandbox a temp
# copy of the skills, and deleting the old copy empties running sandboxes'
# skills (hermes-agent #53630).
skills.external_dirs: ["~/.cua-driver/skills"]
# Never run these, even in the sandbox and even under /yolo (examples from
# Hermes's hardening guide). Case-insensitive globs over the whole command.
approvals.deny:
+8 -3
View File
@@ -34,9 +34,14 @@ Manages cogitator-02, an Apple Silicon Mac on the tailnet (`mac.yml`,
because Hermes drops its own "reasoning off" for Haiku 5.5 on OpenRouter.
Keys in `hermes_settings_force` are set with `--force` (Hermes reads
`agent.reasoning_effort` but `config set` refuses it, hermes-agent #140221).
Also creates `~/hermes`, the Bot Chat's folder (the Hermex app's default
bot). The session's saved folder was set once by hand; Hermes has no
command for it.
Also creates `~/hermes` (`hermes_workspace`), the only host folder the
sandbox sees (`terminal.cwd`, mounted at `/workspace`). The Hermex Bot
Chat's saved folder points there too; that was set once by hand, since
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.
- **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`
+19 -5
View File
@@ -1,12 +1,26 @@
# The Hermex app's Bot Chat works here: its session's saved folder is
# mounted into the sandbox at /workspace. Saved once with Hermes's
# update_session_cwd, since Hermes has no command for it.
- name: Bot Chat workspace folder
# terminal.cwd: the folder the sandbox gets at /workspace. The Hermex Bot
# Chat session's saved folder points here too (set once with Hermes's
# update_session_cwd, since Hermes has no command for it).
- name: Hermes workspace folder
ansible.builtin.file:
path: "{{ hermes_bot_workspace }}"
path: "{{ hermes_workspace }}"
state: directory
mode: "0755"
# Replaced by skills.external_dirs (see group_vars). Only a symlink is
# removed; a real folder of that name is left alone.
- name: Look for the cua-driver skills symlink
ansible.builtin.stat:
path: "{{ ansible_user_dir }}/.hermes/skills/cua-driver"
register: hermes_cua_skills_link
- name: Remove the cua-driver skills symlink
ansible.builtin.file:
path: "{{ ansible_user_dir }}/.hermes/skills/cua-driver"
state: absent
when: hermes_cua_skills_link.stat.islnk | default(false)
notify: [Restart Hermes gateway, Restart Hermes dashboard]
# Secrets go in first, so servers and settings that reference them
# (${VAR}) find them when the gateway restarts.
- name: Secrets in Hermes's .env
-1
View File
@@ -4,4 +4,3 @@ hermes_dashboard_label: local.hermes-dashboard
tailscale_cli: /Applications/Tailscale.app/Contents/MacOS/Tailscale
hermes_cli: "{{ ansible_user_dir }}/.local/bin/hermes"
podman_machine_label: local.podman-machine
hermes_bot_workspace: "{{ ansible_user_dir }}/hermes"