{"repo":"NousResearch/hermes-agent","public_id":"32624","display_label":"Config warnings for memory settings and profile traps","summary":"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.","subsystem":"agent","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":1,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":32624,"title":"[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","url":null,"state":"open"},{"kind":"pr","number":32816,"title":"fix(config): warn when memory.provider is set alongside memory_enabled=false","url":null,"state":"closed","close_reason":{"category":"stale_abandoned","implication":"active"},"merged":false},{"kind":"pr","number":50076,"title":"fix(config): warn on memory_enabled/provider mismatch + show resolved config path at startup","url":null,"state":"open","close_reason":{"refs":[{"kind":"commit","value":"2bb531b67a","number":0}],"category":"duplicate_of","implication":"duplicate"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}