Continue: Open-Source Coding Agent, Now Read-Only
continuedev/continueContinue is an open-source coding agent that shipped as a CLI, a VS Code extension, and a JetBrains plugin. It's worth knowing up front: the README states the repository is now read-only and no longer actively maintained after a final 2.0.0 release.
Reach for Continue only as a reference codebase or if you specifically want the final 2.0.0 build with telemetry and forced auth stripped out. Skip it as your daily driver — the README says the repo is read-only and unmaintained, so nobody's shipping bug fixes anymore. Pick a maintained agent for real work.
The problem it solves
Developers want an AI coding assistant that lives in the editor and CLI they already use instead of a separate app, and open-source teams in particular want one they can read and self-host rather than a closed box. Continue was built for exactly that — the catch now is that active development on this repo has stopped.
What is it?
Continue is an open-source (Apache-2.0) coding agent available three ways: a CLI (`@continuedev/cli`), a VS Code extension, and a JetBrains plugin. The README describes a final 2.0.0 release across all three that removed anonymous telemetry and pulled out authentication, and states the repository is now read-only and no longer actively maintained.
Why it's getting attention
The attention here is tied to an ending, not a launch. The README documents a final 2.0.0 release and declares the repo read-only, and it recommends the CLI over the now-deprecated JetBrains plugin. A well-known project reaching a clear stopping point — and freezing a clean, telemetry-free final version — is the kind of moment that gets shared.
Key features
- ✓Coding agent delivered as a CLI, a VS Code extension, and a JetBrains plugin
- ✓Final 2.0.0 release that removed anonymous telemetry, per the README
- ✓Authentication pulled out in the final release, so the build runs without a forced login
- ✓Apache-2.0 licensed, so the code can be read, forked, and self-hosted
- ✓The README frames the codebase as a foundation others can build on
Best use cases
- •Studying how an open-source, multi-surface coding agent is structured
- •Forking the code as a starting point for your own maintained agent
- •Running the frozen, telemetry-free 2.0.0 CLI if you accept it won't get updates
- •Migrating off it to a maintained alternative while keeping familiar workflows
How to install / try
The README points to the VS Code Marketplace and Open VSX for the extension, npm (`@continuedev/cli`) for the CLI, and GitHub Releases for the JetBrains plugin. Configuration details are in the Continue docs. Note the repo itself is read-only, so treat these as final builds rather than a moving target.
How to use
Per the README, the CLI is the recommended entry point over the JetBrains plugin. How to configure and customize Continue is documented at the project's docs site. Because the repository is no longer maintained, expect the docs and builds to reflect the final 2.0.0 state rather than ongoing changes.
Strengths
- ✓Runs where you already work — terminal, VS Code, and JetBrains IDEs
- ✓The final release strips anonymous telemetry and forced auth, which some teams will prefer
- ✓Apache-2.0 code you can read, fork, and self-host
- ✓Reaches a clean, clearly labeled stopping point instead of quietly going stale
Limitations & risks
- △The README says the repo is read-only and no longer actively maintained — no future fixes or features
- △Security issues found later won't be patched here; a fork would have to carry that weight
- △The JetBrains plugin is deprecated in favor of the CLI, per the README
- △Docs and integrations are frozen at 2.0.0 and will drift as models and editors change
Alternatives
Who should try it — and who should skip
Developers who want to study or fork a mature open-source coding agent, or who deliberately want a frozen, telemetry-free 2.0.0 build and accept no updates. Anyone choosing a tool for ongoing daily work should pick a maintained alternative, since the README says this repo is read-only.
Frequently asked questions
No. The README states the repository is now read-only and no longer actively maintained, following a final 2.0.0 release.
According to the README, it removed anonymous telemetry, pulled out authentication, and fixed bugs across the CLI, VS Code extension, and JetBrains plugin.
The README recommends using the Continue CLI instead of the JetBrains plugin, which it marks as deprecated.
Yes — it's Apache-2.0 licensed and the README frames the codebase as a foundation others can build on, but you'd be maintaining any fork yourself.