fix(docs): add checkpointer=InMemorySaver() to trim_messages example for persistent memory #1244
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.
Overview
This PR updates the
trim_messagesexample in the documentation to includecheckpointer=InMemorySaver().Without the checkpointer, each
agent.invoke()call starts a new conversation thread, causing the agent to forget previous context (e.g., the user’s name).This change ensures persistent memory across invocations and aligns the example’s behavior with the printed output shown in the docs.
Type of change
Type: Update existing documentation
Related issues/PRs
None directly.
This PR addresses confusion reported by users when reproducing the
trim_messagesexample —the code output did not match the example’s described behavior without adding a
checkpointer.Checklist
Your name is Bobis remembered)Additional notes
This change makes the example self-contained and beginner-friendly.
It clarifies that persistent memory requires an explicit checkpointer when using
create_agent()with multi-turn interactions.