Fix: Cohere Endpoint - Add Support for Tools #1490
Merged
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
…SingleStep for linting
|
Hi @nsarrazin, |
nsarrazin
approved these changes
Sep 26, 2024
|
thanks for the fix! 🚀 |
ice91
pushed a commit
to ice91/chat-ui
that referenced
this pull request
Oct 30, 2024
* fix(endpointCohere): Added force_single_step param to chatStream call * refactor(endpointCohere): change force_single_step parameter to forceSingleStep for linting
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.
This pull request addresses the issue described in #1404 (comment), where attempting to use tools with the Cohere endpoint results in the following error:
cannot specify both message and tool_results in multistep mode.Since the Chat UI project handles the tool usage process, the multistep feature provided by the Cohere endpoint is unnecessary in this context. Therefore, I've modified the implementation to enforce a single API call, which resolves the issue.
Tested on: