-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(AI Agent Node): Fix output parsing and empty tool input handling in AI Agent node #10970
Merged
OlegIvaniv
merged 4 commits into
master
from
ai-317-using-output-parsers-with-memory-throws-error-on-subsequent
Sep 30, 2024
Merged
fix(AI Agent Node): Fix output parsing and empty tool input handling in AI Agent node #10970
OlegIvaniv
merged 4 commits into
master
from
ai-317-using-output-parsers-with-memory-throws-error-on-subsequent
Sep 30, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
burivuhster
reviewed
Sep 27, 2024
packages/@n8n/nodes-langchain/nodes/agents/Agent/agents/ToolsAgent/execute.ts
Outdated
Show resolved
Hide resolved
burivuhster
reviewed
Sep 27, 2024
packages/@n8n/nodes-langchain/nodes/agents/Agent/agents/ToolsAgent/execute.ts
Show resolved
Hide resolved
burivuhster
requested changes
Sep 27, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, I only have one minor suggestion about TS types
burivuhster
approved these changes
Sep 30, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
n8n Run #7087
Run Properties:
|
Project |
n8n
|
Branch Review |
ai-317-using-output-parsers-with-memory-throws-error-on-subsequent
|
Run status |
Passed #7087
|
Run duration | 04m 19s |
Commit |
b9d3e33a92: 🌳 🖥️ browsers:node18.12.0-chrome107 🤖 OlegIvaniv 🗃️ e2e/*
|
Committer | Oleg Ivaniv |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
0
|
Pending |
0
|
Skipped |
0
|
Passing |
432
|
View all changes introduced in this branch ↗︎ |
✅ All Cypress E2E specs passed |
OlegIvaniv
deleted the
ai-317-using-output-parsers-with-memory-throws-error-on-subsequent
branch
September 30, 2024 08:09
Got released with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR addresses two issues in the AI Agent node:
Output parser and memory compatibility
When using both an output parser and memory in the AI Agent node, we encountered an issue where the memory component requires the output to be a string. To resolve this, we now:
This ensures that the memory component receives the expected string format while maintaining the structured output for workflow operations.
Empty tool input handling for Anthropic
The Anthropic chat model expects tool inputs always to be objects. However, when using a tool that doesn't require arguments, the input would default to an empty string (''), causing errors. We've implemented a fix to:
Related Linear tickets, Github issues, and Community forum posts
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)