1.2 KiB
1.2 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-10-20 | 2026-10-20 | 2026-10-20 | 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.