-
Notifications
You must be signed in to change notification settings - Fork 22
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
Assistants API #57
Assistants API #57
Conversation
As per #50, I'm going to leave anything that has to do with the Files API out of the PR. |
Okie dokie! We're now ready for a review. I added tests and such but we should be good to go here. All tests pass locally using my personal API key. |
@rory-linehan could we merge this one or do a review? The tests fail due to not having and API key, but they pass locally on my machine. |
Looks good to me! Sorry, I've been traveling for the past couple weeks. And I'm ill now, of course.. |
Tests seem to fail on my side, and after merge.. I'm familiarizing myself with the Assistants API to figure out what's going on. Do they still pass for you locally? The failure I'm seeing is:
on line 183, in |
This is a WIP draft to add API coverage for the OpenAI Assistant tooling.
This implements the bulk of the beta API, with the exception of the File endpoints. This requires a bigger effort than this PR.
We may wish to stash all this stuff in a submodule like
OpenAI.Assistants
, especially since there are so many API endpoints associated with the assistants.I'm also addressing some formatting stuff inside the repo, since many of the function declarations are very wide and do not generally fit in most conventional editing panes. This is however not the primary focus of this PR and may not be complete. I'd prefer if we merged in #56 so that the formatting issues were addressed more thoroughly.
API implementations
Assistants API to implement
Threads
Messages
Runs
Will not be implemented in this PR: