Files
ansible/roles/mac/README.md
T
PhilandClaude Opus 5.5 bad2426896 Mac: automatic login for phil
The Mac powers back on after a power cut but stopped at the login window,
so nothing that needs a login session (dashboard, Podman VM for Hermes's
sandbox, BlueBubbles, Beeper) came back. Turn on automatic login with
sysadminctl, using phil's password from the vault. FileVault is off, so it
works unattended. User accepted the physical-access trade-off.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 07:34:26 -07:00

3.4 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), checked with hermes config get 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 and voice-note transcription. Leave agent.reasoning_effort out: config set refuses it without --force (hermes-agent #140221).
  • 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.
  • 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; redeploy after changing it.

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.