Continue: the 2.0 release and maintenance status

What Continue Solves and Who It Is For

Continue is an open source coding agent that sits inside your editor or terminal. It is aimed at developers who want AI assistance without being locked into a proprietary platform. The project offers three surfaces: a CLI, a VS Code extension, and a JetBrains plugin. The README explicitly says the repository is no longer actively maintained and is read-only for all users, so this is not a project you adopt expecting future development. It is for someone who wants a working, self-hostable coding agent today, with the source code open under Apache-2.0. The target user is a developer who values transparency and who can accept that the codebase is frozen.

How Continue Works: Three Interfaces, One Core

The repository layout shows a single codebase that ships as three separate extensions. The VS Code extension is published to both the Visual Studio Marketplace and Open VSX, which means it works in code editors like VSCodium that use the Open VSX registry. The CLI is distributed as an npm package under the name @continuedev/cli. The JetBrains plugin is distributed through GitHub releases. The README recommends using the CLI instead of the JetBrains plugin, which suggests the plugin may be less polished or harder to maintain. The core mechanism is that Continue integrates with your editor, but the README does not detail the internal model routing or context engine. You can find that in the Continue Docs, which the README links to, but the repository itself does not explain the data flow.

Getting Started: Install Commands and Configuration

To run Continue, you install the appropriate client. For VS Code, you install the extension from the marketplace or from Open VSX. The README does not give explicit install commands, but the npm CLI package is available as @continuedev/cli, so you would install it with npm install -g @continuedev/cli in a standard Node environment. For JetBrains, you download the plugin from the GitHub releases page. Configuration is handled through the Continue Docs, which the README points to. The 2.0.0 release notes mention removing anonymous telemetry and pulling out authentication, so configuration in the final version is likely simpler than earlier versions, but the README does not list specific config keys. You will need to consult the docs to set up model providers, API keys, or local models.

The Final 2.0.0 Release: What Changed

The 2.0.0 release is described as a final polish of the VS Code extension, CLI, and JetBrains plugin. The release notes say it removed anonymous telemetry, pulled out authentication, and squashed bugs. Removing telemetry is a meaningful change for privacy-conscious users, because it means the final version no longer sends anonymous telemetry. The notes do not establish whether every workflow can be used without an account or what happened to features that depended on a central service. The release notes do not specify which bugs were fixed or what authentication was removed, so you cannot know the full impact without testing the release yourself.

Limitations and When It Is the Wrong Tool

The most obvious limitation is that the repository is read-only. No new features, security patches, or bug fixes will arrive. If you encounter a bug in the 2.0.0 release, you are on your own. The README also recommends against using the JetBrains plugin in favor of the CLI, which is a warning that the plugin may be a second-class citizen. Another limitation is that the README does not describe any model-agnostic guarantees. You likely need to bring your own model or API access, and the configuration complexity could be high for non-experts. This is the wrong tool if you need a supported, actively developed coding agent with a vendor behind it. It is also wrong if you want a turnkey solution that works out of the box without reading external documentation.

Alternative: What Else Exists and How It Differs

The main alternative to Continue is a proprietary coding agent like GitHub Copilot. Copilot is a closed-source, subscription-based service that integrates deeply with GitHub and offers continuous updates and support. The difference in approach is fundamental: Copilot is a managed service where the vendor controls the model, the telemetry, and the feature roadmap. Continue is an open source project where you control everything, but you also take on the maintenance burden. With Continue, you can inspect and modify the code; check the documentation and your chosen workflow for its account and provider requirements. With Copilot, you cannot do any of that. The trade-off is that Copilot is actively maintained, while Continue is frozen. Another alternative is to use a local model with a different open source tool, but the README does not compare Continue to any other project.

Maintenance and License Implications

Continue is licensed under Apache-2.0, which is a permissive license that allows you to use, modify, and distribute the code, including for commercial purposes, as long as you preserve the license notice. The copyright line says 2023-2026 Continue Dev, Inc. Since the repository is read-only, the maintenance cost is effectively zero for the project team, but it is high for you if you adopt it. You must maintain your own fork if you want fixes or updates. The README calls 2.0.0 the final release, while GitHub also lists a 2.1.0 VS Code prerelease. The 2.0.0 releases are dated 2026-06-19, while the most recent push to the repository was on 2026-11-02. The Apache-2.0 license gives you the right to fork and continue development, but you would need to build your own release pipeline. There is no mention of a community forum or support channel in the README, so you cannot rely on external help.

Editorial conclusion

Adopt Continue if you want a free, Apache-2.0 coding agent that works across VS Code, JetBrains, and a CLI, and if you are comfortable with a project that is no longer actively maintained. Do not adopt it if you need ongoing updates, security patches, or community support. Before using it, verify that the 2.0.0 release works with your specific IDE version and that your model providers are compatible, since the read-only repository means no fixes will come.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes