Command reference ยท Cursor CLI
/bedrock
Configures AWS Bedrock as the model backend, if the Bedrock feature is enabled.
/bedrock [subcommand] configures AWS Bedrock as the model backend for the Cursor CLI. According to the reference table, the command only works if the Bedrock feature is enabled for your account โ if not, it has no effect.
According to Cursor's changelog, you use it to set up Bedrock "with your own credentials": either via classic AWS access keys or via a team IAM role. According to the changelog, the setup applies across the board โ it works in interactive sessions as well as in headless mode and in editor integrations, so you don't have to configure Bedrock separately for each mode.
/bedrock is intended for setups where model requests should run over your own AWS infrastructure instead of Cursor's standard backend, for example for compliance or cost reasons in an enterprise environment.
โ WHEN TO USE IT?
Set up Bedrock with your own AWS credentials
/bedrock โ store your own access keys so model requests run over your own AWS infrastructure
Team-wide Bedrock connection via an IAM role instead of individual keys
Use /bedrock in an enterprise context to instead store a team IAM role
โ WHEN NOT TO?
The Bedrock feature isn't enabled for the account
According to the docs, /bedrock only works if the Bedrock feature is enabled.
Better: Choose a model regularly via /model, or request Bedrock access from the Cursor team
It's enough to briefly test a different default model
/bedrock is intended for a permanent backend configuration, not for a quick model switch.
Better: Use /model or a model shortcut like /composer
SOURCES
- Cursor Docs โ Slash Commands โ cursor.com
- Cursor Docs โ Changelog โ cursor.com