Cursor Origin FAQ: Every Open Question, Tracked

Origin generates more questions than any recent Cursor launch, mostly because the June announcement was loud and the product page said almost nothing for two months. One Hacker News commenter put the mood plainly at the time: "I've never seen a waitlist for such little information." The early beta on August 17, 2026 answered the access questions and left the commercial ones open, so the honest FAQ still has two layers: the facts Cursor's docs now confirm, and the questions where the accurate answer is that Cursor hasn't said. The table below is the fast pass; the full set, including the rumors, is in the FAQ further down.

Sort those eight rows by where the answer came from and the split stops looking random. What Origin is, who built it and how to get in are answered, because those are announcements and docs. What it costs after the beta, what it protects and how you would leave are still thin, because those are commitments.

Early-beta docs tend to be generous with the first kind and quiet about the second, which is normal enough. It also means most of the rows that could change a decision still sit in the second group.

The confirmed spine grew on August 17, and every entry in it comes from Cursor or Graphite directly. Everything outside this list, from pricing tiers to the agent-native review features to the throughput numbers that circulated after the demo, is either third-party reporting or simply unanswered.

Seven rows is still a thin spine for a product this widely discussed, and the pull when somebody asks you about Origin is to fill the gaps with the interesting parts, because those are the parts you remember. The habit I have settled on is to give the spine first and then label the rest as press. It sounds less informed in the moment. The advantage shows up when the person asks a second question.

Yes, and it is done. This one started life muddied by a satirical post, but the deal is a matter of public record: a Form 8-K filed with the SEC on June 16, 2026 (the same day as the Compile keynote) discloses that SpaceX exercised the acquisition option it secured in April and signed a merger agreement to buy Anysphere, Cursor's parent company, for $60 billion in an all-stock transaction, the largest acquisition of a venture-backed startup on record. On August 14, 2026 Cursor's own blog closed the loop with a post titled "Cursor is now a part of SpaceX," whose first sentence reads "Cursor has officially been acquired by SpaceX."

The row people skip is the break fees. A termination fee is both sides putting a number on the chance this does not close, and the smaller figure attached to an antitrust block prices regulatory risk separately. Read that as interpretation rather than disclosure, though: both numbers reach this page through coverage, not the filing itself.

What does this mean for Origin? Directly: the company that hosts your code on Origin has been a SpaceX subsidiary since August 14, 2026, three days before the beta opened. That is not a reason to panic and not a reason to relax. It is one more line in the due-diligence list, alongside the security-terms and data-handling questions covered in the code custody guide. Cursor's announcement talks about compute for model training and about cheaper, more capable models; anything you read into it about Origin's roadmap or pricing is inference, not disclosure.

Three of them: what security terms cover the hosting, what runs CI, and how you get your data back out. The rest are worth knowing and will not change anything you do this quarter.

Ask them in that order, because each one can end the conversation before you spend time on the next. If no security terms cover a hosting product, the CI question never comes up, since the repo is not going there. Run it backwards and you can lose a fortnight mapping pipelines onto a host your own policy was never going to clear.

The enterprise checklist carries all ten questions and the wording to send. It runs them in a different order, starting with identity and audit logs.

At four people all three land on one person, and the risk there is that they get answered in someone's head rather than in writing, which helps nobody who asks again in six months. At four hundred they land on three desks, security, platform and procurement, and the recurring failure is each desk assuming one of the others already asked.

Put the answers in one dated document either way, with a name against each.

Most advice about evaluating a git host assumes you can open an account and try it, and since August 17 you can, on a paid plan. That covers the hands-on half: sync a repo, run real pull requests through it, see whether the review model fits the way your team actually works. It does not cover the paperwork half, because the docs say only that Origin follows your Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. and that the permissions controls are still being redesigned. Written answers from a vendor tend to be the slowest thing in the process, which makes that the half worth starting early.

The obvious moment to send these is the day your team's access opens. Or rather, write them now and send them then, because none of the three depends on having access, and the version you draft under time pressure is the one that comes back with a vague answer.