Skip to content

Conversation

StephenHodgson
Copy link
Member

@StephenHodgson StephenHodgson commented May 20, 2024

  • 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

- Updated Assistants Beta v2
- Added BatchEndpoint
- Added VectorStoresEndpoint
Copy link

@Bodekaer Bodekaer left a 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?

fixing a super old typo

Co-authored-by: Stephen Hodgson <rage.against.the.pixel@gmail.com>
@StephenHodgson StephenHodgson mentioned this pull request May 23, 2024
@StephenHodgson
Copy link
Member Author

@Bodekaer I just pushed up changes for parity with the upstream repo. Let me know what you think.

@StephenHodgson StephenHodgson marked this pull request as ready for review June 10, 2024 04:46
@StephenHodgson StephenHodgson requested a review from Bodekaer June 10, 2024 04:46
@Bodekaer
Copy link

Great updates! Testing today.

where method.IsStatic
let functionAttribute = method.GetCustomAttribute<FunctionAttribute>()
where functionAttribute != null
let name = $"{type.FullName}.{method.Name}".Replace('.', '_')

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 :)

Copy link
Member Author

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.

Copy link

@Bodekaer Bodekaer left a 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.

@StephenHodgson StephenHodgson merged commit 9a3c7cb into main Jun 10, 2024
@StephenHodgson StephenHodgson deleted the development branch June 10, 2024 09:21
github-actions bot pushed a commit that referenced this pull request Jun 10, 2024
- 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants