You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this tool already employs anthropic python sdk it is possible to add AWS Bedrock support out of the box for already supported models.
Right now I'm seeking opinion around what would be the ideal integration pattern:
Adding a separate provider e.g anthropic_bedrock and related configuration/cli options/handlers. and specifically on handler side it is a complete copy (you don't need to modify it besides the client initialization)
extending Handler behaviour to resolve AWS Bedrock client init by model id. Here idea is that the model name/ model id has different values than Anthropic API model name and we need to make that distinction only at create time
Adding a flag for anthropic api | bedrock in the CLI and pass it along in Settings and use this to create client, forcing user to know how to execute
combination of 2/3 where (2) is a default behaviour where nothing is specified and 3 if it is passed along
My own preference is 4, however looking for any advice and I can submit a MR right after.
The text was updated successfully, but these errors were encountered:
Since this tool already employs anthropic python sdk it is possible to add AWS Bedrock support out of the box for already supported models.
Right now I'm seeking opinion around what would be the ideal integration pattern:
Settings
and use this to create client, forcing user to know how to executeMy own preference is 4, however looking for any advice and I can submit a MR right after.
The text was updated successfully, but these errors were encountered: