Cursor acquired Continue, an open-source coding agent, and the Continue team has ended the standalone product. Reports say the team issued a final 2.0.0 release, made the repository read-only, and left the Apache 2.0-licensed code available for forks, but upstream maintenance—including security, model-adapter, and editor-compatibility updates—has stopped. The supplied material identifies no maintained successor; claims about the repository state and community handoff come primarily from third-party reports rather than the brief official announcement.
2026-08-29T14:27:06Z
Repeated rechecks have produced only amplification of Cursor’s separate model-access dispute, with no Continue repository activity, governance handoff, or maintained successor. The dormant watch can expire and be reopened if substantive repository or first-party succession evidence appears.
2026-08-29T13:26:53Z
The refreshed comments and minor engagement increase only amplify Cursor’s separate model-access dispute; they add no repository activity, governance handoff, maintained Continue successor, or first-party succession disclosure.
2026-08-29T11:34:52Z
The refreshed comments remain repetitive discussion of Cursor’s separate model-access dispute and add no repository activity, governance handoff, or maintained Continue successor. The succession case remains dormant and should move only on substantive repository or first-party evidence.
2026-08-29T10:31:55Z
The refreshed comments remain repetitive discussion of Cursor’s separate model-access dispute and provide no repository activity, governance transfer, or maintained Continue successor. The case remains a dormant succession watch and should be revisited only on substantive first-party or repository evidence.
2026-08-29T09:26:40Z
Refreshed discussion remains repetitive commentary on Cursor’s model access and adds nothing about Continue’s repository, governance, or successor maintenance. The case is now best treated as a dormant succession watch triggered only by first-party disclosure or substantive repository activity.
2026-08-29T08:31:34Z
The refreshed comments are further amplification of the previously alerted Cursor model-access dispute, not evidence about Continue’s repository, governance, or a maintained successor. The case remains an unresolved but increasingly slow succession watch that should be revisited only on repository or first-party change.
2026-08-29T07:29:48Z
The discussion stream is now fully repetitive and should no longer drive the case; it remains a slow watch for repository activity, transferred maintainership, or a first-party succession disclosure.
2026-08-29T06:32:12Z
The refreshed comments only amplify the already-covered Cursor model-access dispute and add no Continue repository activity, governance handoff, maintained fork, or first-party succession disclosure. The case remains a low-temperature watch that should move only on substantive repository or official evidence.
2026-08-29T05:31:26Z
Refreshed comments remain repetitive speculation about Cursor’s model access and add no Continue repository activity, governance handoff, or maintained successor. The case remains a slow succession watch and should move only on substantive first-party or repository evidence.
2026-08-29T04:28:45Z
Refreshed comments repeat the already surfaced claim that OpenAI model access is being withdrawn from Cursor, without adding first-party terms, timing, user actions, or any Continue repository or succession change. The adjacent access story no longer justifies high heat; this returns to a low-temperature watch for substantive repository or official evidence.
2026-08-29T03:30:01Z
The added Reddit discussion only echoes that OpenAI model access may be withdrawn from Cursor; it supplies no concrete terms and does not affect Continue’s unresolved maintenance succession. The case remains hot only for retrieval of the adjacent first-party decision, not because the abandonment hypothesis strengthened.
2026-08-29T03:23:20Z
evidence attached: reddit.post.1w1a5li — shared external link with case evidence
2026-08-29T02:28:47Z
The new headline signals a potentially consequential OpenAI decision about Cursor after the reported SpaceX acquisition, but its missing text neither establishes the consequences nor changes the unresolved Continue succession question. Treat it as a short-fuse adjacent access issue pending retrieval, not evidence of a maintained successor or permanent abandonment.
2026-08-29T02:23:23Z
evidence attached: hn.story.49486172 — Official follow-up on Cursor’s reported acquisition by SpaceX materially contextualizes the open acquisition and ecosystem-ownership episode.
2026-08-28T20:42:10Z
Another stale recheck produced only one additional comment and no repository activity, governance handoff, or credible successor. Continued silence modestly supports near-term abandonment but still cannot establish permanent ecosystem discontinuity.
2026-08-26T20:36:16Z
Additional comments remain migration anecdotes and alternative-tool recommendations, providing no evidence of successor maintenance, governance transfer, or renewed upstream activity. The case remains a low-temperature repository watch, but the current discussion stream no longer merits frequent review.
2026-08-24T19:57:42Z
The latest comments remain replacement-tool recommendations and migration anecdotes, with no maintained fork, governance handoff, first-party disclosure, or renewed repository activity. The succession question is unchanged and should now be revisited only on substantive repository or first-party evidence.
2026-08-23T14:30:17Z
The refreshed discussion still consists of replacement recommendations and migration anecdotes, with no maintained fork, governance handoff, or renewed upstream activity. It does not change the succession hypothesis; only repository or first-party evidence would materially reprice it.
2026-08-23T09:35:45Z
The refreshed comments add only more individual migration and replacement-tool anecdotes, not a maintained fork, governance handoff, or renewed upstream activity. The succession question remains unresolved and still depends on repository or first-party evidence.
2026-08-23T07:23:44Z
The refreshed comments remain migration anecdotes and replacement recommendations, with no evidence of a maintained fork, governance transfer, or renewed upstream development. The succession question is unchanged and still depends on repository or first-party activity.
2026-08-23T06:29:14Z
The refreshed discussion remains replacement-tool chatter rather than evidence of a maintained fork, governance handoff, or renewed upstream activity. It adds no substance to the succession question, so the case remains a low-temperature watch for repository or first-party changes.
2026-08-23T04:30:43Z
Refreshed comments remain individual recommendations for replacement tools, not evidence of an organized fork, transferred maintainership, or renewed upstream development. They reinforce near-term user migration but do not resolve whether Continue will have a credible maintained successor.
2026-08-23T03:23:50Z
User discussion now shows Continue users actively migrating to alternative tools, modestly strengthening the near-term abandonment reading, but it identifies neither a maintained fork nor evidence that abandonment is permanent. The unsupported SpaceX claim is discounted.
2026-08-23T03:22:07Z
evidence attached: reddit.post.1vvvbtj — Despite unreliable acquisition details, the report adds ecosystem evidence that Continue users may be left with a final release and no maintained successor.
2026-08-22T11:27:11Z
No successor, renewed maintenance, or additional acquisition disclosure has surfaced; the case remains an unresolved succession watch rather than evidence of permanent ecosystem abandonment. The minor engagement increase is repetitive amplification and adds no substance.
2026-08-22T11:26:02Z
grounded: known/low — Sovereign Software Assurance already states the exact position this case illustrates: source-code availability and fork rights do not provide continuity without
2026-08-22T11:23:48Z
origin walked (codex/luna, conf 0.96): anchor hn.story.49398366 -> echo.blog.6de87ef59d by Continue Dev, Inc.
2026-08-22T11:22:47Z
case created — The observation quotes Continue’s acquisition announcement and the repository’s read-only maintenance notice, establishing a concrete developer-tool transition with unresolved consequences for open and offline users.