Is this a new feature, an improvement, or a change to existing functionality?
Improvement
How would you describe the priority of this feature request
High
Please provide a clear description of problem this feature solves
When serving a LangGraph agent through NAT’s langgraph_wrapper, LangGraph checkpoint/thread memory does not work because the wrapper invokes the graph without passing a RunnableConfig containing configurable.thread_id.
This breaks LangGraph graphs that are compiled with a checkpointer and rely on thread_id for conversation continuity.
It seems as if NAT has some built in utilities for long term memory, but not shorter term persistence.
Describe your ideal solution
When a user id and/or conversation id is given to NAT, it should probably combine those and pass them to langgraph like this:
conversation_id = f"{nat_user}:{nat_conversation_id}"
await graph.ainvoke(
input,
config={"configurable": {"thread_id": conversation_id}},
)
Additional context
This support is required for agents with preserved sessions and is analogous to how tools like Hermes manage sessions.
Code of Conduct
Is this a new feature, an improvement, or a change to existing functionality?
Improvement
How would you describe the priority of this feature request
High
Please provide a clear description of problem this feature solves
When serving a LangGraph agent through NAT’s langgraph_wrapper, LangGraph checkpoint/thread memory does not work because the wrapper invokes the graph without passing a RunnableConfig containing configurable.thread_id.
This breaks LangGraph graphs that are compiled with a checkpointer and rely on thread_id for conversation continuity.
It seems as if NAT has some built in utilities for long term memory, but not shorter term persistence.
Describe your ideal solution
When a user id and/or conversation id is given to NAT, it should probably combine those and pass them to langgraph like this:
Additional context
This support is required for agents with preserved sessions and is analogous to how tools like Hermes manage sessions.
Code of Conduct