hermes - 💡(How to fix) Fix [Feature]: add a --force option to `hermes sessions prune` [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#15685Fetched 2026-04-26 05:25:50
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4
RAW_BUFFERClick to expand / collapse

Problem or Use Case

I communicate with Hermes via Slack. Every thread creates a new session, so there are many. If pruning never deletes sessions that are active, and there isn't an obvious way to end a session from a Slack thread, sessions accumulate in storage forever. I need a convenient way to clean these up.

Proposed Solution

Add a --force option to hermes sessions prune to override the "Active sessions are never pruned" policy [https://hermes-agent.nousresearch.com/docs/user-guide/sessions).

Alternatives Considered

Provide a well-known way in a slack conversation to end a session tied to a thread without starting a new session. The /new and /reset mechanisms don't seem appropriate.

Feature Type

CLI improvement

Scope

Small (single file, < 50 lines)

Contribution

  • I'd like to implement this myself and submit a PR

Debug Report (optional)

extent analysis

TL;DR

Add a --force option to hermes sessions prune to allow deletion of active sessions.

Guidance

  • Review the Hermes documentation to understand the current session pruning policy and its implications.
  • Consider the potential consequences of overriding the "Active sessions are never pruned" policy, such as loss of active session data.
  • Evaluate the proposed --force option as a potential solution to the issue of accumulating sessions in storage.
  • Investigate alternative methods for ending a session from a Slack thread without starting a new session.

Example

No code snippet is provided as the issue does not contain sufficient technical details to generate a accurate example.

Notes

The proposed solution may have unintended consequences, such as data loss, and should be carefully evaluated before implementation.

Recommendation

Apply workaround: Add a --force option to hermes sessions prune to override the "Active sessions are never pruned" policy, as it provides a convenient way to clean up accumulated sessions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Feature]: add a --force option to `hermes sessions prune` [1 participants]