Install the Cursor CLI
- Open Settings → Code Harnesses → Cursor and follow Install Cursor CLI if it is missing.
- Review the installer and alias-collision disclosure, then choose Download and run it.
- Wait for installation and detection. If it fails, inspect the error before Try again, or use Open install docs.
- For manual recovery, follow the official Cursor CLI installation instructions for your native OS. The provider documents both shell and Windows PowerShell installation.
- Fully quit and reopen Rudr after an external installation. Verify the provider-specific
cursor-agentexecutable is available to the app. The upstream guide uses the genericagentalias; Rudr intentionally launchescursor-agentto avoid confusing another tool’s executable.
Complete account setup
- Choose Cursor account.
- Choose Set up Cursor and complete the CLI-owned login in your default browser. The official authentication guide describes the underlying browser and API-key methods.
- Return to Rudr and let the setup status refresh. If already signed in but not enabled, choose Complete Cursor setup.
- Complete the usage connection and look for Cursor setup complete. A fresh usable usage response is required by this enablement path; Cursor account connected alone is insufficient.
- Save settings and verify Cursor is enabled and a model is available before trying a new task.
Signing out affects the CLI account outside Rudr and clears Rudr’s local Cursor enablement. Review that confirmation before proceeding.
API-only access and limits
A Cursor API key route is available, with key configuration under Models. An API key alone does not bypass Cursor’s readiness checks. Confirm that Cursor is enabled and a model is available in Code before sending a task. If the provider remains disabled, complete the account setup above or report the setup problem.
If account login succeeds but usage connection fails, include both results in a problem report.