agents: add deprecation notice to reAct agent#465
Merged
Conversation
dkolas
approved these changes
Jul 11, 2023
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
2 participants
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.
Since the publication of the updated OpenAI models that support function data, we have observed a severe drop in functional performance of the
ReActAgent.This PR marks that agent as deprecated and lists the models that still respond best for that style of agent (
gpt-4-0314andgpt-3.5-turbo-0301).Each of those models will be discontinued in Sept. of this year, so this merely provides a deprecation period for the
ReActAgent(unless another non-OpenAI LLM is found to work with them, or OpenAI's iterations togpt-4andgpt-3.5-turboend up supporting the style of prompting exploited byReActAgentagain.