Mechanism: A team makes an app Public, submits a description and demo video, and Cursor reviews it before the app becomes Listed; Public status alone allows direct-link installation but does not put the app in the marketplace. Why now: The documented submission flow marks a move from Origin’s repository-hosting role toward a platform boundary where outside tools can connect to team workflows.
The source says submissions require a demo video of about five to ten minutes and a detailed app description. It asks demos to cover installation, consent to default scopes, and uninstall behavior. It also distinguishes Private, Public, and Listed visibility states. These Observed facts: the submission requires a publicly viewable demo video of roughly five to ten minutes; approval by Cursor is required for marketplace listing. First implication: Origin’s extension surface is permissioned and curated rather than self-publishing. First watch condition: Whether the listed apps expose useful, repeatable workflow connections beyond installation and permission handling.
Evidence boundary: Cursor’s documentation establishes the process and its stated requirements, but does not establish how many apps are currently listed, how quickly reviews occur, or whether the catalog materially increases adoption. It also does not verify the reported count of more than 20 integrations. The distinction between direct installation and marketplace listing matters: Public apps can be installed by link, while marketplace visibility follows approval. The next evidence to watch is actual listed app coverage and examples of teams using those apps in production.