TopGit
GitHub Repo Review

Continue: Open-Source Coding Agent, Now Read-Only

continuedev/continue
CTopGit review image for continuedev/continue
Review by Topgit.dev for continuedev/continue, with GitHub repository stats and README context.
Quick verdict

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.

Stars
โ˜… 36.0k
Forks
โ‘‚ 5.4k
Contributors
๐Ÿ‘ฅ 507
Language
TypeScript
License
Apache-2.0
Topic
Developer Tools
Updated
Sep 2026

A CLI, VS Code Extension, and JetBrains Plugin

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.

A Final 2.0.0 Release, Then Read-Only

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.

How this repository's GitHub stars have grown over time. Source: star-history.com.View the star history โ†—

Wanting an Agent You Can Read and Self-Host

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 Shipped in the Final Build

  • โœ“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

Studying, Forking, or Migrating Away

  • โ€ข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

Where to Get the Frozen Builds

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.

The CLI Over the Deprecated JetBrains Plugin

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.

What the Final Release Got Right

  • โœ“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

No Fixes Are Coming

  • โ–ณ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

Cline, Aider, Roo Code, GitHub Copilot

Cline โ€” open-source autonomous coding agent for VS Code, actively developedAider โ€” open-source AI pair programmer that runs in the terminalRoo Code โ€” VS Code coding-agent fork with active maintenanceGitHub Copilot โ€” proprietary, deeply integrated editor assistant

Who Should Still Look at Continue

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.

Continue Questions, Answered

Is Continue still maintained?

No. The README states the repository is now read-only and no longer actively maintained, following a final 2.0.0 release.

What did the final 2.0.0 release change?

According to the README, it removed anonymous telemetry, pulled out authentication, and fixed bugs across the CLI, VS Code extension, and JetBrains plugin.

Should I use the CLI or the JetBrains plugin?

The README recommends using the Continue CLI instead of the JetBrains plugin, which it marks as deprecated.

Can I still build on Continue?

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.

Related repositories

Source & attribution

Based on the official continuedev/continue GitHub repository, including its README and project metadata.

GitHub data ยท last synced Jul 11, 2026Reviewed by Henry
โ† Back to TopGit

Want a second opinion on continue?

Ask an AI that can read this page โ€” one click and you get its take on continue.

GitHub