docs: document third-party memory stores via register_memory_store() - #670
Open
mdhaseeb343q-pixel wants to merge 1 commit into
Open
docs: document third-party memory stores via register_memory_store()#670mdhaseeb343q-pixel wants to merge 1 commit into
mdhaseeb343q-pixel wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The memory guide documents the four in-tree stores but not that
register_memory_store()is usable from installed packages - which it is, and it works great. This PR adds a short Third-Party Stores subsection todocs/user_guide/en/modules/memory.mdexplaining the seam, with a working pip-installable example (chatdev-memorysync, a store type for the MemorySync memory service) including its YAML config.No code changes - docs only. The example package registers itself via a
.pthhook on install and no-ops outside DevAll environments; the store passes DevAll's config parser, MemoryFactory, and MemoryManager end to end (tested against a fresh clone of this repo's main on every push).Happy to adjust wording or trim the example if you'd prefer the section to stay vendor-neutral.