fix(plugins): give dual-kind memory hooks a single owner

This commit is contained in:
Joey
2026-09-06 18:18:04 +02:00
committed by Teknium
parent 857218e6da
commit 684a2cfbd7
6 changed files with 248 additions and 11 deletions
@@ -1511,6 +1511,8 @@ def register(ctx):
Memory providers are single-select — only one is active at a time, chosen via `memory.provider` in `config.yaml`.
If a provider also loads as a general plugin, general discovery owns its lifecycle hooks. The memory loader supplies hooks only as a fallback until that same plugin source loads successfully through general discovery. Repeated provider loads replace the fallback hook group; distinct callbacks within the group are preserved. This does not deduplicate hooks from different plugin sources or change provider activation.
**Full guide:** [Memory Provider Plugins](/developer-guide/memory-provider-plugin) — full `MemoryProvider` ABC, threading contract, profile isolation, CLI command registration via `cli.py`.
### Context engine plugins — replace the context compressor