Files
ansible/roles/mac/README.md
T
PhilandClaude Opus 5.5 2376f4284c 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>
2026-11-11 15:18:12 -07:00

5.5 KiB

mac

Manages cogitator-02, an Apple Silicon Mac on the tailnet (mac.yml, PLAYBOOK=mac.yml bin/deploy).

  • Homebrew (tag homebrew): taps, formulae and casks listed in group_vars/mac/main.yml. Installs what's missing; never upgrades or removes.
  • SSH key (tag ssh): your local ~/.ssh/id_ed25519.pub in phil's authorized_keys. Other keys there are left alone.
  • Power (tag power): mac_pmset in group_vars/mac/main.yml: never sleep, power back on after a power cut, wake on network.
  • Firewall (tag firewall): macOS's application firewall on, with signed software allowed automatically (SSH, BlueBubbles, AirPlay, Tailscale), no stealth mode and no block-all. Any unsigned program that needs incoming connections has to be allowed explicitly, or the firewall silently blocks it. (Nothing needs that today.)
  • Hermes dashboard (tag hermes-dashboard): a launchd service (local.hermes-dashboard) running hermes dashboard on 127.0.0.1:9119, and Tailscale Serve publishing it at https://cogitator-02.porgy-porgy.ts.net, reachable from the tailnet only. Login is username admin with the password hash and signing secret from vault_cogitator02, written into ~/.hermes/.env (a plaintext password line there is removed, since it would override the hash). After setting up Serve, the play checks the dashboard demands a login through it; if not, it turns Serve off and fails.
  • Hermes settings (tag hermes-settings): the individual keys in hermes_settings (group_vars/mac/main.yml), compared against ~/.hermes/config.yaml and fixed with hermes config set; any change restarts the gateway (hermes gateway restart) and the dashboard. Covers update backups, timezone, not borrowing Claude Code's login, sandbox memory, disabled toolsets, skill-write approval, deny rules, streaming, voice-note transcription, and models: chat on GPT-6.1 Sol, short side tasks (approval, titles) on Claude Haiku 5.5, longer ones and cron on GLM-5.3 Flash, subagents on DeepSeek V4.1 Flash, /model aliases. The approval guardian also gets extra_body.reasoning: {effort: none}, 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 (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 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 (from the vault) and written to ~/.hermes/.env. Today: Karakeep, with only search/read/create/tag tools registered, and Kagi's hosted server for web search and page fetching (Hermes's built-in web toolset is off).
  • Podman VM (tag podman): a launchd job (local.podman-machine) that starts the VM running Hermes's sandbox at login, and podman_machine_memory for its size. A resize stops the VM and starts it again through that job. The job needs AbandonProcessGroup, or launchd kills the VM as soon as podman machine start exits.
  • Hermes cron jobs (tag hermes-cron): hermes_cron_jobs in group_vars/mac/main.yml, with their scripts from files/hermes-scripts/ copied to ~/.hermes/scripts/. Missing jobs are created; existing ones are left as they are. Today: hermes-update-notice, which messages you on Telegram on Mondays only when a new stable Hermes release is out, and hermes-model-review, a monthly GPT-6.1 Sol research run that recommends model changes (as Ansible keys) based on the Hermes Index, OpenRouter rankings and prices, and your usage.
  • Automatic login (tag autologin): phil is logged in automatically after a reboot, so everything that needs a login session (dashboard, Podman VM, BlueBubbles, Beeper) comes back after a power cut. Uses phil's password from the vault; after changing it, sudo rm /etc/kcpassword on the Mac and redeploy. Setting it needs phil logged in at the console: sysadminctl only works inside that session (launchctl asuser).

Ansible logs in as phil. sudo needs phil's password, which is in the vault as vault_cogitator02.become_password; only tasks with become: true use it. phil deliberately doesn't get passwordless sudo, because Hermes Agent runs as phil and takes commands over Telegram.

Not managed here: Hermes Agent itself (~/.hermes, a self-updating git install on the stable channel, launchd agent ai.hermes.gateway), its other settings, and the Tailscale app.