continuedev/continue: An Open-Source Coding Agent That Is Now Read-Only

What Continue Solves, and Who It Was Built For

Continue is a coding agent that runs inside the editor or the terminal rather than as a hosted service. The README describes it as "a coding agent available as a CLI, VS Code extension, and JetBrains plugin." That three-surface layout is the point: the same agent is meant to follow a developer from an inline edit in VS Code to a scripted run in a shell.

The audience is developers who want the agent to sit next to their code and their own model credentials, not behind a vendor account. The README's description of the final 2.0.0 release says it included "removing anonymous telemetry, pulling out authentication, squashing bugs, and more." Read plainly, that is a project deliberately stepping away from a managed service and leaving behind something you run yourself.

The important framing is that this is a finished artifact, not a growing one. The README carries a note at the top: "The continuedev/continue repository is no longer actively maintained and is read-only for all users." Anyone evaluating it should treat that sentence as the primary fact and everything else as detail.

How the Agent Is Wired Across core, gui, binary and extensions

The repository layout tells you where the work happens. Top-level directories include core/, gui/, binary/, extensions/, packages/, sync/, actions/, eval/, and docs/. The package.json scripts compile four of them independently: gui/tsconfig.json, extensions/vscode/tsconfig.json, core/tsconfig.json, and binary/tsconfig.json, each run through tsc with --noEmit in watch mode.

That split is the architecture in miniature. core/ holds the agent logic, gui/ holds the interface that appears in the sidebar, extensions/ holds the per-editor adapters (extensions/vscode and extensions/intellij are both present), and binary/ covers the standalone CLI path. A change to how a model call is assembled belongs in core; a change to how VS Code surfaces it belongs in extensions/vscode.

The presence of sync/ and actions/ suggests there is more than one way to drive the agent, and eval/ indicates the project carried its own evaluation harness. The root also holds .continueignore, which mirrors the gitignore convention: a file listing paths the agent should skip. If you fork this codebase, that is the first file to audit, because it is the boundary between what the agent reads and what it does not.

Installing Continue in VS Code and Running a First Session

The README points to three distribution channels. For VS Code, the badge links to the Marketplace listing under the publisher Continue.continue and to Open VSX under Continue/continue. For the terminal, the CLI is published on npm as @continuedev/cli. For JetBrains, the README links the releases page, but adds a direct recommendation: "We recommend using the Continue CLI instead of the JetBrains plugin." Take that at face value; the plugin is the least favoured of the three surfaces.

If you want the CLI without touching an editor, install it from npm. The package name is the one the README badge points at:

npm install -g @continuedev/cli

After that, the CLI is on your PATH and you can start a session from a project directory. The README does not document the CLI's flags or subcommands, so consult the Continue Docs at docs.continue.dev rather than guessing at arguments.

For the editor path, install the extension from the Marketplace and open the Continue panel in the sidebar. Configuration lives in a .continue/ directory inside the project, which is present as a top-level entry in this repository itself, so the project's own setup doubles as a working example you can read. The README does not spell out the config schema; it defers to the Continue Docs at docs.continue.dev for "how to configure Continue, how it works, and how to customize it." That documentation site is the place to look for model provider settings, because the README itself gives none.

The Read-Only Repository Is the Real Constraint

The most consequential fact about Continue is not a feature gap. It is that the README states the repository "is no longer actively maintained and is read-only for all users," and the last push to main was on 2026-06-19. The final releases, v2.1.0-vscode and v2.0.0-vscode, both landed on 2026-06-19, with v1.3.40-vscode a few days earlier on 2026-06-15.

What that means in practice: the code you install today is the code you will have in a year unless you change it yourself. Model providers retire API versions. Editor extension APIs change. Neither of those events will produce a commit here. The README frames this as intentional, closing with the hope that "this codebase continues to serve as a foundation for others," which is a handing-off statement rather than a roadmap.

There is a second, quieter limitation. The README does not document rollback, migration between versions, or a support policy. If a 2.0.0 build breaks your workflow, there is no documented path back to 1.3.40 beyond reinstalling an older published artifact, and the README does not confirm that older artifacts stay available. Plan for that before you standardise on it.

Continue Against Cline and Roo Code: Different Assumptions About the Host

The closest alternatives in the same category are editor-resident agents such as Cline and Roo Code. The difference is not mainly features; it is what each assumes about the surrounding system.

Continue's own README describes a three-surface agent with a shared core, an independent interface, and a standalone binary, plus a sync layer and an eval harness in the repository root. That is the shape of a tool that wants to be the agent layer across multiple editors and a terminal, with the model provider chosen by you and no authentication layer in the way (the 2.0.0 notes say authentication was pulled out).

The practical divergence is maintenance. Cline and Roo Code are distributed as VS Code extensions that are still being pushed to. Continue's advantage is the Apache-2.0 licence and the breadth of surfaces; its disadvantage is that the repository is read-only, so the extension you install is a snapshot. If your requirement is "an agent that keeps up with new models without me doing anything," Continue is the wrong tool. If your requirement is "a permissively licensed agent I can read, fork, and pin," the frozen state is closer to a feature than a defect.

Licence, Forking, and What Upgrades Actually Cost

Continue is Apache-2.0, and the README footer reads "Apache 2.0 © 2023-2026 Continue Dev, Inc." Apache-2.0 permits commercial use, modification, and redistribution, and it includes an express patent grant. It also requires that you keep the licence and notice files and state what you changed. That is a summary of the licence text, not legal advice; read LICENSE in the repository root and the CLA.md and CONTRIBUTING.md files if you plan to contribute back.

The upgrade cost is where the read-only state bites. A normal dependency upgrade is a version bump. Here, an upgrade is a fork: you take the repository, apply your own patches to core/ or extensions/vscode/, and rebuild. The build is not trivial. The root package.json runs four separate TypeScript projects, and the toolchain pins TypeScript ^5.6.3, eslint ^8, prettier ^3.3.3, and husky ^9.1.7 as dev dependencies. There is a .node-version and a .nvmrc, so the Node version is pinned too, and getting that wrong is the most likely first failure.

For a team that only consumes the published extension or the npm CLI, none of this applies. The cost only appears the moment you need a change nobody else is going to make.

Editorial conclusion

Teams that want a self-hosted, Apache-2.0 coding agent inside VS Code or a terminal can still install the final 2.0.0 builds, because the extension, CLI, and plugin remain published and the licence does not expire. Teams that need upstream fixes, new model support, or a security response channel should not start here: the README states the repository is read-only for all users and the last push was on 2026-06-19. Before committing, verify three things: that the VS Code Marketplace listing or the @continuedev/cli package still resolves, that your chosen model provider is one the 2.0.0 configuration supports, and whether you can carry the maintenance yourself, since no further commits are expected.

Frequently asked questions

Official sources

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