Cursor acquires Continue and gives its users a July 15 export deadline

Cursor has acquired Continue, the open-source AI coding assistant, in a quiet acqui-hire that disables recurring billing and gives existing users until July 15 to export their data before it is deleted, The New Stack's Paul Sawers reported on 22 June 2026. Around 16 June the project's homepage was updated to announce the deal, per the same report.

For teams that built workflow tooling on Continue's VS Code extension, JetBrains plugin or CLI, the operational read is straightforward. The product is going away, the data is going with it on a fixed date, and the only continuity path the vendor is offering is a fork.

What is staying and what is going

Continue went into the deal as a Y Combinator Summer 2023 cohort company with around 34,300 GitHub stars, 4,800 forks and roughly $5 million raised, per The New Stack. The team pushed a final 2.0.0 release that removed telemetry and tidied the code as a deliberate handoff to the community, and the Apache 2.0 codebase remains publicly available to fork. The hosted service does not. Recurring billing has been disabled, and the FAQ on the homepage sets July 15 as the data-deletion deadline.

Terms of the deal were not disclosed, per the report. The timing matters: Cursor itself is on the way into SpaceX, which has confirmed a $60 billion deal for the IDE company, so SpaceX is now the eventual owner of what was, until last week, the headline open-source alternative to GitHub Copilot. Cursor used its Compile developer conference to unveil a separate product, Origin, an agent-native challenger to GitHub for code hosting and collaboration.

The migration that is now on someone's backlog

If a CI job or onboarding script invokes Continue's CLI, or a workspace ships with the Continue extension preinstalled and pointed at an internal model gateway, those references stop being stable on 15 July. The shop-floor question is whether to swap in a different assistant before the deadline or to take ownership of the Apache 2.0 source and host it internally. The first costs a re-configuration pass across every developer machine that has the extension pinned. The second costs a small team a maintenance budget the project did not previously have.

The data export is a one-time job. The maintenance is not.