Cursor Opens Its Origin App Marketplace to Public Submissions, Listing Over 20 Apps for CI, Code Review and Security
Cursor says its Origin git forge now integrates with over 20 apps, and any team building developer tools can submit one; Origin remains in early beta.
Overview
Cursor said in an October 13, 2026 changelog entry that Origin, its git forge, “now integrates with over 20 apps for deployments, CI, code review, security, monitoring, and project management, from partners including Cloudflare, Linear, Sentry, and Socket Security.” The same entry says that “Starting today, the marketplace is also open to public submissions, so any team building developer tools can publish an app for Origin.”
What Origin Is
Per Cursor’s documentation, “Origin is Cursor’s git forge for storing and sharing code.” The same page says Origin is “currently released in early beta” and that in the beta users can create repositories, push and pull with git, mirror from GitHub, browse and search code, and open and merge pull requests. It also lists “Connect automations and cloud agents to Origin repos” among the things a team can do.
Which Apps Are Listed
The changelog entry groups the marketplace apps by category:
- Deployments: Cloudflare, Netlify, Render, Spacelift and Vercel
- CI: Buildkite, CircleCI, CloudBees, Depot, EngFlow, Namespace and RWX
- Code review: CodeRabbit, Greptile and Tenki
- Security: Artemis Security, Semgrep, Socket Security and Upwind
- Monitoring: Sentry
- Project management: Linear
By the Herald’s own count, that is 21 apps. Cursor’s Origin Apps documentation shows the same categories but lists one more CI app, Tuist, which makes 22 by the Herald’s own count.
The documentation also sets a limit: “Origin apps work only on Origin-hosted repositories, not on repositories mirrored from GitHub.” It adds that “Mirrored repositories keep their CI and integrations on GitHub.”
How Developers Submit an App
According to the changelog entry, an app is created in the developer’s namespace, where “It stays private to your namespace while you build.” Apps are built against the Origin API; the entry says “Apps authenticate with an app JWT and installation access tokens, receive webhook events, and write back check runs, pull request comments, and reviews.”
A developer then makes the app public and submits it from the app’s page with a slug, suggested tags and a demo video. The entry says the video “should show install, uninstall, and your core product flows.” The entry adds: “We review the submission and list the app once it’s approved.”
The publishing guide describes three visibility settings. A private app can be viewed and installed only from its own namespace. A public app can be installed by any Origin team from a direct link, but “It isn’t listed in the marketplace until Cursor approves it.” A listed app appears in the marketplace. The guide asks for a demo video of “about 5 to 10 minutes” and states that “Cursor reviews every submission.”
A Third-Party Integration Example
A Jenkins plugin shows what building against Origin looks like in practice. The Cursor Origin Branch Source plugin repository says the plugin “allows you to use Jenkins to run CI on Cursor Origin Git repositories.” Its README warns that because Origin is in early beta, the plugin may be broken at any time by service changes. The README says build status is reported back to Origin through support for the Checks API plugin, and that pointing a webhook at a Jenkins URL means Jenkins does not “need to poll for changes.”
The README also observes that “Origin does not seem to have a concept of forks like GitHub, so pull requests are from branches within the same repository.”
What We Don’t Know
The sources reviewed do not say how many outside developers have submitted apps since the marketplace opened, how long Cursor’s review takes, or when Origin will leave early beta. The changelog entry does not state the criteria Cursor uses to approve an app beyond the demo-video and description requirements in the publishing guide.