What Cursor Origin is
Cursor announced Origin on 16 June 2026 and opened an early beta on 17 August 2026 for Pro, Teams and Enterprise plans. It is a Git-compatible code hosting platform that lives in a Codebase tab inside the Cursor editor, with repository creation, stacked pull requests, merge queues, browser-based code navigation and MCP and API extensibility. Repositories can be mirrored from GitHub and kept in sync, with GitHub remaining the system of record for those projects.
What Nool adds
A forge merges what it is given. Nool decides what should be given. Before an agent edits shared code it announces intent and leases scope, so two agents in parallel worktrees cannot silently overwrite each other. At proposal time Nool computes semantic blast radius, checks architectural invariants and runs policy gates. Only proposals that pass are solidified into a signed ledger and pushed to your Git host, whether that is Origin or GitHub.
Where they differ
Text versus semantics. Merge queues and stacked pull requests resolve conflicts at the level of Git text. Nool checks whether two changes are compatible at the level of the code's structure and the declared intent, which is where agent-produced conflicts usually hide. In the independent coordination benchmark Nool matched git worktrees on throughput while adding that governance layer.
Using them together
Keep Origin, or GitHub, as your forge. Add Nool to the agents that push to it. Nool's CLI runs in Cursor's terminal and its MCP server is available to Cursor agents, so proposals are gated before they become pull requests in Origin's queue. Setup is the same as for any remote: run nool init on the repository, keep origin pointing at Origin or GitHub, and let agents propose through Nool from Cursor's terminal or through the MCP server. Solidified knots mirror to Git and push as ordinary commits, so nothing about Origin's stacked pull requests or merge queue changes; they simply receive changes that have already passed the envelope check and the policy gates.
When to choose which
Choose Origin when what you need is a forge that lives inside Cursor: repositories, stacked pull requests, merge queues and review without leaving the editor, on Cursor's paid plans. Choose Nool when what you need is governance before the push: scope leases for parallel agents, semantic conflict detection, policy gates and signed evidence, on whichever forge you already use. Choose both when your team lives in Cursor and runs several agents at once; Nool gates the proposals and Origin merges what passed. The one thing not to do is expect a merge queue to catch a semantic conflict, because it orders text merges and does not inspect meaning.
Cursor Origin vs Nool, side by side
| Criterion | Cursor Origin | Nool |
|---|---|---|
| What it is | Git forge inside Cursor; early beta since August 2026 on paid plans | Change-control CLI and control plane on top of any Git host |
| Hosting | Hosts repositories; can mirror GitHub | Does not host. Origin, GitHub or any Git host stays the system of record |
| Conflict model | Git text merge with merge queues and stacked pull requests | Semantic blast radius and invariant checks at proposal time |
| Coordination between agents | Parallel work lands through the queue | Announce, lease and propose; conflicts surfaced before anyone commits |
| Review | Pull request review flows in Cursor | Cross-vendor reviewer quorum, policy gates, signed evidence |
| Agents | Cursor agents, MCP and API | Claude Code, Codex, Cursor and any CLI or MCP agent |
| Debugging a bad change | Pull request history | Replay, blame and bisect over the ledger |
Frequently asked questions
- Does Nool work with Cursor Origin?
- Yes. Origin is a Git host, and Nool sits before the push. Agents propose changes through Nool, and solidified changes are pushed to whichever remote you use.
- Is Nool an alternative to Cursor Origin?
- Only if what you need is governance rather than hosting. Nool does not store your repositories. If your problem is agents colliding or shipping out-of-scope changes, Nool solves it whether you host on Origin or GitHub.
- Do I need Origin to use Nool with Cursor?
- No. Nool works with Cursor on any Git remote. See the Nool with Cursor guide in the docs.
- Does Nool support stacked pull requests?
- Nool works in try branches that promote into main history one at a time, and nool merge can ingest an incoming Git branch, such as a pull request, through the gate stack. Stacking and queueing pull requests remain the forge's job, whether that forge is Origin or GitHub.