Hermes can search and read bookmarks, create them, tag them and add them
to lists from Telegram. Per Karakeep's MCP README and Hermes's MCP docs:
- the official server image (pinned 0.34.1) runs in a throwaway Podman
container (`podman run -i --rm`), started on first use and stopped
after 10 idle minutes;
- only search/read/create/tag/add-to-list tools are registered (no update
or delete); trust: full because Karakeep doesn't mark its search tools
read-only;
- the API key is in the vault, written to ~/.hermes/.env via the new
hermes_env_secrets, and passed into the container by name.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
Non-interactively, `hermes config get` prints only the default for a key
that isn't in config.yaml, so an unset key can't be detected and the play
kept trying (and failing) to unset terminal.cwd. Set it to Hermes's own
default "." instead and drop the unset branch.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`hermes config get` writes "Config key not set" to stderr and Hermes's
default to stdout, so terminal.cwd: null looked set ("."), the play tried
to unset it again and `unset` failed on the missing key.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The VM resize in a92d4c1 worked but left the VM stopped: a VM started from
an Ansible task is stopped when the task ends. Nothing started the VM at
login either, so after a reboot Hermes's sandbox stayed down.
- launchd job local.podman-machine runs `podman machine start` at login;
the resize now starts the VM through it and waits until it's running.
- Hermes setting changes also restart the dashboard, which keeps its own
copy of the settings (it kept logging the old /workspace cwd).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Via hermes_settings (now compared structurally, with null = unset, and a
gateway restart on change):
- timezone America/Denver (was unset)
- auth.adopt_external_logins false: never borrow Claude Code's login
- terminal.cwd unset: stops the /workspace warnings (#140527)
- agent.disabled_toolsets [kanban]: unused, 25 KB of tool schema per call
- skills.write_approval true
- approvals.deny: force-push, curl|sh, dd to devices (docs' examples)
- streaming.enabled true, stt.local.model small
- terminal.container_memory 3072, inside a 4 GB Podman VM (was 2 GB VM
with a 5 GB container limit), set by a new podman task
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds a small hermes_settings map that Ansible checks with
`hermes config get` and fixes with `hermes config set`, leaving the rest
of config.yaml to Hermes (its updates migrate that file).
First setting: updates.pre_update_backup: full (was false), so every
`hermes update` zips ~/.hermes first. Rollback isn't supported once a new
version has written state.db, so the backup is the way back.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>