Models, from the Nov 2026 review (Nous Hermes Index, OpenRouter data): - chat: openai/gpt-6.1-sol (user's pick), reasoning high (was ultra) - side tasks (compression, approval, titles, mcp, memory query rewrite, curator, mail monitor) and unpinned cron: z-ai/glm-5.3-flash - subagents: deepseek/deepseek-v4.1-flash - /model aliases: deepseek, haiku agent.reasoning_effort needs --force (hermes-agent #140221), so settings can list keys in hermes_settings_force. `config get` exits 1 for unset keys without a default; that now reads as unset, not a failure. hermes-model-review: monthly cron job on Sol (pinned, high effort, continuity) that redoes this research and sends keep/change recommendations as Ansible keys to Telegram. A script injects the live model setup and 30-day usage into its prompt. hermes_cron_jobs gains model/provider, reasoning_effort and continuity. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.9 KiB
3.9 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 ingroup_vars/mac/main.yml. Installs what's missing; never upgrades or removes. - SSH key (tag
ssh): your local~/.ssh/id_ed25519.pubin phil'sauthorized_keys. Other keys there are left alone. - Power (tag
power):mac_pmsetingroup_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) runninghermes dashboardon 127.0.0.1:9119, and Tailscale Serve publishing it athttps://cogitator-02.porgy-porgy.ts.net, reachable from the tailnet only. Login is usernameadminwith the password hash and signing secret fromvault_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 inhermes_settings(group_vars/mac/main.yml), checked withhermes config getand fixed withhermes 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, side tasks and cron on GLM-5.3 Flash, subagents on DeepSeek V4.1 Flash,/modelaliases. Keys inhermes_settings_forceare set with--force(Hermes readsagent.reasoning_effortbutconfig setrefuses it, hermes-agent #140221). - Podman VM (tag
podman): a launchd job (local.podman-machine) that starts the VM running Hermes's sandbox at login, andpodman_machine_memoryfor its size. A resize stops the VM and starts it again through that job. The job needsAbandonProcessGroup, or launchd kills the VM as soon aspodman machine startexits. - Hermes cron jobs (tag
hermes-cron):hermes_cron_jobsingroup_vars/mac/main.yml, with their scripts fromfiles/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, andhermes-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/kcpasswordon the Mac and redeploy. Setting it needs phil logged in at the console:sysadminctlonly 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.