You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So it would be cool to have more "native" support for it.
The trick here is that after sending an update the status of specific node sendUpdate like this
It's crucial to pass "null" and not "toolMessage with empty content".
The issue with current implementation is when I'm calling addResult(null); in my component it sends ToolMessage with content='' which sends an empty message.
So I tweaked the chatApi.ts to ignore that and send "null" to continue the workflow. Then workflow nicely continued on "humanInput" node as expected and is not going through START node.
Could you please add some better support to sending "null" into the stream?
I'm trying to do pause-resume scenario with LangGraph and works very nicely but I had to tweak chatApi.ts
https://github.com/Yonom/assistant-ui/blob/main/examples/with-langgraph/lib/chatApi.ts#L44
So it would be cool to have more "native" support for it.
The trick here is that after sending an update the status of specific node
sendUpdate
like thisIt's important to send message that "continue" the workflow from THAT node. And it's done via
It's crucial to pass "null" and not "toolMessage with empty content".
The issue with current implementation is when I'm calling
addResult(null);
in my component it sends ToolMessage with content='' which sends an empty message.So I tweaked the chatApi.ts to ignore that and send "null" to continue the workflow. Then workflow nicely continued on "humanInput" node as expected and is not going through START node.
Could you please add some better support to sending "null" into the stream?
Langgraph docs for reference: https://langchain-ai.github.io/langgraph/cloud/how-tos/human_in_the_loop_user_input/#invoking-after-receiving-human-input
The text was updated successfully, but these errors were encountered: