useStream stop() method behaves inconsistently when stopping a thread/stream #353

Closed
opened 2026-02-15 18:16:08 -05:00 by yindo · 0 comments
Owner

Originally created by @afmoleirinho96 on GitHub (Sep 4, 2025).

Checked other resources

  • I added a very descriptive title to this issue.
  • I searched the LangGraph.js documentation with the integrated search.
  • I used the GitHub search to find a similar question and didn't find it.
  • I am sure that this is a bug in LangGraph.js rather than my code.
  • The bug is not resolved by updating to the latest stable version of LangGraph (or the specific integration package).

Example Code

See description.

Error Message and Stack Trace (if applicable)

No response

Description

Currently, with "@langchain/langgraph-sdk": "0.1.0" or 0.1.1, it's impossible to stop the stream and the tool calls seem to be heavier and more UI blocking.
The request that the stream.stop() hit is:

Image

Before, with"@langchain/langgraph-sdk": "0.0.112", triggering stream.stop() would stop the stream from emitting values, although not 100% of the times.

The request that the stream.stop() would hit is:

Image

Moreover, would it be possible to provide a method, such as the stop() from useStream that puts the thread on hold?

My reasoning is that even with version 0.0.112, the stream would sometimes receive an:

interrupt: { when: "breakpoint"}

This only occurred occasionally, but it was useful since I could then continue working on that thread afterwards.

It would therefore be great to have additional options such as stop(), stop() - with some properties - or even resume()

System Info

"@langchain/langgraph-sdk": "0.0.112" to "@langchain/langgraph-sdk": "^0.1.1"

Originally created by @afmoleirinho96 on GitHub (Sep 4, 2025). ### Checked other resources - [x] I added a very descriptive title to this issue. - [x] I searched the LangGraph.js documentation with the integrated search. - [x] I used the GitHub search to find a similar question and didn't find it. - [x] I am sure that this is a bug in LangGraph.js rather than my code. - [x] The bug is not resolved by updating to the latest stable version of LangGraph (or the specific integration package). ### Example Code See description. ### Error Message and Stack Trace (if applicable) _No response_ ### Description Currently, with `"@langchain/langgraph-sdk": "0.1.0"` or `0.1.1,` it's impossible to stop the stream and the tool calls seem to be heavier and more UI blocking. The request that the `stream.stop()` hit is: <img width="270" height="19" alt="Image" src="https://github.com/user-attachments/assets/38bd45e3-202d-43f7-aeb6-ab1a1d2ab635" /> ----------------------------------------------- Before, with`"@langchain/langgraph-sdk": "0.0.112",` triggering `stream.stop()` would stop the stream from emitting values, although not 100% of the times. The request that the `stream.stop()` would hit is: <img width="272" height="28" alt="Image" src="https://github.com/user-attachments/assets/c85093a7-5cf8-46ab-ad74-51aaac872f6b" /> Moreover, would it be possible to provide a method, such as the `stop()` from `useStream` that puts the thread on hold? My reasoning is that even with version `0.0.112`, the stream would sometimes receive an: ``` interrupt: { when: "breakpoint"} ``` This only occurred occasionally, but it was useful since I could then continue working on that thread afterwards. It would therefore be great to have additional options such as stop(), stop() - with some properties - or even resume() ### System Info `"@langchain/langgraph-sdk": "0.0.112"` to `"@langchain/langgraph-sdk": "^0.1.1"`
yindo added the bug label 2026-02-15 18:16:08 -05:00
yindo closed this issue 2026-02-15 18:16:08 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraphjs#353