0
Add support for Cursor Origin
Source: getsentry/sentry#123992 · opened by @bruno-garcia
Problem Statement Cursor has added support for their own SCM provider During hackweek, I got it working end to end with Sentry and Seer. Including Autofix PRs Here are the related PRs: 1. Sentry PRs: 2. [getsentry/scm-platform#130]( In the process I found a few gaps, which would be blocker for real prod access. <details><summary> Summary of gaps </summary> <p> <html><head></head><body><h1>Where the Origin API makes us work around it</h1> <p><strong>Sentry · Cursor Origin integration</strong></p> <p>We built a Sentry integration against Origin — repositories, stack-trace linking, commit tracking, webhooks, and our AI debugging agent. Most of it maps cleanly onto your API. This is the honest list of where it doesn't: what we do instead, what it costs, and what each change would let us delete.</p> <blockquote> <p><strong>For:</strong> the Origin team · <…
No pledges yet. Be the first to back this.
Comments
Similar requests
Use the original baseline for % based alerts
0 votes · 0 comments
Feature Request: API Endpoint for originally accepted Events with environment data
1 vote · 0 comments
Okta imports Sentry teams with their original name
0 votes · 0 comments
Send stacktraces for an issue as a thread message to the original Issue Alert
0 votes · 0 comments
Show total match count on Replays list page
0 votes · 0 comments
No comments yet.