docs(synap): fix pipeline example — add user query path and wire memory_writer#520
Closed
Copilot wants to merge 2 commits into
Closed
docs(synap): fix pipeline example — add user query path and wire memory_writer#520Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Copilot
AI
changed the title
[WIP] Fix code based on review comment 3435602430
docs(synap): fix pipeline example — add user query path and wire memory_writer
Jun 18, 2026
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
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 "Use in a Pipeline" example fed
memory_retriever.messagesdirectly intoChatPromptBuilder.template, leaving no path for the user's current query, andmemory_writerwas added to the pipeline but never connected.Changes
ChatPromptBuilderwithOutputAdapter— merges retrieved memory messages with the current user message ({{ memories + user_messages }}), matching the pattern used bymem0-haystackmemory_writer— connectllm.replies → memory_writer.messagesto actually persist conversation turnspipeline.run(...)call — shows how to supply both the retrieval query and the user message at runtime