39 lines
1.2 KiB
Markdown
39 lines
1.2 KiB
Markdown
---
|
|
title: Persistent shell enabled
|
|
type: decision
|
|
status: active
|
|
created: 2026-07-22
|
|
updated: 2026-10-20
|
|
review_after: 2026-10-20
|
|
verified_on: 2026-10-20
|
|
confidence: high
|
|
tags: [automation, shell, decision]
|
|
sources: []
|
|
---
|
|
# 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 `active` and the setting is still `true`.**
|
|
> `terminal.persistent_shell: true` in `~/.hermes/config.yaml`, `backend: local`,
|
|
> `timeout: 180`, `home_mode: auto`, `container_cpu: 1`, `lifetime_seconds: 300`.
|
|
> The `review_after: 0001-01-01` value 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: 300` means 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]].
|
|
|
|
## Related
|
|
- [[persistent-shells]]
|