-
-
Notifications
You must be signed in to change notification settings - Fork 84
com.openai.unity 8.0.0 #235
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
Conversation
- Updated Assistants Beta v2 - Added BatchEndpoint - Added VectorStoresEndpoint
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.
@StephenHodgson I believe the dynamic
keyword isn't supported on all platforms like WebGL and requires .NET 4.0 (doesn't work w/ 2.1).
Any chance we can avoid using dynamic
?
OpenAI/Packages/com.openai.unity/Runtime/Threads/CreateRunRequest.cs
Outdated
Show resolved
Hide resolved
OpenAI/Packages/com.openai.unity/Runtime/Threads/CreateThreadAndRunRequest.cs
Outdated
Show resolved
Hide resolved
OpenAI/Packages/com.openai.unity/Runtime/Threads/RunResponse.cs
Outdated
Show resolved
Hide resolved
OpenAI/Packages/com.openai.unity/Runtime/Threads/RunResponse.cs
Outdated
Show resolved
Hide resolved
OpenAI/Packages/com.openai.unity/Runtime/Threads/CreateRunRequest.cs
Outdated
Show resolved
Hide resolved
OpenAI/Packages/com.openai.unity/Runtime/Threads/CreateThreadAndRunRequest.cs
Outdated
Show resolved
Hide resolved
OpenAI/Packages/com.openai.unity/Runtime/Assistants/AssistantsEndpoint.cs
Outdated
Show resolved
Hide resolved
fixing a super old typo Co-authored-by: Stephen Hodgson <rage.against.the.pixel@gmail.com>
OpenAI/Packages/com.openai.unity/Runtime/Threads/CreateMessageRequest.cs
Show resolved
Hide resolved
@Bodekaer I just pushed up changes for parity with the upstream repo. Let me know what you think. |
… are not processed
updated vector store endpoint impl
added Tool.TryUnregisterTool to remove a tool from the cache misc bug fixes and cleanup
Great updates! Testing today. |
where method.IsStatic | ||
let functionAttribute = method.GetCustomAttribute<FunctionAttribute>() | ||
where functionAttribute != null | ||
let name = $"{type.FullName}.{method.Name}".Replace('.', '_') |
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.
@StephenHodgson I've found that Assistant v2 doesn't always understand well when type.FullName is included, because the namespaces I use are long and not relevant/confusing to the AI context.
I found that removing this and only including the method.Name
solved it.
I realize it isn't the ideal scenario in case two types contain the same method name, but it would still be helpful with an omit namespace
option if possible. For now I've been removing it manually here in each update :)
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.
I've ran into this a few time myself. I'll likely update it soon in the future to be a hashed string guid.
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.
Assistant v2 tested and works very well.
Note: Streaming + Vector DB not yet tested. Will do soon.
- Updated Assistants Beta v2 - Added support for specifying project id - Added BatchEndpoint - Added VectorStoresEndpoint - Added Message.ctr to specify specific tool call id, function name, and content - Renamed OpenAI.Images.ResponseFormat to OpenAI.Images.ImageResponseFormat - Changed ThreadEndpoint.CancelRunAsync return type from RunResponse to bool - Fixed Json defined Tools/Functions being improperly added to tool cache - Added Tool.TryUnregisterTool to remove a tool from the cache
TODO