Native Grok implementation package #174
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Easily enable Web/X search from options
We model the hosted tool content so that responses can include them if needed by the client.
HostedFileSearchTool => Collection Search HostedVectorStoreContent => CollectionIds
Since opting for those outputs likely consumes additional output tokens, make them opt-in only. Now both are represented with specific tools rather than our generic HostedToolCallContent. Marked its usage as experimental since it's marked such in MS.E.AI too.
Member
Author
|
🧪 Details on Ubuntu 24.04.3 LTSfrom dotnet-retest v1.0.0 on .NET 10.0.0 with 💜 by @devlooped |
This fixes missing method exceptions in tests. We don't need the conditional deps versions for .net8. It's perfectly fine to use .v10 packages in .net8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We switch to the native gRPC-based GrokClient rather than endlessly trying to shoehorn everything over the OpenAI responses API.
By going native, we can now leverage quickly and easily all of the latest and greatest features that would otherwise require using the native API (most agentic tools require that).
Still pending to implement the embedding generator and image generator clients.