Cursor Opens Over 20 Integrations for Origin Code Hosting Platform
Cursor announced that its code hosting platform Origin now supports over 20 integrations, allowing repositories to connect to CI, deployment, code review, security, monitoring, and project management tools. The application marketplace is now open for public submissions, enabling any development tool team to publish applications.
The current applications in the marketplace cover categories including: deployment tools such as Cloudflare, Netlify, Render, Spacelift, and Vercel; CI tools including Buildkite, CircleCI, CloudBees, Depot, EngFlow, Namespace, and RWX; code review tools like CodeRabbit, Greptile, and Tenki; security tools such as Artemis Security, Semgrep, Socket Security, and Upwind; monitoring tools like Sentry; and project management tools like Linear.
Applications are authenticated via the Origin API, using application JWTs and installation access tokens, and can receive webhook events, as well as write back check runs, pull request comments, and reviews. Developers must first create private applications in their namespace, and after completion, submit them for public review; once approved, they will be listed in the marketplace for all Origin teams to install.
Origin is Cursor's git forge, supporting repository creation, GitHub mirroring, code browsing, and opening and merging pull requests, and can be used in conjunction with Cursor automation and cloud proxies. The cloud proxy can perform clone, branch, commit, and push operations on Origin repositories; pull requests created on Origin can be directly opened.
The opening of the application marketplace allows third-party tools to directly integrate into the Origin repository workflow. Events are driven by official announcements from Cursor. Teams using Origin gain direct connections to CI, deployment, and security tools, reducing the need for cross-platform switching; development tool vendors gain distribution channels through the marketplace, while users relying on other code hosting platforms face migration or dual maintenance costs.
Source: Public Information
ABAB AI Insight
Cursor launched Origin as its own git forge in August 2026, initially supporting repository creation, GitHub mirroring, and pull requests. The opening of the application marketplace expands the number of integrations to over 20, covering deployment, CI, code review, security, monitoring, and project management, and allows third parties to enter the market through public submissions.
Resources are shifting from Cursor's proprietary proxies and automation to standardized access for third-party applications. Applications authenticate via the Origin API using JWTs and installation tokens, receiving webhooks and writing back checks and comments; developers must submit demo videos and pass reviews before going public. The marketplace categories clearly cover the complete chain from code pushing to deployment and security scanning, allowing Origin repositories to directly trigger external CI and preview deployments.
Following a construction path similar to GitHub Marketplace or GitLab integration ecosystems, Cursor is expanding code hosting from proprietary tools to a platform that can integrate third-party workflows. It is currently transitioning from early beta basic functionalities to an open application ecosystem, with the combination of Origin and cloud proxies and automation making repositories the entry point for proxy operations.
This essentially represents a restructuring of the industry chain. AI coding proxies require a complete code hosting and workflow environment, as a single editor is insufficient to cover CI, deployment, and security stages. This change occurs because the code generated by proxies requires ongoing review, deployment, and monitoring support; opening the application marketplace allows third-party tools to directly access Origin repositories, expanding code hosting from a storage layer to an orchestrable workflow node.
ABAB News · Cognitive Laws
The next layer of code hosting platforms is standardized access to application marketplaces
Proxy workflows require a complete toolchain from repository to deployment
The public submission mechanism determines the expansion speed of the third-party ecosystem