#Honcho and active memory
4 messages Β· Page 1 of 1 (latest)
Let me verify the Honcho integration bit so I donβt hand-wave this.
Nice, found the missing bit: Honcho is implemented as a memory-slot plugin, not just an add-on.
Yes, but with an important caveat:
Honcho is its own memory plugin, not a memory.backend for memory-core. So if you use Honcho, it becomes the active memory layer and replaces the built-in memory plugins rather than plugging into them.
Practical version:
- Honcho = cross-session/user memory via
honcho_*tools - QMD / builtin memory backend = local file search over
MEMORY.md/memory/*.md
If you want both, pair Honcho with QMD. Then you get:
- Honcho for cross-session memory
memory_search/memory_getfor local markdown memory
Docs: