The Rundown AI homepage

Independent tool overview

Origin at a glance

Cursor Origin is an active, early-beta code-hosting service built into Cursor for repositories, standard Git operations, pull requests, code search, GitHub mirroring, cloud agents, automations, and CI or deployment apps. It began rolling out on August 17, 2026 to paid Cursor plans. Cursor has not announced a separate Origin fee, repository allowance, or storage price; access currently follows the eligible Cursor subscription.

Visit the official Origin site ↗
Origin product preview
Status
Active early beta
Released
August 17, 2026
Best for
Cursor teams testing agent-native code hosting
Access
Eligible paid Cursor plans
GitHub behavior
Real-time mirror; GitHub remains source of truth
Separate Origin price
None publicly announced

Overview

What Origin is

Origin is Cursor's new git forge: teams can create repositories hosted by Cursor or place real-time GitHub mirrors beside them in the Codebase tab. Native Origin repositories use standard clone, push, pull, branch, and pull-request workflows, while the browser adds source browsing, search, reviews, checks, settings, and direct access to Cursor agents.

The GitHub path is deliberately conservative. GitHub remains the source of truth for repositories that began there, pushes continue to GitHub, and pull-request comments, replies, reviews, and merges synchronize between the two systems. A repository can later be detached, which stops synchronization and turns the Origin copy into a standalone Cursor-hosted repository without altering the GitHub source.

Origin's appeal is proximity: code, pull requests, cloud agents, automations, and Cursor's coding interface live in one workspace. Its biggest drawback is maturity. The product is in early beta, integrations and protections are still expanding, and Cursor has not yet published the operational limits buyers normally expect from an established primary code host.

Use cases

Who Origin is best for

The strongest fit depends on the job you need the product to complete, not the size of its feature list.

Cursor-native repositories

Host new projects where agents, source browsing, pull requests, and Cursor's cloud workflows share one codebase context.

Low-risk GitHub evaluation

Mirror selected GitHub repositories into Cursor while keeping GitHub as the authoritative remote and existing CI system.

Agent-generated changes

Let Cursor agents inspect code, create branches, update pull requests, and propose changes beside the repository they are working on.

Integrated preview deployments

Connect Vercel to create pull-request previews and production deployments from an Origin repository.

Teams exploring agent-scale review

Test how a forge designed around cloud agents and automations changes repository browsing, review, and merge workflows.

Capabilities

Core Origin features

1

Native Origin repositories

Create a repository from the Codebase tab, CLI, API, or Cursor agent and use standard git clone, push, and pull over HTTPS.

2

GitHub mirroring

Select repositories to mirror in Cursor, receive updates in real time, and keep GitHub as the source of truth until an explicit detach.

3

Pull-request workflow

Open, review, comment on, inspect checks and diffs for, merge, close, or reopen pull requests in the browser or Origin CLI.

4

Code browsing and search

Browse repositories and search source from cursor.com/codebase without cloning every project locally.

5

Agents in each repository

Ask questions about the open codebase, request changes, update a pull request, or push an agent-created branch.

6

Automations and cloud agents

Connect Cursor's background development workflows directly to eligible Origin codebases.

7

Vercel, Depot, and Buildkite apps

Add preview deployments or CI to native Origin repositories; GitHub mirrors continue to use their GitHub-side CI configuration.

8

Permissions and protections

Choose Internal or Private visibility, manage repository and codebase access, and configure the branch rules and merge protections currently available in beta.

9

Origin CLI and REST API

Manage repositories, pull requests, rulesets, SSH keys, apps, installations, checks, scopes, webhooks, and rate limits programmatically.

Process

How the Origin workflow works

  1. Step 1

    Start with a GitHub mirror

    Mirror a non-critical repository first so GitHub remains authoritative while the team evaluates browsing, reviews, agents, permissions, and sync behavior.

  2. Step 2

    Match access deliberately

    Review who can access the Cursor codebase, choose Private or Internal visibility, and avoid assuming GitHub permissions map perfectly to Origin settings.

  3. Step 3

    Validate synchronization

    Test pushes, comments, reactions, assigned reviews, checks, merges, branch updates, and disconnect behavior in both directions.

  4. Step 4

    Keep existing CI initially

    Leave mirrored repositories on their GitHub CI path and verify status checks before moving a new native Origin project to Depot or Buildkite.

  5. Step 5

    Constrain agents and apps

    Use minimum repository permissions, branch rules, required checks, short-lived tokens, signed webhooks, and human review before merge.

  6. Step 6

    Maintain an exit path

    Keep a second remote or automated backup, document repository export and detach procedures, and do not make the beta the only copy of critical source.

  7. Step 7

    Reassess before migration

    Wait for proven reliability, required integrations, protection controls, support terms, usage limits, and security documentation before making Origin the system of record.

Cost

Origin pricing and free plan

Origin is rolling out on eligible paid Cursor plans without a separately published hosting charge. Cursor has not publicly itemized repository counts, storage, transfer, LFS, or additional Origin usage fees. Agent and model consumption remains subject to the usage pools and on-demand pricing of the underlying Cursor plan.

Start — India

₹649/month, tax included

Regional entry plan eligible to create Origin repositories and use Cursor's own model pool.

  • Available only in India
  • Origin eligibility is documented in the API
  • Cloud Agents included
  • No third-party model pool or on-demand model usage

Pro

$20/month

Lowest globally listed individual plan included in Origin's paid-plan rollout.

  • Cursor Models and third-party model pools
  • Cloud Agents and Bugbot
  • On-demand model usage available
  • No separate Origin fee published

Pro Plus

$60/month

Individual plan for heavier daily agent usage.

  • Larger included usage than Pro
  • Cloud Agents and Bugbot
  • Origin access during the paid-plan beta rollout
  • Model choice affects how quickly included usage is consumed

Ultra

$200/month

Highest published individual plan for power users running many agents and automations.

  • Largest individual included usage pool
  • Cloud Agents and Bugbot
  • Origin access during beta rollout
  • On-demand usage can add cost beyond subscription

Teams

$40 or $120 per user/month

Standard and Premium seats for collaborative Cursor and Origin use.

  • Centralized team administration
  • Team rules, skills, plugins, cloud agents, and automations
  • Privacy mode enforcement and SSO
  • Premium includes five times the usage of Standard

Enterprise

Custom

Contract plan for larger organizations, subject to administrator Origin controls.

  • Pooled usage, invoicing, SCIM, and advanced controls
  • Origin can be disabled by an enterprise admin
  • Legacy Privacy Mode can make a team owner ineligible for Origin writes
  • Confirm beta eligibility and support terms in the agreement

Pricing checked . Check current pricing at the source ↗

Assessment

Origin strengths and limitations

Where it stands out

  • Native repositories put source, pull requests, agents, and Cursor cloud workflows in one interface.
  • Standard git operations and a dedicated CLI reduce dependence on a proprietary editing workflow.
  • GitHub mirroring provides a lower-risk evaluation path without immediately moving the source of truth.
  • Pull-request discussion syncs between Cursor and GitHub within seconds according to the launch documentation.
  • Vercel previews and Depot or Buildkite CI cover important initial deployment and check workflows.
  • Internal and Private repository visibility support team-wide and restricted projects.
  • The public API uses scoped installations, short-lived tokens, signed webhooks, and documented rate limits.
  • No separate Origin add-on fee has been announced for eligible paid Cursor subscribers.

What to consider

  • Origin is an early beta released only days before this review, so reliability and operational maturity are not yet independently established.
  • Free Hobby users are not included in the paid-plan rollout.
  • Cursor has not published repository, storage, bandwidth, LFS, retention, backup, availability, or support limits specific to Origin.
  • The branch-protection and permission interfaces are still being redesigned, and available controls may expand during beta.
  • GitHub mirrors are copies, not a replacement source of truth; pushes and CI continue through GitHub until the repository is detached.
  • Depot and Buildkite integrations work only for native Origin repositories, not GitHub mirrors.
  • The initial app ecosystem is limited to Vercel, Depot, and Buildkite compared with established code-hosting marketplaces.
  • The partner API cannot create repositories or list them namespace-wide and lacks several first-class reviewer, thread, and compare operations.
  • Mirrored repositories can become read-only during synchronization transitions, and API clients must treat a 403 response as authoritative.
  • Agent changes and automated merges still require branch rules, checks, least privilege, and human review.
  • Making a new beta forge the only copy of critical source increases vendor, outage, recovery, and migration risk.

Compare

Origin alternatives

The right alternative depends on the specific output, workflow, controls and budget your project requires.

Coding

GitHub Spark

Choose GitHub's ecosystem when established repository hosting and marketplace depth matter, with Spark available for prompt-built applications.

Explore GitHub Spark

Coding

Replit Agent 4

Consider Replit Agent 4 for an integrated cloud development and hosting environment centered on autonomous app creation.

Explore Replit Agent 4

Coding

Claude Code Review

Use Claude Code Review when the primary need is multi-agent pull-request analysis rather than moving repository hosting into Cursor.

Explore Claude Code Review

Questions

Origin FAQs

What is Cursor Origin?

Origin is Cursor's early-beta git forge for hosting repositories, mirroring GitHub, browsing code, reviewing pull requests, and connecting agents, automations, CI, and deployments.

How much does Cursor Origin cost?

Cursor has not announced a separate Origin fee. The beta is rolling out to eligible paid Cursor plans, starting at Pro for $20 per month globally and Start for ₹649 per month in India.

Is Origin available on Cursor Hobby?

No. Cursor says Origin is rolling out to paid plans. The free Hobby plan is not included in the published eligibility list for creating repositories.

Does Origin replace GitHub?

It can host new repositories directly, but a repository synced from GitHub remains a mirror. GitHub stays the source of truth and receives pushes until you explicitly detach the Origin copy.

Can Cursor agents modify Origin repositories?

Yes. Agents can answer code questions, make changes, push branches, and update pull requests, subject to repository access, rules, checks, and plan usage.

Can Origin run CI and preview deployments?

Yes. Vercel supports deployments and pull-request previews. Depot and Buildkite run CI for native Origin repositories; mirrored repositories keep CI on GitHub.

Can I make an Origin repository private?

Yes. Private repositories are limited to explicitly granted members or codebase permissions, while Internal repositories are visible to eligible members of the Cursor team.

Should I migrate a production repository now?

A mirror of a non-critical repository is the safer first step. Wait for required protections, integrations, limits, support, reliability evidence, and an independently tested backup and recovery path before making Origin authoritative.

Bottom line

Our Origin verdict

Origin is a strategically coherent addition to Cursor: agents work best when code, branches, pull requests, checks, and context are close together. The GitHub mirror makes evaluation practical, and eligible paid users can test it without a separately announced hosting fee. But this is still a very new beta. Keep GitHub authoritative at first, retain an external backup, and treat published operational limits, security controls, integration coverage, and recovery evidence as prerequisites for a production migration.

Visit Origin website ↗
The Rundown University

AI training for the future of work.

Get access to all our AI courses, hundreds of real-world AI use cases, live expert-led workshops, an exclusive network of AI early adopters, and more.

AI Courses

Get unlimited access to all of our current & upcoming industry-specific AI courses for the duration of your subscription.

Daily Guides

To keep up with the rapid pace of AI, our team publishes AI implementation guides daily. Our library contains 300+ practical use cases to automate real-world work.

Workshops

Join weekly, live, interactive sessions with industry leaders who are at the forefront of AI for hands-on implementation guidance and exclusive insights.

Community

Network with an exclusive community of AI-first professionals who are working smarter with AI. Learn how early adopters are using AI in their work and businesses.