vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-20 12:37:04 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[GH-ISSUE #160] [Bug]: When using Bedrock, toolConfig is not defined causing failures. #64

New Issue
Closed
opened 2026-06-06 22:08:55 -04:00 by yindo · 1 comment
yindo commented 2026-06-06 22:08:55 -04:00
Owner
Copy Link
Copy Source

Originally created by @ThatServerGuy on GitHub (Mar 1, 2026).
Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/160

Originally assigned to: @asdek on GitHub.

Affected Component

External Integrations (LLM/Search APIs)

Describe the bug

With any model on Bedrock I get failures in line with this:
Error: converse API call failed: operation error Bedrock Runtime: Converse, https response error StatusCode: 400, RequestID: fb82c3b1-af04-4405-8958-999d7a5e39c4, ValidationException: The toolConfig field must be defined when using toolUse and toolResult content blocks.

Steps to Reproduce

Create new provider, set bedrock as provider, test with any model.

System Configuration

N\A

Logs and Artifacts

No response

Screenshots or Recordings

Image

Verification

  • I have checked that this issue hasn't been already reported
  • I have provided all relevant configuration files (with sensitive data removed)
  • I have included relevant logs and error messages
  • I am running the latest version of PentAGI
Originally created by @ThatServerGuy on GitHub (Mar 1, 2026). Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/160 Originally assigned to: @asdek on GitHub. ### Affected Component External Integrations (LLM/Search APIs) ### Describe the bug With any model on Bedrock I get failures in line with this: Error: converse API call failed: operation error Bedrock Runtime: Converse, https response error StatusCode: 400, RequestID: fb82c3b1-af04-4405-8958-999d7a5e39c4, ValidationException: The toolConfig field must be defined when using toolUse and toolResult content blocks. ### Steps to Reproduce Create new provider, set bedrock as provider, test with any model. ### System Configuration N\A ### Logs and Artifacts _No response_ ### Screenshots or Recordings <img width="901" height="646" alt="Image" src="https://github.com/user-attachments/assets/581cd4e1-1e07-4a7d-be58-c5d3fd1a6b5f" /> ### Verification - [x] I have checked that this issue hasn't been already reported - [x] I have provided all relevant configuration files (with sensitive data removed) - [x] I have included relevant logs and error messages - [x] I am running the latest version of PentAGI
yindo added the bug label 2026-06-06 22:08:55 -04:00
yindo closed this issue 2026-06-06 22:08:55 -04:00
yindo commented 2026-06-06 22:08:56 -04:00
Author
Owner
Copy Link
Copy Source

@asdek commented on GitHub (Mar 19, 2026):

hey @ThatServerGuy

thanks for the report! this issue has been addressed through multiple fixes:

  • #166 - initial Bedrock toolConfig handling
  • #185 - additional Bedrock API compatibility improvements
  • #206 - further Bedrock converse API fixes

these were actually three different underlying issues that manifested similarly. the Bedrock provider is now working correctly in the latest builds.

i'm closing this issue as resolved. if you still encounter this problem after updating to the latest version, please reopen with fresh PentAGI server logs and we'll investigate further

<!-- gh-comment-id:4093949173 --> @asdek commented on GitHub (Mar 19, 2026): hey @ThatServerGuy thanks for the report! this issue has been addressed through multiple fixes: - #166 - initial Bedrock toolConfig handling - #185 - additional Bedrock API compatibility improvements - #206 - further Bedrock converse API fixes these were actually three different underlying issues that manifested similarly. the Bedrock provider is now working correctly in the latest builds. i'm closing this issue as resolved. if you still encounter this problem after updating to the latest version, please reopen with fresh PentAGI server logs and we'll investigate further
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#64
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?