Cairn
NousResearch/hermes-agent

Old installs keep stale seeded config defaults after upgrades

Cluster 136754 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 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
1 issue and 1 PR.

The members share one theme: older installs appear to retain previously seeded config values (such as approvals.mode: manual and timeout: 60), so newer defaults may not reach long-time users. One item is a bug report, and the two PR-style titles describe CLI changes that re-baseline or drop seeded timeout settings.

Open issues1

  • Issue#136754[Bug]: Upgraded installs stay pinned to old seeded defaults (e.g. approvals.mode: manual / timeout: 60) — default changes never reach long-time users

Open PRs1

  • PR#136771fix(cli): drop seeded approvals.timeout/agent.clarify_timeout so new defaults reach old installs

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #136776 fix(cli): re-baseline stale seeded defaults on pre-stripping installs · superseded by another PR → #136771, #136754
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/136754.json
cluster/136754.md