Cursor Login

Authorize Cursor Desktop or CLI login requests, inspect Cursor User Token usage, and parse account exports locally in the browser.

Web

Hosted interface: curgo.vercel.app

The Web interface contains three tabs:

• Login authorization approves a pending Cursor Desktop or CLI login.
• Token inspection checks whether a User Token is active and displays quota, on-demand status, hard limit, and paginated usage events.
• Batch processing extracts one or more email----email password----Cursor password----User Token records from noisy text, highlights malformed or duplicate records, filters the result, checks selected Tokens, and exports the selected credentials. Parsing is local and never checks a Token until the user explicitly requests it.

Token inspection shows the independent Cursor Models and Other Models usage pools reported by Cursor, plus their combined usage. When Cursor omits bucket amounts for the recognized $900 tier, the interface estimates the $700/$200 split from Cursor's reported percentages and labels it as estimated. Usage events show the model, token counts, usage value, and actual charged amount.

The browser sends login and inspection requests to the deployment's same-origin Vercel Function. Batch parsing itself is local; batch inspection sends only each selected User Token, never the parsed email or passwords. The application code does not persist submitted values or place them in URLs, browser storage, or application cookies. The Function sends the User Token to Cursor as the required WorkosCursorSessionToken Cookie header.

Deploy to Vercel

The npm CLI and Vercel Web application live in this repository and share the same Cursor request implementation.

bun install
npx vercel login
npx vercel --prod
npx vercel alias set <production-deployment-url> curgo.vercel.app

For local Web development:

npx vercel dev

CLI

Run without a global installation:

npx cursor-login

The interactive menu offers:

• Authorize Cursor login
• Inspect User Token

The authorization flow asks for the Cursor login URL and User Token, then sends one approval request. The inspection flow shows the account state, separate Cursor Models and Other Models pools, their combined usage, on-demand status, hard limit, and paginated usage events. User Token input is hidden in the CLI.

Run inspection directly:

npx cursor-login --inspect-token

Read a User Token from a private file:

chmod 600 ./token.txt
npx cursor-login --inspect-token --token-file ./token.txt

--check-session remains an alias for --inspect-token.

Development

bun install
bun run typecheck
bun run test
bun run build
bun run test:dist

Inspect the npm package contents:

npm pack --dry-run

Inspect the files Vercel would upload after linking the project:

bun run deploy:dry

Publishing

npm login
npm publish --access public

The npm files allowlist includes only the bundled CLI, this README, and the license. Web and Vercel Function source files are not shipped in the npm package.

Notes

• Token inspection uses Cursor Web Dashboard endpoints and does not log the account into Desktop or CLI.
• Cursor Desktop and CLI use the same approval endpoint; the login URL identifies the client waiting for the result.
• Approval requests use manual redirect handling and are never retried automatically. An interrupted approval has an unknown outcome; check Cursor before generating a new login request.
• The local CLI uses the local network. The hosted Web interface sends requests through the selected Vercel deployment.
• These Cursor endpoints are not documented as stable public APIs and may require updates when Cursor changes them.