Cairn
NousResearch/hermes-agent

Config warnings for memory settings and profile traps

Cluster 32624 · agent. 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.

These items address silent or confusing behavior in memory-related configuration, including mismatches between memory_enabled and provider settings, and UX pitfalls around profile config overrides and log paths. The work involves adding warnings and surfacing active config paths to help users debug these scenarios.

Open issues1

  • Issue#32624[Bug/UX] Three config semantic traps for users debugging memory / multi-profile: silent failure of memory_enabled, profile config override, and per-profile log paths

Open PRs1

  • PR#50076fix(config): warn on memory_enabled/provider mismatch + show resolved config path at startup

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #32816 fix(config): warn when memory.provider is set alongside memory_enabled=false · stale or abandoned
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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/32624.json
cluster/32624.md