Add Cursor Cloud Agents AI provider support - #64
Conversation
|
Warning Review limit reached
Next review available in: 22 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughThis change adds Cursor Cloud Agents as a separate AI provider. It adds agent execution, provider normalization, connection probing, settings UI updates, tests, pricing defaults, and documentation for Cursor Cloud and OpenAI-compatible gateways. ChangesCursor Cloud Agents integration
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant SettingsUI
participant API
participant CursorCloud
SettingsUI->>API: Save Cursor provider and test connection
API->>CursorCloud: Probe /v1/me with configured key
CursorCloud-->>API: Return account and model information
API-->>SettingsUI: Return provider, model, base URL, and sample
Possibly related PRs
Suggested reviewers: ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Wire dashboard crsr_ keys to the Cloud Agents API using short-lived no-repo agents for digests and drafts. Split OpenAI-compatible gateways into a separate provider, with legacy cursor+gateway settings mapped automatically. Test probes /v1/me for fast key validation. Co-authored-by: Damon <Modsofthenation@users.noreply.github.com>
Co-authored-by: Damon <Modsofthenation@users.noreply.github.com>
d59b36d to
6dbf3bf
Compare
Summary
Settings → AI can now use Cursor Cloud Agents with dashboard
crsr_…keys. Digests and drafts launch a short-lived no-repo agent viahttps://api.cursor.com/v1(not OpenAI chat completions).Changes
cursorCloud.tsclient: create agent → poll run → returnresult→ archivecursor) uses that path; models blank = account defaultopenai_compatible)provider=cursor+ gateway URL still maps to OpenAI-compatible until re-savedGET /v1/me(fast key check)Notes
Cloud Agents are slower than Anthropic/OpenAI chat (async agent runs). Prefer those for interactive writing-desk latency; Cursor is for users who already have Cursor API keys.
Verification
pnpm --filter @prm/api exec node --import tsx --test src/ai.cursor.test.ts(7 pass)pnpm --filter @prm/api typecheckpnpm --filter @prm/ui typecheckSummary by CodeRabbit
New Features
Bug Fixes
Documentation