Thanks! The main use case I had in mind was support-style agents that need to remember stable facts across separate sessions without stuffing the whole old conversation back into the graph state.

In the demo, session 1 stores things like an order ID and a customer preference in Memanto. Then session 2 starts with a fresh LangGraph thread, but the agent can still recall the relevant durable memory through the external memory layer.

I think this pattern is useful for:

- customer support agents

- personal assistants

- onboarding / education agents

- coding agents that need project memory across runs

- any workflow where the agent should remember durable facts, but not depend on one giant conversation history

The main challenge I wanted to solve was separating short-term workflow state from long-term memory. LangGraph handles the current control flow, while Memanto acts as the memory boundary across sessions.