hermes-agent/plugins/memory
Livia Ellen 5e3303b3d8 fix(mem0): merge env vars with mem0.json instead of either/or
When mem0.json exists but is missing the api_key (e.g. after running
`hermes memory setup`), the plugin reports "not available" even though
MEM0_API_KEY is set in .env.  This happens because _load_config()
returns the JSON file contents verbatim, never falling back to env vars.

Use env vars as the base config and let mem0.json override individual
keys on top, so both config sources work together.

Fixes: mem0 plugin shows "not available" despite valid MEM0_API_KEY in .env
2026-04-03 20:42:48 -07:00
..
byterover fix(memory): Fix ByteRover plugin - run brv query synchronously before LLM call 2026-04-03 12:11:29 -07:00
hindsight feat(memory): pluggable memory provider interface with profile isolation, review fixes, and honcho CLI restoration (#4623) 2026-04-02 15:33:51 -07:00
holographic fix(memory): preserve holographic prompt and trust score rendering 2026-04-03 14:22:22 -07:00
honcho feat(honcho): add configurable observation mode (unified/directional) 2026-04-02 20:38:36 -07:00
mem0 fix(mem0): merge env vars with mem0.json instead of either/or 2026-04-03 20:42:48 -07:00
openviking fix(openviking): send tenant-scoping headers on every request (#4825) 2026-04-03 20:32:55 -07:00
retaindb feat(memory): pluggable memory provider interface with profile isolation, review fixes, and honcho CLI restoration (#4623) 2026-04-02 15:33:51 -07:00
__init__.py feat(memory): pluggable memory provider interface with profile isolation, review fixes, and honcho CLI restoration (#4623) 2026-04-02 15:33:51 -07:00