Cursor acquires Continue, letting the community with open-source AI coding tools

Cursor Acquisition of Continue: What It Means for Open-Source AI Coding Assistants

The open-source AI coding assistant landscape shifted sharply with the quiet acquisition of Continue by Cursor. Continue, which attracted over 34,000 GitHub stars and emerged as a standout GitHub Copilot alternative, has now been discontinued as a managed service. Its codebase is handed to the community, with current users on a short timeline to export their data. This deal, closely following SpaceX’s $60 billion investment in Cursor, underscores both the intensity of competition in AI developer tools and the uncertainty facing independent open AI assistants. If you care about the future of developer experience, this is the moment to reassess where you get your assistive intelligence.

What is Continue and why was it important?

Continue was an open-source AI coding assistant built to challenge the status quo dictated by GitHub Copilot. Its main appeal: full transparency, self-hosting, and freedom to extend—attributes not available with Copilot’s closed platform. With 34,000 GitHub stars at the time it was acquired, Continue wasn’t a fringe experiment; it was the community’s most prominent open-source alternative for smart code completion and automation.

Continue’s toolset allowed developers to interact with AI deeply integrated into their workflow, instead of living in a side window or locked behind SaaS. It emerged thanks to founders Ty Dunn and Nate Sesti, both with backgrounds in conversational AI and data infrastructure. The project rapidly grew through 2023, in a climate where “coding agent” tools were embryonic and investors largely viewed Copilot as having already won the market. Continue’s core audience wasn’t just open-source purists—it was pragmatic engineers who needed to inspect, debug, and extend their coding assistants, something black-box SaaS couldn’t support.

Its popularity revealed the pent-up demand for more transparent and customizable developer tools. Continue’s rise signaled that developer-first AI was more than a side project: it was a viable competitor, continuously shaped by real user friction.

Who is Cursor and what does this acquisition involve?

Cursor is an AI developer tools vendor that has spent the past 18 months in hyper-consolidation mode, quietly acquiring engineering-focused startups like Continue. Cursor’s business is the same developer experience frontier where Continue made its stand: smart code recommendations, deep AI copiloting, and high-velocity workflows.

The acquisition itself was low-profile. According to The New Stack, the deal closed around the same time as SpaceX’s headline $60 billion investment in Cursor, making Elon Musk’s rocket company the indirect owner of the Continue IP and brand. Terms were not disclosed, but the effect was immediate: Continue as a product shuts down, and its codebase officially passes to the open-source community.

Around June 16, Continue’s homepage was updated to confirm the acquisition by Cursor. This included a FAQ explaining timelines and user migration steps—an explicit nod to transparency, if not continuity of service. Developer reports online, as well as posts from investors like Matthaus Krzykowski, corroborated the shutdown and commended the founding team on their technical leadership.

Cursor, flush with investment capital and now backed by SpaceX, signals its intent to lead the AI coding assistant market by whatever means—acquisition, integration, or community handoff. The pattern is clear: as the stakes in AI coding assistants escalate, major companies will not hesitate to buy, assimilate, and sometimes sunset fast-growing open-source competitors.

How does the Cursor acquisition affect Continue users?

The direct outcome for Continue users was swift and unambiguous. Service discontinuation, account shutdown, and a limited window for migration were communicated as part of the announcement. The Continue homepage and FAQ (as of June 16) told users:

• Continue has been bought by Cursor and will be discontinued.
• Current users have until July 15 to export their data, after which data will be deleted.
• All recurring billing has been disabled.

Emails to account holders (and third-party confirmation via LinkedIn and forum reports) echoed the same: accounts will close, and no new managed service will follow. This handoff is not “business as usual”—it’s an abrupt end to Continue as a hosted product. There is no in-place migration to a Cursor-branded equivalent, nor a guarantee of feature parity in Cursor’s own tools.

For users relying on Continue’s integrations, agent pipelines, or in-IDE helpers, the timeline is clear and fixed. Data export is available until July 15, then accounts and stored state will be wiped. The entire billing infrastructure has been shut off, eliminating the risk of orphaned charges.

This is an explicit break: Continue is not being merged or white-labeled into Cursor’s product suite. Instead, the service is discontinued entirely, with only the codebase surviving as an open-source artifact for the community to maintain, fork, or revive.

Is Continue a viable GitHub Copilot alternative after acquisition?

Continue’s status as a Copilot alternative has fundamentally changed post-acquisition. Practically, Continue users now depend on a community-maintained codebase, not a company-backed service. The GitHub repo remains open, but the guarantees and velocity of a funded team are gone.

Compared to GitHub Copilot—whose paid product remains tightly integrated into the GitHub and VS Code ecosystems—Continue now resembles projects like TabNine’s open forks: valuable as templates and proof-of-concept, but lacking the smooth onboarding, cloud infrastructure, and cohesive support that mainstream developers require.

On the upside, Continue’s open code lives on and can be self-hosted, extended, and vetted for privacy or security-sensitive contexts. Feature development and bugfixes will depend entirely on new maintainers and contributor interest. For advanced users, this is an opportunity to steer the assistant in directions closed SaaS never would—tailored model support, custom prompts, unconventional IDEs.

But for the wider market—developers seeking a drop-in Copilot alternative with minimal setup—the barrier has grown. The shutters come down on managed hosting, account sync, and smooth updates. The project’s future is now at the mercy of open-source sustainability patterns: enthusiasm from a few core contributors, the real risk of stagnation, and the hope that community needs align with continued development.

Continue doesn’t vanish, but its status as a “viable Copilot alternative” now depends on community energy, not startup funding.

How to access and use Continue’s codebase today?

With the discontinuation of Continue as a product, the project’s functionality is now fully in the hands of its developer community. Developers can access, fork, and contribute to Continue’s codebase via its GitHub repository. To use Continue today:

1. Find the repo:
   Search for “Continue AI GitHub” to land on the main repository, which as of acquisition had 34K stars. The codebase includes installation instructions for supported IDEs and platforms.

2. Install locally:
   Clone the repo and follow the setup guide. The assistant can typically be deployed as a local or self-hosted plugin, with configuration files for various environments. Example:

   git clone 
   cd continue
   # Follow included README for installation steps.

3. Export or import settings:
   With official support winding down, ensure you port your previous configurations, prompts, or workspace data before July 15 using the provided migration docs.

4. Contribute or extend:
   The community is now responsible for triage, feature requests, and releases. Developers familiar with TypeScript, Python, or modern AI tool integrations can submit pull requests or join issue discussions directly on GitHub.

5. Community and support:
   For updates, developer chat, or collaborative debugging, check pinned issues and links to Discord/Matrix or forum channels cited in the repo’s README.

This is an open invitation—anyone can help define what the “next” Continue becomes, whether as a direct Copilot competitor or a research platform for new coding interfaces.

What does this acquisition mean for the AI developer tools market?

Cursor’s acquisition of Continue is not just another startup M&A—it’s a signal of accelerating consolidation at the very heart of developer experience platforms. With SpaceX’s $60 billion investment in Cursor, the resources behind these moves are on the order of entire sectors, not just software rounds.

For the market, this means:

• Large platform gravity: As well-capitalized players like Cursor (and by extension, SpaceX) pull in open-source IP, the window for independent, impactful coding assistants narrows.
• Tool churn and consolidation: Open-source projects face a choice—compete directly with mega-funded SaaS, or risk being bought, sunsetted, or niche-forked.
• Uncertain open-source futures: Even standout projects like Continue, with 34K stars, are not immune to abrupt discontinuation or handoff.

For competitors like GitHub Copilot, this trend means fewer direct open-source threats, but also continued innovation from the edges as new projects spin up from the remains of older ones. Every consolidation leaves behind both a stronger central player and a community determined to rebuild.

Closing: the new shape of open-source AI coding assistants

Cursor’s acquisition of Continue marks a new inflection point for the AI coding assistant ecosystem. A leading open-source alternative is shuttered as a managed service but handed to the community for ongoing development. For developers, the lesson is clear: the ground beneath AI developer tooling is still shifting, with corporate coordination and community resilience driving the next generation of tools. The future of open-source assistants—and developer agency in AI—depends on what happens in these next cycles of codebase stewardship and new launches.