Join the Waitlist
Open cursor.com/origin in your browser
Enter your email in the waitlist form
Submit. You will see the confirmation: "We'll reach out when Origin is ready for you"
No app install required at this stage. Origin is pre-launch.
Table of Contents
🧠 Why Origin Exists
GitHub was built in 2008. Its entire interface (pull request diffs, inline comments, merge buttons, conflict markers) was designed for one type of user: a human developer reading text in a browser.
By 2026, that assumption has broken.
Cursor's background agents can take a GitHub issue, implement a feature, run tests, and open a pull request without a human typing a single line. One engineer now oversees dozens of agent-generated PRs per day. The bottleneck is no longer writing code. The bottleneck is the review-and-merge layer. That layer still lives on a platform designed for 2008.
Origin is Cursor's answer. It is a Git hosting and code collaboration platform built from scratch under the assumption that AI agents are primary users, not edge cases.
⚠️ Context worth knowing: GitHub's own VP Jay Parikh privately warned colleagues that Cursor and Claude Code could make GitHub's core repository service obsolete. Reported by The Information from two people who heard the remarks (May 2026). That warning came before Origin was announced.
⚡ What Origin Can Actually Do
Based on verified announcements from Cursor as of June 17, 2026. Features not yet confirmed in product documentation are marked ⏳.
You need to... | What Origin does |
|---|---|
Store and version code | Hosts Git repositories. Teams and agents push to the same forge. |
Review agent-generated PRs | Purpose-built review layer designed for machine-authored code |
Handle merge conflicts | Agent resolves conflicts automatically. Does not just flag them. Fixes them. |
Run parallel agent branches | Designed to handle many agents cloning, branching, and committing at once |
Extend with your own tools | API and MCP extensible out of the box |
Manage stacked PRs | Graphite's stacked diff workflow built into the review layer |
Handle CI failures | Agent resolution for CI failures baked in |
Migrate from GitHub | Git-compatible. Works with existing tooling. |
⚠️ Pricing: Not announced. No public figures as of June 17, 2026. Verify at cursor.com/origin before assuming anything about cost.
⚠️ Availability: Fall 2026. Waitlist only right now. Specific release date not confirmed.
✅ Before You Start
Accounts
Cursor account at cursor.com (free tier available)
Origin waitlist slot at cursor.com/origin (free to join)
GitHub account (current). You will likely migrate repos when Origin launches.
Graphite account (optional now, worth exploring) at graphite.dev
Knowledge
Understand what Git is. Clone, branch, commit, PR, merge. These are Origin's primitives.
Basic familiarity with Cursor's background agents. That is the feature that makes Origin necessary.
Understand what MCP (Model Context Protocol) is. Origin will expose an MCP interface.
Team and Org Prep
Identify which repos you would migrate to Origin first. Likely: greenfield agentic projects.
Flag any compliance or security requirements that would affect repo hosting decisions.
Note: Origin is Git-compatible, so migration risk is lower than switching version control systems entirely.
🚀
🔍 What Graphite Brings to the Table
Cursor acquired Graphite in December 2025 for "way over" its last valuation of $290M. Graphite had raised a $52M Series B. Tomas Reimers, Graphite's co-founder, presented Origin on stage at the announcement.
Graphite's core capabilities now form Origin's review layer:
Graphite Feature | What it means in Origin |
|---|---|
Stacked diffs | Break large changes into a stack of small, reviewable PRs. Agents and humans can both navigate. |
Merge queues | Serialize PRs safely so parallel agent commits do not conflict on merge |
Review flow | Structured review workflow designed for fast iteration |
PR dependency tracking | Understand which PR depends on which. Critical when agents open many simultaneously. |
⚠️ It has not been officially confirmed which specific Graphite features will ship in Origin's first release vs. later. Verify against Origin's launch documentation when available.
🛠 How to Prepare Your Agent Workflow
While Origin is in waitlist phase, you can prepare your agentic setup so you are ready to migrate immediately on launch.
Get Cursor Agents Running Now
# Install Cursor
# cursor.com/download (macOS, Windows, Linux)
# In Cursor: enable Background Agents
# Settings > Features > Background Agents > Enable
# Assign your first agent task
# Open a new chat in Cursor, type:
"Act as an autonomous agent. Take the following GitHub issue and implement a solution, run the tests, and prepare a pull request description."Structure Repos for Agent Handoffs
# Recommended repo structure for agent-friendly codebases:
# Clear AGENTS.md or CONTRIBUTING.md describing agent rules
# Automated test suite agents can run (pytest, jest, etc.)
# CI configured to block merge on failing tests
# Descriptive issue titles (agents read these as task specs)Explore Graphite Now (Pre-Origin)
bash
# Install Graphite CLI to preview the review workflow Origin will use
npm install -g @withgraphite/graphite-cli
# Authenticate
gt auth --token YOUR_TOKEN
# Create your first stacked PR
gt branch create feature/my-change
gt commit create -m "first layer"
gt submit⚠️ Graphite CLI availability and commands may change as Graphite integrates more deeply into Cursor. Check graphite.dev/docs for current documentation.
💬 Prompts to Use Right Now
These prompts work today in Cursor to prepare for an Origin-ready agentic workflow.
Audit your repo for agent-readiness
Review this codebase and tell me:
1. Which files or modules are well-suited for autonomous agent modification (clear interfaces, good test coverage)
2. Which areas are risky for agents to touch without human review (tight coupling, no tests, side effects)
3. What I should add or change to make this repo agent-friendly before I migrate to an agent-native Git platformGenerate a PR description an agent would produce
Based on the changes in the current diff, write a pull request description that:
- States the problem being solved (one sentence)
- Lists all files changed and why
- Describes how to test the change
- Flags any risks or side effects
Format it so another AI agent reviewing this PR can quickly decide whether to approveSimulate agent merge conflict resolution
Here are two branches with a conflict:
[paste branch A diff]
[paste branch B diff]
Resolve the conflict. Explain:
- What the semantic intent of each branch was
- Which resolution you chose and why
- Whether there is any information loss from the resolutionWrite an AGENTS.md for your repo
Write an AGENTS.md file for this codebase that tells an autonomous AI agent:
- What this repo does (one paragraph)
- Which directories it can freely modify
- Which directories require human approval before merging
- How to run the test suite
- The commit message format to follow
- What to do when tests fail🗺 The Stack Origin Completes
Layer | Tool | Status |
|---|---|---|
Write code | Cursor IDE | Live now |
Run autonomous agents | Cursor Background Agents | Live now |
Review and stacked diffs | Graphite workflow (inside Origin) | Acquired Dec 2025, integrated into Origin |
Host, merge, collaborate | Origin | Waitlist only. Fall 2026. |
GitHub currently owns the last row. Origin is the bet that this is the most valuable row to own in 2026.
📅 Daily Workflow (Projected for Fall 2026)
Projected based on announced features. Not confirmed until Origin ships.
Morning
Open Cursor. Review agent-opened PRs in Origin from overnight background runs.
Use Origin's review layer to approve, request changes, or merge stacked agent PRs.
Assign new tasks to agents via Cursor. They push branches directly to Origin.
During the day
Agents commit to Origin in parallel. Merge queue handles sequencing.
CI failures trigger automatic agent resolution attempts. You review the fix, not the failure.
Use MCP-connected tools to automate PR triage (route to right reviewer, tag by risk level).
End of day
Merge approved stacks.
Origin's audit trail shows which agent made which decision and why.
💡 Tips for Early Adopters
Join the waitlist with your work email. Cursor is targeting enterprise teams first. A personal Gmail may deprioritize you.
Start using Graphite now. The review workflow in Origin is built on Graphite's stacked diff model. Familiarity now means zero ramp-up at launch.
Identify your migration repo before launch. Pick one greenfield agentic project, not your production monolith, as your Origin pilot. Have it ready to push on day one.
GitHub's API is deeply embedded in most CI/CD tooling. Origin claims Git-compatibility, but confirm before assuming your GitHub Actions workflows port cleanly. This is the most likely friction point at launch.
Watch for MCP integration details. The announcement confirmed MCP extensibility. When docs drop, the MCP surface area will tell you what is actually possible.
Pricing is unknown. Do not build a business case around Origin until pricing is announced. Verify before committing.
🔧 Troubleshooting and Known Concerns
Concern | What's known |
|---|---|
"Is my code safe on Origin?" | Not yet confirmed. Cursor is SOC 2 certified but Origin-specific security documentation has not been released. Verify before migrating sensitive repos. |
"Will my GitHub Actions work?" | Origin is Git-compatible. Actions are a GitHub-specific CI layer. Plan to migrate or rebuild CI pipelines. This will be the biggest migration cost. |
"What about open source hosting?" | Not announced. GitHub's free public repo hosting is a major moat. No Origin equivalent confirmed yet. |
"Pay-per-commit pricing fears?" | Multiple community commenters flagged this concern. Cursor has not addressed pricing at all. Treat as unknown until confirmed. |
"Is this replacing Graphite's standalone product?" | Per Cursor's announcement: Graphite's brand and product are not going away. Both continue independently for now with deeper integration planned. |
"I'm on a team that uses GitHub Enterprise" | GitHub Enterprise has deep SSO, compliance, and audit features. Origin has not announced enterprise feature parity. Do not plan enterprise migration until those details are confirmed. |
⚠️ If you encounter issues joining the waitlist, try cursor.com/origin directly. If the page does not load, check @cursor_ai on X for status updates.
📋 Quick Reference
# Origin waitlist
cursor.com/origin
# Cursor IDE (prerequisite)
cursor.com/download
# Graphite CLI (preview the review workflow)
npm install -g @withgraphite/graphite-cli
gt auth --token YOUR_TOKEN
gt branch create BRANCH_NAME
gt commit create -m "message"
gt submit
gt sync
gt log
# Key announcements to track
@cursor_ai on X
cursor.com/blog
graphite.dev/blog
# What was confirmed June 17, 2026
- Git hosting and code storage
- Agent-native review layer
- Merge conflict agent resolution
- CI failure agent resolution
- API and MCP extensible
- Git-compatible
- Available fall 2026
# What is NOT yet confirmed
- Pricing
- Exact launch date
- Open source and public repo hosting
- Enterprise compliance features
- GitHub Actions migration path
- Specific agent permission model
Follow @bestapps.ai for more daily AI assets
By The AI Leverage - Learn and master AI daily