Since the last two updates, AWS Bedrock integration has completely stopped working.
Affected versions:
2026.06.03-0bbb28e
2026.06.04-5fd875e (latest)
What’s broken:
Bedrock support appears to have been fully broken — the /bedrock command is no longer available in the CLI at all. Previously it was accessible as expected, but after updating it simply doesn’t show up as a valid command.
Steps to Reproduce
Update to either of the versions listed above
Open the CLI
Type /bedrock — the command is not recognized / doesn’t appear in autocomplete
Expected Behavior
/bedrock command should be available in the CLI and AWS Bedrock models should function as they did in prior versions.
You’re not doing anything wrong here. This is a possible regression on our side: a recent change stopped the /bedrock command from registering in the CLI, which is why it no longer appears in autocomplete. It isn’t specific to your setup, and re-logging in won’t bring it back.
We’ve identified the cause and a fix is in progress. There isn’t a reliable client-side workaround in the current CLI builds, so the best path for now is what you’re already doing - using Bedrock models in the Cursor desktop app, which isn’t affected. Once the fixed CLI version ships, /bedrock should come back automatically after you update.
I’ll follow up here as soon as the fix lands in a CLI release. Sorry for the disruption in the meantime.
Please bake some unit/integration tests into the release pipeline this time, for the love of god.
We are seeing constant regressions with the Bedrock integration. A couple of updates ago, Bedrock models stopped appearing in the /model list entirely. We waited for a fix, and now with the latest update, the /bedrock option itself is completely gone.
This is breaking production workflows for teams relying on AWS infrastructure. Can we please get automated regression tests so AWS/Bedrock configurations stop breaking every few patch releases?
Thanks for the detail here, and sorry this is disrupting your CLI workflows. When the CLI is how you run the agent, the desktop app isn’t a real substitute, so I understand the urgency.
To confirm: this is a known regression on our end, not anything in your configuration. The missing /bedrock command (and the earlier issue where Bedrock models dropped out of the /model list) come back to the same underlying cause, and we’ve identified the fix internally. It isn’t in a released CLI build yet, so updating won’t bring it back just yet. I don’t have a firm ETA to share, but I’ll post here the moment the fixed CLI version ships so you can update right away.
On regression coverage for Bedrock specifically - that’s a fair ask, and I’m raising it alongside this bug so it gets the right attention.
