NousResearch/hermes-agent

Fix outdated memory_mode reference in doctor.py

Cluster 5327 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
Nothing open on GitHub.

These issues and PRs address a naming inconsistency where doctor.py references an old field name memory_mode instead of the current recall_mode on HonchoClientConfig. The fix updates doctor.py to use the correct field name.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #5645 fix(doctor): use recall_mode instead of memory_mode on HonchoClientConfig

    merged to mainSuggested link · files and diff not shown

1 PR closed without merging

From the close comments: duplicate 1

  • #5328 fix: HonchoClientConfig has `recall_mode`, doctor.py still references `memory_mode` · duplicate → #5645
Closed issues · 1
  • Closed#5327fix: HonchoClientConfig has `recall_mode`, doctor.py still references `memory_mode`
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
Merged PRs
#5645
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.