Cairn
NousResearch/hermes-agent

Doctor auto_prune suggestion shown when already enabled

Cluster 83933 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These issues and pull requests address a bug where the doctor command incorrectly suggests enabling auto_prune even when it is already enabled. The fix ensures the advisory checks the effective setting before making the recommendation.

Open issues1

  • Issue#83933fix(doctor): size advisory suggests auto_prune even when already enabled

Open PRs1

  • PR#112391fix(doctor): large-DB advisory matches effective sessions.auto_prune (#83933)

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #83954 fix(doctor): don't suggest enabling auto_prune when already enabled · superseded by another PR → #112391
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/83933.json
cluster/83933.md