bypassing annoying bedrock error message#280
Draft
marytlf wants to merge 1 commit into
Draft
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
###Issue: #278
Description:
AWS Bedrock requires a toolConfig field whenever a conversation contains toolUse/toolResult content blocks — even if you're making a follow-up call without tools. The UI tools selector was triggering this because it calls the LLM with conversation history (which may contain tool blocks) but without any tools defined.
Atual Results:
Annoying messages "The toolConfig field must be defined when using toolUse and toolResult content blocks."
Expected Results:
No annoying messages when using liz without any tools configured.
Environment:
Rancher: main
Rancher-ai-agent: v1.1.0-alpha.7
Tests:
TBD
###Reproduction steps:
TBD