Bedrock: Ask to support Claude Computer Use in Converse Function

[skerava]

Describe the feature

• It is very normal and convenient to use 'converse' method to invoke models in Bedrock.Many system integrations are based on the 'converse' method.
• Currently, the AWS Bedrock API and Python SDK support the 'converse' method to invoke the 'computer use' feature of the Claude Haiku 3.5/Sonnet 3.5 v2 model.
  https://aws.amazon.com/cn/blogs/aws/upgraded-claude-3-5-sonnet-from-anthropic-available-now-computer-use-public-beta-and-claude-3-5-haiku-coming-soon-in-amazon-bedrock/
• However it seems that go sdk now only support ‘computer use’ feature in InvokeModel Method.

Please integrate support in the Go SDK to use the 'converse' method to invoke Claude's 'computer use' feature.

Use Case

Same above

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS Go SDK V2 Module Versions Used

github.com/aws/aws-sdk-go-v2 v1.27.1

Go version used

1.23.3

[RanVaknin]

Hi @skerava,

Could you clarify what specific SDK implementation you're looking for? The computer use feature should already work with the existing InvokeModel method by passing the appropriate JSON request body (including the tools configuration and anthropic_beta flag with the new computer use value as shown in the blogpost).

Thanks,
Ran~

[skerava]

Hi @RanVaknin,

Here are the key points:

The Bedrock runtime supports two methods for interacting with Claude models:Converse and InvokeModel. Our system, as well as those of our customers, are both based on the Converse method.

As you mentioned, the computer-use feature currently works with the InvokeModel method. However, it is not yet supported with the Converse method, even though AWS API and Python's boto3 library already support it.

Our customer's system has been waiting for the Bedrock-runtime's Converse method in the Go SDK to support the computer-use feature, as they already have clear project goals that require this capability. Reintegrating with the InvokeModel method would not only increase the system's complexity but also fall short of customer expectations, as they do not want to integrate the same functionality twice.