Nothing open on GitHub. Fix merged in #120137 on 23 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #120137. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #120137. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern a bug where cloning a profile copies the memory.provider setting but not the provider's configuration directory, causing silent failures. The work addresses how memory provider config dirs are handled during light and full clone operations.
Open issues0
Open PRs0
Fixes on record
-
#120137 profile --clone keeps the active memory provider's config (#120115, supersedes #43107)
files:
hermes_cli/profile_cmd.py,hermes_cli/profile_memory_config.py,hermes_cli/profiles.py,tests/hermes_cli/test_profiles.py,website/docs/reference/profile-commands.md,website/docs/user-guide/profiles.md
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#120115profile create --clone copies memory.provider but not the provider's config dir (hindsight/) — clone auto-installs the plugin then reports 'not available' silently
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Merged PRs
- #120137
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 23 Sep 2026