feat(agents): support AbortSignal in createReactAgent #8671
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds support for
AbortSignal
in thecreateReactAgent
function, allowing users to cancel agent execution and tool invocations. This is particularly useful for long-running agent operations where users may want to cancel execution based on external events or user interaction.Key Changes:
abortSignal
parameter toCreateReactAgentParams
- Users can now pass anAbortSignal
when creating an agentToolNode
and properly merged with any existing signals from LangGraph's Pregel classAbortSignal.any()
- When both agent-level and config-level signals are present, they are merged usingAbortSignal.any()
(with appropriate TypeScript declarations for this newer API)Usage Example:
Additional Improvements:
AbortSignal.any()
which is not yet in TypeScript's libFixes #(issue)