Okay, I understand now. The issue is that when running inside LangGraph Studio, it’s using PostgreSQL to persist state—so the Memory Saver feature seems redundant, lol.
However, when accessing it via Postman, even if we pass all the messages, without a checkpointer there’s no persistent state across requests. That’s where we can actually see the Memory Saver in action. 