Why we need to write to the state after processing from a node in the langgraph's graph?

[nguyentruong-ins]

Why we need to write to the state after processing from a node in the langgraph's graph?

[nguyentruong-ins]

@dosu

[dosubot[bot]]

@nguyentruong-ins

Could you provide more context or details about the specific use case or system you're working with? For example, what is the purpose of the state in your application, and how does it interact with the nodes in the langgraph's graph? This information would help in understanding why writing to the state is necessary in your scenario.

To continue talking to Dosu, mention @dosu.

[nguyentruong-ins]

@dosu
I just want to know why in the graph created by langgraph. We must write to at least one field of the State?

[dosubot[bot]]

Could you provide more details about the specific functionality or purpose of the State in your application? Additionally, how does the State interact with the nodes in the langgraph's graph? Understanding these aspects would help in explaining why writing to the State is necessary.

To continue talking to Dosu, mention @dosu.

[nguyentruong-ins]

@dosu
The State in my application is the State of the lang graph's compiled graph, which will have a messages field for storing the list of messages of each node after every node process. After processing by a node, the node will add a message to the messages list. I want to add another RagNode that extracts relevant documents based on the user's message and print this document to the console without modifying the messages field of State

[dosubot[bot]]

Could you clarify what specific behavior or outcome you are trying to achieve by not modifying the messages field of the State? Additionally, are there any constraints or requirements in your application that necessitate this approach? Understanding these details might help in finding a suitable solution.

To continue talking to Dosu, mention @dosu.