I use a cursor for both work and home. At work, I switch between the Bedrock API and Cursor models (Grok, Composer). However, when I have Bedrock turned on, I am unable to use Cursor models with an error: This model does not support custom API keys.
Could we add a feature that lets me use both Bedrock API key models with Cursor and non-Bedrock models without having to switch Bedrock off every time?
Request ID: xxxxxxx-xxxxxxxxx-xxxxxxxxx-xxxxxxxxx
{“error”:“ERROR_BAD_REQUEST”,“details”:{“title”:“Bad Request”,“detail”:“This model does not support custom API keys.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:,“analyticsMetadata”:{“actionRequired”:“config”}},“isExpected”:true}
Bad Request This model does not support custom API keys.
ActionRequiredError: Bad Request This model does not support custom API keys.
Grok and Composer are Cursor-hosted models, so they cannot use a custom API key, including AWS Bedrock. With the Bedrock toggle on, those credentials still get sent, and the request is rejected with “This model does not support custom API keys.”
For now, open Cursor Settings > Models, turn AWS Bedrock off when you want Grok or Composer, and turn it back on when you want a Bedrock model. You can leave the credentials saved.
Using both without toggling is a fair request and we are aware of it. I don’t have a timeline to share, but I’ll post here if that changes.
