Skip to content
Bookmarkit
All news
Cursor|Update··Abhishek Kapoor

Cloud Agents can start without GitHub. Cursor Origin is where the repo lands

On 27 August 2026, Cursor let Cloud Agents start from a prompt and save to an Origin repo. Origin is still an early paid-plan beta. The editor, the agent, and the host can now sit on one vendor.

Two repository trees meeting in a dark editor chrome, one labeled as a mirror and one as the source
Summarize this page with AI

On 27 August 2026, Cursor wrote that Cloud Agents no longer need GitHub or another source-control host to start. You prompt first. Then Create repo writes a private or internal Origin repository. That is the week’s news. The 17 August launch only opened the forge.

Cursor launched Origin on 17 August 2026 as an early beta on paid plans: repos, pull requests, code browsing, and GitHub sync. Cursor said agent-native features would ship later. As of 5 September 2026, Origin docs and cursor.com/origin still say early beta. There is no standalone Origin price and no Bookmarkit software profile. Keep it under Cursor.

VentureBeat noted a GitHub incident the morning Origin began rolling out. GitHub’s own post later said that outage lasted 7 hours and 47 minutes and hit github.com, authentication, Actions, APIs, pull requests, issues, and Copilot. VentureBeat found no evidence Cursor timed the launch. Treat the overlap as context, not a conspiracy.

What 27 August actually shipped

  • Start from scratch in the Cloud Agent repo picker. Cursor says it creates an Origin repo in the background while you prompt.
  • Create repo later, with a custom or suggested name, and private or internal visibility.
  • Port-forward from the cloud agent into the browser for a live preview, including design mode.
  • Publish to a live URL requires a connected Vercel account. Cursor says that explicitly.

Put this next to the September coding-agent shortlist when you score Cursor as editor plus host, not as a chat pane.

Two kinds of repo, two sources of truth

Origin-hosted repos treat Origin as the source of truth. Pushes land on Cursor. GitHub is not in the path. Synced GitHub repos keep GitHub as the source of truth. Origin mirrors them. Pull-request comments on synced repos travel both ways. Cursor’s changelog is explicit about that split. Mixing the two in one org without a written rule is how you get two histories.

  • Paid plans only. The free plan is out. Enterprise admins can opt out.
  • Day-one apps: Vercel preview deploys on pull requests, plus Depot and Buildkite for CI. Depot and Buildkite can run existing GitHub Actions workflows.
  • Agents can answer questions, edit, update pull requests, or push a branch from the same Codebase tab.
  • The API and the app ecosystem are also early beta. Cursor tells integration authors to read the current spec.

What to ask before you move a default remote

  1. Which repos will be Origin-hosted, and which will only sync from GitHub? Write the rule down.
  2. Who can create a codebase name? That name becomes part of the URL at cursor.com/codebase/…
  3. What happens to audit logs, SAML, and required reviews if Origin is the source of truth?
  4. If you already standardized on GitHub for CODEOWNERS and rulesets, does a sync preserve the controls you actually use?
  5. Compare the same workflow on GitHub plus Claude Code or OpenAI Codex before you move the default remote.