-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
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
Support openai assistant v2 API #2466
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2466 +/- ##
==========================================
- Coverage 33.33% 33.20% -0.14%
==========================================
Files 83 83
Lines 8636 8692 +56
Branches 1835 1852 +17
==========================================
+ Hits 2879 2886 +7
- Misses 5516 5565 +49
Partials 241 241
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Co-authored-by: Eric Zhu <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the new changes compatible with older version of assistant API?
Yes, it has been done with the maximum backward compatibility. If the user uses the old file_ids to create the assistant, the assistant can still be created successfully. However, if the old and new configurations are mixed, an error will be reported. |
* adapted to openai assistant v2 api * fix comments * format code * fix ci * Update autogen/agentchat/contrib/gpt_assistant_agent.py Co-authored-by: Eric Zhu <[email protected]> --------- Co-authored-by: Eric Zhu <[email protected]>
Why are these changes needed?
This PR introduces support for the newly released OpenAI Assistant API v2, incorporating significant changes outlined in the migration guide. We aim to ensure compatibility with the existing API v1 without disrupting current implementations. The key modifications include:
By making these changes, it aim to leverage the advancements in API v2 while maintaining a smooth transition for existing applications still utilizing API v1.
Related issue number
Checks