Continue, the open-source AI coding assistant, is no longer maintained: Cursor acquired it in June 2026 and its hosted service has closed. This page compares what Continue offered with CodeZero, for teams deciding where to go next.
CodeZeroACTIVE
Frigga Cloud Labs · VS Code extension · release 1.2.3
ContinueUNMAINTAINED
Continue Dev, Inc. · Apache-2.0 · acquired by Cursor, June 2026
THE SHORT VERSION
What Continue offered
A configurable AI layer. 20+ model providers through one config file, fill-in-the-middle autocomplete, inline edit and chat, in VS Code and JetBrains.
Where it stands now
Unmaintained. The README declares the repository read-only, the Hub and sign-in are gone, and the final VS Code release was 2.1.0 on 19 June 2026. The source stays available under Apache-2.0.
What CodeZero offers
Everything around the agent. A Git client, an index of your organisation’s code including repositories not on your machine, shared tasks and plans, and a Planned mode in which the agent cannot write until you approve its plan.
01
Two architectures
Continue sat between the editor and the models. CodeZero attaches to the editor and uses the agent you already have.
Two places to attach. Continue sat between the editor and the models and provided the abstraction — provider config, autocomplete, inline edit. CodeZero attaches to the editor instead, delegates the model layer to the agent CLI the developer already uses — Claude Code, Codex, GitHub Copilot CLI or Cursor CLI — and adds Git, an organisation index, a plan gate and shared tasks around it.
Key
CodeZero advantageContinue advantageContestedNot a contest
02
Status and shape
ParameterCodeZero AI IDEContinue
Vendor
Frigga Cloud Labs
Continue Dev, Inc. — 2023 to 2026
Status
Active — release 1.2.3
Unmaintained — acquired by Cursor around June 2026; the hosted service closed (a third-party report gives a 15 July data-export deadline). GitHub does not mark the repo archived; the README declares it read-only
Final release
n/a
The final releases cover the VS Code extension only: v2.0.0-vscode and v2.1.0-vscode, both 19 June 2026, 2.1.0 being a version bump of 2.0.0. 2.0.0 removed sign-in and the Hub. The CLI’s last release was 1.5.47 (18 June 2026) and the JetBrains plugin’s 1.0.67 (27 March 2026). Continue’s README calls 2.0.0 the final release across all three, but only the VS Code extension carries a 2.x version
What it was
An AI IDE panel — Git client, agent host, org index and task system
An AI coding assistant — chat, autocomplete, inline edit and agent, over any provider
Surfaces
VS Code
VS Code, JetBrains, and a CLI published as @continuedev/cli
Licence
Proprietary
Apache-2.0, source public and still readable
Architecture
Extension plus webview, driving a local agent CLI
A TypeScript core, a React GUI, and per-IDE extensions over it
03
What Continue offered
Continue’s inline features, next to CodeZero’s approach.
ParameterCodeZero AI IDEContinue
Tab autocomplete
Not offered
Core feature — fill-in-the-middle completions
Inline edit
None
Yes — the Cmd+I interaction
Model choice
Whatever the chosen agent CLI supports — Claude Code, Codex, GitHub Copilot CLI or Cursor CLI
20+ providers via config.yaml. The Continue Hub that backed it is gone — hub.continue.dev no longer resolves
Yes — covering repositories never cloned on this machine
Local workspace only (and that embeddings index is deprecated)
Cross-repo tracing
Functions view — cross-repository flows at module and file level, with file:line evidence on each cross-repo edge
None
Write isolation
Structural in Planned mode — before approval the agent can write only ~/.code0/plans, outside every repository. The default mode is Auto
A read-only Plan mode, then per-tool policies — Ask First (default), Automatic or Excluded; no approval step unlocks writes
Team-owned work items
Tasks and plans are organisation objects
None — tool policies and configuration are per developer
Self-hosted backend
Yes, on Enterprise — backendUrl, identityUrl and accountsUrl point the extension at your own deployment without a rebuild
None now — the hosted Hub closed in 2026; the open-source extensions run without a backend
About this comparison
Details for Continue come from Continue’s own website, documentation and GitHub repository, and from published coverage, checked on 26 October 2026. Products and prices in this category change often, so check the vendor’s site for current terms. Product names and trademarks belong to their respective owners.
We use cookies to keep our website running smoothly, remember your preferences, and improve your experience. Choose “Allow all” to accept all cookies, or “Allow essential” to keep only the ones needed for the site to work.