-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 AWS Bedrock as an Assistant provider #16544
Comments
Looking forward to this! |
I would be very excited for this feature! It would enable us to push for and recommend using Zed at my company! |
This comment has been minimized.
This comment has been minimized.
I would like to take this on; however, I would need guidance on how/what integration points we'd need to curate for Zed. |
I've started working with this and with Bedrock's model list getting longer each quarter, I thought a procedural macro might be the way to go when making the list of models. That way each build gets the most up-to-date Bedrock model without having to curate it letting the user pick the best model for their purpose. Does Zed have a particular policy for or against proc_macros? For the extension itself, I'm going to try and follow the Anthropic crate but instead of HTTP requests, I'll use the AWS Bedrock Runtime Client. |
Check for existing issues
Describe the feature
Add AWS Bedrock as an Assistant provider.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
The text was updated successfully, but these errors were encountered: