- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13) - skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299) - runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated - comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest - incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised - incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused) - 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists) - log.md addendum + index.md date bump; no page deleted, no secrets written
2.2 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Persistent Shells | concept | active | 2026-07-22 | 2026-11-11 | 2026-11-11 | high |
|
|
Persistent Shells
Idea
A background shell session that survives across separate Hermes turns/requests, instead of spawning and tearing down a fresh shell each time — so state (working directory, exported variables, long-running processes) carries over.
How this install implements it
- Verified (
~/.hermes/config.yaml):terminal.persistent_shell: true - Backend: local (not containerized separately from the agent process)
- Working directory:
/home/hermes/workspace - Timeout: 180s
- Home mode: auto
- Container CPU: 1
Full
terminal:block re-read 2026-10-20 — the above still holds, plus more. Live values:backend: local,persistent_shell: true,timeout: 180,home_mode: auto,container_cpu: 1,container_memory: 5120,container_disk: 51200,container_persistent: true,lifetime_seconds: 300,docker_mount_cwd_to_workspace: false,docker_run_as_host_user: true. The container-* keys are inert whilebackend: local— the shell is not containerised on this box, socontainer_memory/container_diskdescribe a path that isn't taken.
terminal:block re-read 2026-11-11 — unchanged.backend: local,persistent_shell: true,timeout: 180,home_mode: auto,container_cpu: 1,container_memory: 5120,container_disk: 51200,container_persistent: true,lifetime_seconds: 300,docker_mount_cwd_to_workspace: false,docker_run_as_host_user: true,cwd: /home/hermes/workspace/. The container-* keys are still inert whilebackend: local.
Why it matters here
Enables multi-step CLI workflows (e.g. a long git operation, a build, a watch process) to be resumed across turns without Hermes re-establishing context each time. The tradeoff is a shell can be left in a bad state (stuck process, wrong directory) that silently affects the next turn — see runbooks/troubleshoot-tool-loop for the related tool-loop guardrails that catch some of this.