Week 12 — Lesson 4: Persistent memory with the SQLite checkpointer

2 min

Without memory, the NorthPeak agent forgets the previous question as soon as graph.invoke returns. A technician who asks "How many incidents does M014 have?" and then "And what is its machine type?" gets a second answer that ignores the first. A checkpointer is the object that saves the state after every node under a thread_id, so a conversation can continue tomorrow, on the same laptop, from a SQLite file. This lesson covers the checkpoint, the SqliteSaver, the thread, and a real run with and without memory.

Preview — the rest of the lesson is for enrolled readers.

Already enrolled with a code?

Your access is tied to your account, not to this link. Sign in with the same email you used in class: your course is waiting, no need to enter the code again.

Sign inNo account yet? Create one
This lesson is part of the “Week 12 — Stateful workflows with LangGraph” module

The first modules of the course are open to everyone. For the rest you have three options: buy this course once and for all, subscribe, or enter the code handed out in class.

Are you a student on this course?

The code is tied to your account: sign in or create an account and it will be applied automatically when you come back.

No account yet? Create one