Dev & Engineering coding-agentclivs-code-extensionjetbrains-plugindeveloper-tools

Continue

An open-source coding agent shipped as a CLI, VS Code extension, and JetBrains plugin, bringing AI coding assistance into your existing workflow.

FollowAgents review · FARS-2.1
Not recommended
43/ 100 5-point scale 2.2 / 5
1 2 3 4 5 6
1Trust11 / 29 · 1.9/5

Evidence shows an archived, read-only repository (explicitly stated in README). Trust evidence is thin: the auto-fix workflow is disabled (if: false) with scoped permissions, but the agent's core permission model, user confirmation, data flows, and secret handling (readSecrets/writeSecrets handlers appear in test code) cannot be audited from the provided source; only a handful of root dependencies are visible with no lockfile or audit evidence. Publisher is unverified but not deducted per rules; source_attribution earns 2 for a clear LICENSE and copyright notices.

2Reliability5 / 14 · 1.8/5

Binary tests cover ping/pong, config, history, and model add/delete, showing intent toward protocol self-consistency, but failure paths and error-message design are not evidenced in this static review; the archived status means dependency availability degrades over time with no patch channel.

3Adaptability8 / 18 · 2.2/5

README describes three forms (CLI, VS Code, JetBrains) and recommends the CLI, giving some environment fit; but audience details and capability-boundary docs live outside the repo at docs.continue.dev and cannot be verified here. trigger_precision earns 2 because workflow trigger conditions are concretely specified.

4Convention9 / 18 · 2.5/5

License earns 3 (full Apache-2.0 text consistent with README badge); README candidly discloses the archival and the recommendation to prefer CLI over JetBrains, so known_limitations earns 2; naming is stable across packages/directories. However install notes defer entirely to external docs, changelog is only a link to GitHub Releases, maintenance has actually ended (read-only), and the provided file set shows only a fragmentary information architecture.

5Effectiveness6 / 13 · 2.3/5

README evidences historical value as a pioneering open-source coding agent and an explicit positioning as a foundation for others (marginal_value), but archival and no active maintenance make cost-benefit questionable for adopters; output usability lacks source evidence to score.

6Verifiability4 / 8 · 2.5/5

Facts and inference are mostly separable: archival status, license, and the disabled auto-fix workflow are pointable file facts; but key claims (security posture, functional completeness) cannot be cross-corroborated within the repository, and SECURITY.md's promised responsiveness is unverifiable for an archived project.

Evidence confidence: Low Reviewed Sep 10, 2026 Reviewed revision 5522c6f44ca0
Before you use it
  • The repository is explicitly declared unmaintained and read-only; adopters get no security patches and should treat it as a frozen snapshot, not a live product.
  • The auto-fix test workflow is disabled (if: false) but its design uses CI secrets to start a remote agent session and asks the agent to commit fixes; if re-enabled, its permissions and auto-commit behavior should be re-assessed.
  • SECURITY.md promises high responsiveness to vulnerability reports, but this is unverifiable for an archived repo and should not be relied upon.
  • readSecrets/writeSecrets IDE handler interfaces appear in test code; the main source was not provided, so secret-handling paths cannot be statically confirmed as safe.
  • The JetBrains plugin is officially recommended against; avoid using it from this archived revision.
Review evidence [1][2][3][4][5][6][7][8]
See the full review method →

What does this agent do, and when should you use it?

Continue is an open-source coding agent from Continue Dev, Inc., licensed under Apache-2.0, delivered in three forms: a CLI (distributed as the npm package @continuedev/cli), a VS Code extension (published on both the VS Code Marketplace and the OpenVSX Registry), and a JetBrains plugin (distributed via GitHub Releases). The project shipped a final 2.0.0 release covering all three forms, which removed anonymous telemetry, pulled out authentication, and squashed bugs. Notably, the continuedev/continue repository is no longer actively maintained and is read-only for all users. Official documentation lives at docs.continue.dev, covering configuration, how the agent works, and customization. The team explicitly recommends JetBrains users switch to the Continue CLI instead of the plugin. For developers who want a coding agent running in their own environment and can accept a project frozen at its final release, it is a self-hostable option with a permissive license.

Continue serves developers as a coding agent in three delivery forms: as a CLI, users install the @continuedev/cli npm package and invoke it from the terminal; as a VS Code extension, it installs from the VS Code Marketplace or OpenVSX Registry and runs inside the editor; as a JetBrains plugin, it is downloaded from GitHub Releases and installed into IntelliJ-based IDEs (with the CLI officially recommended instead). The final 2.0.0 release removed anonymous telemetry and authentication requirements, meaning no mandatory account binding and no anonymous usage reporting at runtime. Configuration, operation, and customization are documented at docs.continue.dev.

  1. Developers who want to run a coding agent from the local terminal via a CLI, independent of any IDE
  2. VS Code users who want AI coding assistance directly inside the editor
  3. JetBrains (IntelliJ-based) IDE users wanting to try an AI coding plugin (the CLI is officially recommended instead)
  4. Privacy-conscious teams that require tools with no anonymous telemetry and no forced login
  5. Teams that need an Apache-2.0 codebase to build on or fork for their own AI developer tooling

What are this agent's strengths and limitations?

Pros
  • Fully open source (Apache-2.0): auditable, self-buildable, and usable as a foundation for derivative projects
  • The final 2.0.0 release removed anonymous telemetry and mandatory authentication, making it privacy and compliance friendly
  • Ships as a CLI, VS Code extension, and JetBrains plugin, fitting different development environments
  • The VS Code extension is on both the VS Code Marketplace and OpenVSX Registry, covering VS Code forks
Limitations
  • The repository is no longer actively maintained and is read-only; there will be no further bug fixes or features
  • The JetBrains plugin is explicitly not recommended by the maintainers (use the CLI instead), creating deprecation risk for that form
  • The codebase is frozen at 2.0.0; changes to upstream model APIs or dependencies may not receive updates
  • The README lacks detailed install prerequisites and exact commands; users must rely on the external docs at docs.continue.dev

How do you install or deploy this agent?

CLI (recommended path): npm install -g @continuedev/cli, then use it from the terminal (see docs.continue.dev for the exact command surface). VS Code: search for "Continue" on the VS Code Marketplace (extension ID: Continue.continue), or install from the OpenVSX Registry. JetBrains: download the plugin from GitHub Releases at github.com/continuedev/continue/releases. Note: the repository is archived and read-only; 2.0.0 is the final release and no further updates will come.

How do you use this agent?

CLI: after installing, run it from the terminal (detailed usage, configuration, and customization are documented at docs.continue.dev). VS Code / JetBrains: install the extension or plugin and use it inside the IDE. The 2.0.0 release removed authentication, so no account registration is required; anonymous telemetry has also been removed. JetBrains users are explicitly advised to use the Continue CLI instead.

FAQ

Is Continue still maintained?
No. The continuedev/continue repository is no longer actively maintained and is read-only for all users. 2.0.0 is the final release of the VS Code extension, CLI, and JetBrains plugin.
Do I need an account to use Continue?
No. The final 2.0.0 release removed authentication and anonymous telemetry.
Should I use the CLI, the VS Code extension, or the JetBrains plugin?
All three shipped with 2.0.0. If you use a JetBrains IDE, the maintainers explicitly recommend the Continue CLI instead; VS Code users can use the extension, and terminal-first users can use the CLI.
What are the long-term risks of adopting it?
Since the project is archived and frozen, there will be no feature updates or fixes; if your environment or dependencies change, compatibility updates may not arrive. The Apache-2.0 license allows you to fork and maintain your own version.
Where do I find configuration and customization docs?
The official docs at docs.continue.dev explain how to configure Continue, how it works, and how to customize it.

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.

Related agents