[BUG] Breaking on Opus without proper error reporting on UI level

[wzr1337]

Describe the bug

Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.

The Claude 3 (Opus) model is currently unavailable due to a throughput limitation. The system is unable to process the request at this time.

Request: It would be helpful if the actual error message ("The provided model doesn't support on-demand throughput") was displayed directly in the user interface, rather than the generic "An error occurred while responding." This would provide users with more specific information about the issue without requiring them to use web inspection tools for debugging.

To Reproduce

Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.
Steps to reproduce the behavior:

1. Go to Home screen
2. Open WebInseptor
3. open network tab
4. select WebScoket filter
5. focus back on the main screen
6. Click on "Claude 3 (Opus)" (select)
7. Type "Hi" and press enter
8. See error: "An error occurred while responding."
9. check the WebSocket message flow in inspector
10. find last mesage "Failed to run stream handler: An error occurred (ValidationException) when calling the ConverseStream operation: The provided model doesn't support on-demand throughput."

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

[statefb]

@wzr1337 Thank you for your suggestion. We'd be appreciated if you could create a PR to improve UI when you have time.

[jimmyching]

HI, I also get the same error "An error occurred while responding." when after first deployment. Please help to fix that. Thanks.