Cairn

Ghost profile name after rename under multiplexer

NousResearch/hermes-agent · cluster 109267

Data as of

Nothing open on GitHub. Fix merged in #110202. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #110202. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #110202. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs concern a bug where renaming a profile while a multiplexer is running causes the old profile name to reappear as a ghost served profile. The work involves unrouting the old name before completing the rename to prevent this behavior.

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.

  • #110202 Profile rename under a live multiplexer no longer resurrects the old name as a ghost served profile (#109267, salvage #109269)

    merged to main

    files: hermes_cli/profiles.py, tests/hermes_cli/test_profiles.py, website/docs/user-guide/multi-profile-gateways.md

3 PRs closed without merging

From the close comments: done elsewhere 3

  • #109269 fix(profiles): rename under a live multiplexer no longer resurrects the old name · done elsewhere → 6de2dde, #110202
  • #109271 fix(profiles): prevent ghost profile after rename · done elsewhere → 6de2dde, #110202
  • #109299 fix(cli): unroute the old name before renaming a multiplexed profile · done elsewhere → #109269
Closed issues · 1
  • Closed#109267[Bug]: profile rename under a running multiplexer resurrects the old name as a ghost served profile
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.40: 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

Merged PRs
#110202
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
13 Sep 2026

For your agent

The same facts, typed.

cluster/109267.json
cluster/109267.md