- 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
1.6 KiB
title, type, status, created, updated, review_after, verified_on, confidence, tags, sources
| title | type | status | created | updated | review_after | verified_on | confidence | tags | sources | |||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Persistent shell enabled | decision | active | 2026-07-22 | 2026-11-11 | 2026-10-20 | 2026-11-11 | high |
|
Persistent shell enabled
Decision
Enable persistent shells for Hermes.
Reasons
- Preserve terminal state across turns
- Avoid re-activating virtualenvs and aliases every call
Alternatives considered
- Always transient shell
- Manual re-activation by user
Revisit when
Use case becomes critical again.
Re-verified 2026-10-20 — decision still
activeand the setting is stilltrue.terminal.persistent_shell: truein~/.hermes/config.yaml,backend: local,timeout: 180,home_mode: auto,container_cpu: 1,lifetime_seconds: 300. Thereview_after: 0001-01-01value was a zero-date bug (same class as decisions/keep-openrouter-as-fallback); it is now a real date. One caveat worth carrying into the review:lifetime_seconds: 300means a persistent shell is torn down after 5 minutes idle, so "state persists across turns" is true within a burst of work but not indefinitely. See concepts/persistent-shells.
Re-verified 2026-11-11 — decision still
active, setting stilltrue.terminal.persistent_shell: true,backend: local,timeout: 180,home_mode: auto,container_cpu: 1,lifetime_seconds: 300,cwd: /home/hermes/workspace/. The 5-minute idle teardown caveat recorded on 2026-10-20 still applies: state persists across a burst of work, not indefinitely.