Cairn
NousResearch/hermes-agent

CLI profile override applying twice or incorrectly

Cluster 66907 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These issues and fixes center on _apply_profile_override being called more than once or behaving incorrectly under 'python -m' invocation, causing profile context variables and HERMES_HOME to be set wrong. Solutions include PID-scoped sentinels, ContextVar handling, and double-import prevention.

Open issues1

  • Issue#66907Default-profile gateway hijacked to active_profile: _apply_profile_override runs twice under python -m (flag stripped on first pass)

Open PRs2

  • PR#67048fix: add PID-scoped run-once sentinel to _apply_profile_override (#66907)
  • PR#75109fix(cli): prevent python -m main double-import profile rehoming
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
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/66907.json
cluster/66907.md