After changing the profile, Hermes Agent found that the external memory was "gone", often not lost, but the profile was originally isolated. The official Memory Providers documentation clearly states that the configuration and data of each provider are segregated by profile, and credentials and local paths are not necessarily shared.
Why is this happening?
Because the purpose of profile is to separate "work assistants, personal assistants, test instances". If memories and credentials are all strung together, profiles lose their meaning.
How to understand
- On-premises providers take the path of their own profiles.
- Profile-based providers are also saved by profile.
- Although the cloud provider is on the cloud, Hermes will still derive different configurations or project names based on profile.
In a word: After changing the profile, the memory is not the same as before, it is the isolation that takes effect, not necessarily because the Hermes Agent lost the data.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
