Set up Cursor
- Save an OpenRouter API key with
ori loginorori login --with-key. Setup doesn’t accept an OpenRouter OIDC sign-in. See Saved API key only. - On Linux and Windows, close Cursor. On macOS, setup quits Cursor and opens it again for you.
- Run setup:
Go back to your own Cursor setup
Run reset to remove the OpenRouter key and models and put back your previous Cursor settings. On Linux and Windows, close Cursor first.Limits
Cursor has no way to ask Ori for a fresh credential, so Ori writes one static key into Cursor’s settings. The first three limits come from that, and they apply only to Cursor. Codex, Claude, Droid, and Pi get their credential from Ori on each request.Saved API key only
Cursor stores one static key. If you signed in with OpenRouter OIDC (ori login --oidc), setup stops with ORI_CLI_HARNESS_CREDENTIAL_UNSUPPORTED, because an OIDC access token expires.
Requests go through Cursor
Cursor sends your key and every request through its own servers before they reach OpenRouter.Logout doesn’t remove the key
ori logout leaves the key in Cursor. Run ori harness reset cursor to remove it.
Fixed model list
Setup writes your organization’s model list once. If your organization changes which models it allows, runori harness setup cursor again. Factory Droid setup has the same limit.
Not available yet
- Cursor CLI: Setup doesn’t cover the Cursor CLI (
cursor-agent). - Launching from Ori: There is no
ori cursorcommand. Open Cursor as usual after setup. - Automatic restart on Linux and Windows: Setup and reset stop with
ORI_CLI_HARNESS_ALREADY_RUNNINGwhile Cursor is running. Close Cursor and run the command again.