feature: manage tool responses #276
Closed
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
carlos-verdes
force-pushed
the
feature/openai-manage-tool-answer
branch
from
1723559 to
235bddb
Compare
|
Created smaller PR covering only agent changes + fixing OpenAI issues (another PR fixing DeepSeek Message model is open which will make tool calls work) |
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.
It implements the next flow:
It works with OpenAI but I found an issue with DeepSeek and the serialization of content messages, when you send the tool call back to DeepSeek the content is empty and DeepSeek expects
content: "", however current serialization (based on OpenAI) is sendingcontent: []which makes DeepSeek fail.also fixes #274