hermes - 💡(How to fix) Fix [Feature]: Native support/bundling for AgentMemory as a Memory Provider [2 comments, 2 participants]

TL;DR

To use AgentMemory as a native Memory Provider in Hermes, manual workarounds are currently required, but native support or improved external plugin discovery could simplify the process.

Guidance

• Review the AgentMemory integration in the integrations/hermes directory of the AgentMemory repository to understand the required manual workarounds.
• Consider setting AGENTMEMORY_URL in the environment variables and memory.provider: agentmemory in config.yaml as a starting point for configuration.
• Investigate the Hermes plugin discovery mechanism to determine if improvements can be made to support AgentMemory as an available Memory Provider.
• Evaluate the feasibility of submitting a PR to implement native support for AgentMemory in Hermes.

Example

No code example is provided due to the lack of specific technical details in the issue.

Notes

The issue lacks specific error messages or technical details, making it challenging to provide a definitive solution. However, the proposed solution and alternatives considered sections provide a clear direction for potential improvements.

Recommendation

Apply workaround: The current workaround of manually configuring AgentMemory as a Memory Provider in Hermes, while not ideal, may be the most straightforward solution until native support or improved plugin discovery is implemented.