Hermes Makes Auto-Prune Opt-In, Fixes Gateway Routing
Hermes Agent’s main branch makes automatic session pruning opt-in again, replacing silent deletion with a disk-pressure prompt. The update also addresses API-key routing issues in its one-gateway runtime, where profile isolation is a security boundary. [Hermes sessions docs](https://github.com/NousResearch/hermes-agent/blob/main/website/docs/user-guide/sessions.md) [Multiplexing Gateway docs](https://github.com/NousResearch/hermes-agent/blob/main/website/docs/developer-guide/multiplexing-gateway.md)
Hermes is making the right trust tradeoff: persistent session history is part of an agent’s value, so deleting it silently should never be the default. The more consequential change is gateway correctness—centralizing profiles simplifies operations but raises the stakes for credential scoping.
- –Auto-prune now requires explicit opt-in, preserving session history for recall and auditability.
- –Disk-pressure prompting gives operators a chance to choose cleanup instead of discovering missing sessions later.
- –One gateway serving multiple profiles reduces process overhead but must keep API keys bound to the correct profile and host.
- –Hermes’s API server exposes powerful tools, including terminal access, making authentication and routing failures especially serious. [API server docs](https://github.com/NousResearch/hermes-agent/blob/main/website/docs/user-guide/features/api-server.md)
DISCOVERED
1h ago
2026-10-17
PUBLISHED
1h ago
2026-10-17
RELEVANCE
AUTHOR
bwo_ai
