"Enable reasoning" option not available

[sdbarker]

App Version

3.19.3

API Provider

bedrock

Model Used

Claud 4.0 Opus

🔁 Steps to Reproduce

View the options, notice there is no "Enable reasoning" switch. It's suspected that this might be related to consistent "Bedrock is unable to process your request" error

s when using Claude 4 Opus w/ AWS Bedrock.

💥 Outcome Summary

I expected to be able to use Claude 4 Opus, but what happened is I get consistent errors.

📄 Relevant Logs or Errors (Optional)

[dosubot]

Hi @sdbarker! I'm Dosu and I’m helping the Roo-Code team.

I was unable to find any documentation or known issues specifically about the "Enable reasoning" option not appearing in version 3.19.3, or about its relationship to the "Bedrock is unable to process your request" error.

However, I did confirm that Roo Code supports enhanced reasoning for Claude 4 models as of version 3.18, but this appears to be tied to certain providers and model variants, such as OpenRouter and specific "thinking" variants of Claude 4, rather than a universal toggle or switch in the UI. The documentation does not mention a dedicated "Enable reasoning" switch for Bedrock/Anthropic configurations in 3.19.3, so it’s possible this option is either not exposed for Bedrock, or is automatically enabled based on the selected model variant (for example, using a :thinking model) rather than a manual toggle in the UI source.

Regarding the Bedrock error, the most common causes are missing model access, incorrect model IDs, or insufficient IAM permissions. To use Claude 4 Opus via Bedrock, you must have explicit access to both Bedrock and the specific Claude model in your AWS account, and your IAM user must have the bedrock:InvokeModel permission. You must also use the correct model ID (not just the model name) when configuring Roo Code source.

If you have confirmed your AWS Bedrock access, model access, and permissions, and are using the correct model ID, but still see the error, it may be a limitation or unsupported configuration in Roo Code for this provider/model combination. There is no evidence in the documentation that the missing "Enable reasoning" option is directly causing the Bedrock error.

If you have logs or more detailed error output, sharing those may help narrow down the cause. If you have already checked your AWS and model configuration, and the issue persists, it may be an undocumented limitation or a bug in this version.

To reply, just mention my name @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[daniel-lxs]

Closing as duplicate of #4201

[hannesrudolph]

@daniel-lxs this issue also brings to light that the thread is being inturruped with an error instead of retrying, also i don't think it is parsing out the error as it should.