Cairn
NousResearch/hermes-agent

Config migration across Hermes profiles during upgrades

Cluster 20438 · 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, 2 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
Nothing open on GitHub.

These members share a theme: configuration migration appears to apply only to the active profile, so other profiles may keep stale settings (including deprecated toolsets) after upgrades. They discuss migrating all profiles on update and auto-migrating stale profile config at serve/dashboard startup.

Open issues0

No open issues.

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #62492 fix(config): auto-migrate stale profile config on serve/dashboard startup · superseded by another PR → #91277
Closed issues · 2
  • Closed#20438Config migration is profile-local; non-active profiles silently drift across Hermes upgrades
  • Closed#54926hermes update should migrate all profiles and clean up deprecated toolsets from config
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.79: 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
2
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/20438.json
cluster/20438.md