hermes - 💡(How to fix) Fix Profiles using hindsight memory provider cannot isolate memory banks [1 participants]

Problem

When using Hermes profiles, all profiles that enable memory.provider: hindsight share the same hindsight memory bank. There is no way to configure a per-profile bank ID or have per-profile hindsight configuration.

Current behavior

• Hindsight config lives at ~/.hermes/hindsight/config.json (global), with a single bank_id: "hermes"
• Profiles (~/.hermes/profiles/<name>/) have memory.provider: hindsight in their own config.yaml, but no hindsight/config.json — the hindsight/ directory isnt created per-profile
• All profiles with hindsight enabled read/write the exact same bank — memories created in profile A are recallable in profile B

~/.hermes/
├── hindsight/config.json          ← bank_id: "hermes" (single, global)
└── profiles/
    ├── userA/config.yaml          ← memory.provider: hindsight  → uses bank "hermes"
    ├── userB/config.yaml          ← memory.provider: hindsight  → also uses bank "hermes"
    └── (... no hindsight/ dir under any profile)

Expected behavior

Each profile should be able to have its own isolated hindsight memory bank, so that memories written by one profile/user are not visible to others.

Suggested approaches

1. Profile-level hindsight config — allow ~/.hermes/profiles/<name>/hindsight/config.json to override the global config, including a different bank_id per profile.
2. memory.bank_id config option — add a memory.bank_id field to profile config.yaml that overrides the global hindsight configs bank_id when set.
3. Auto-bank-per-profile — when a profile has memory.provider: hindsight but no explicit bank_id, default the bank_id to the profile name (e.g. hermes-<profile_name>).

Impact

Any multi-user Hermes setup (e.g. each team member gets their own profile with a dedicated Feishu/Telegram bot) needs memory isolation to function correctly. Currently this is not possible with hindsight — all users memories bleed into each other.