# NousResearch/hermes-agent · Config migration across Hermes profiles during upgrades

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 2 closed issue(s), 0 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.79`: the share of member 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.

## Closed / duplicate issues

- #20438: Config migration is profile-local; non-active profiles silently drift across Hermes upgrades
- #54926: hermes update should migrate all profiles and clean up deprecated toolsets from config

## Prior & competing PRs

- **#62492: fix(config): auto-migrate stale profile config on serve/dashboard startup**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#91277`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`