We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SelectorGroupChat example does not work with o3-mini. The prompt we use has the agent very eager to TERMINATE after 1 round of thinking.
https://microsoft.github.io/autogen/stable//user-guide/agentchat-user-guide/selector-group-chat.html
For it to work like GPT-4o
Run the example, but change the model to o3-mini
0.4.5
AgentChat
o3-mini
No response
The text was updated successfully, but these errors were encountered:
Text-based termination is too brittle. Likely we need some other verifiers to ensure behavior.
Currently, we can advice that if a task is not completed, just run the team again with a new prompt to continue.
Sorry, something went wrong.
Text-based termination is too brittle. Likely we need some other verifiers to ensure behavior. Currently, we can advice that if a task is not completed, just run the team again with a new prompt to continue.
Agreed. Maybe we just change the example slightly somehow.
No branches or pull requests
What happened?
SelectorGroupChat example does not work with o3-mini. The prompt we use has the agent very eager to TERMINATE after 1 round of thinking.
https://microsoft.github.io/autogen/stable//user-guide/agentchat-user-guide/selector-group-chat.html
What did you expect to happen?
For it to work like GPT-4o
How can we reproduce it (as minimally and precisely as possible)?
Run the example, but change the model to o3-mini
AutoGen version
0.4.5
Which package was this bug in
AgentChat
Model used
o3-mini
Python version
No response
Operating system
No response
Any additional info you think would be helpful for fixing this bug
No response
The text was updated successfully, but these errors were encountered: