AI ERP with agents inside the systems you run
AI phone and voice agents for real calls
LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
CyberAttack.aiThreat detection and defense
Secure AI virtual data roomscontinue
Continue is an open-source coding agent available as a VS Code extension, CLI, and JetBrains plugin. The project released a final v2.0.0 version and is now read-only, having removed telemetry and authentication features. It serves as a foundation for AI-assisted development workflows.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | continuedev/continue |
| Owner | continuedev |
| Primary language | TypeScript |
| License | Apache-2.0 — OSI-approved |
| Stars | 34.7k |
| Forks | 5k |
| Open issues | 948 |
| Latest release | v2.0.0-vscode (2026-06-19) |
| Last updated | 2026-07-07 |
| Source | https://github.com/continuedev/continue |
What continue is
Continue is a TypeScript-based agent framework providing IDE integration (VS Code, JetBrains) and CLI tooling for code generation and assistance tasks. The project concluded active development with v2.0.0 and is archived for maintenance and reference only.
Get the continue source
Clone the repository and explore it locally.
git clone https://github.com/continuedev/continue.gitcd continue# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Verify Node.js/npm compatibility with your environment before deploying the CLI; TypeScript projects require build tooling.
- Plan for dependency auditing and patching—no upstream security updates are expected post-v2.0.0.
- Configure LLM backends and authentication credentials locally; the final release removed built-in authentication features.
- Test VS Code extension with your specific version; marketplace updates may not align with your VS Code release cycle.
- Establish internal fork or mirror strategy if long-term integration is planned, given the read-only repository state.
When to avoid it — and what to weigh
- You need active upstream maintenance and bug fixes — The repository is explicitly read-only and no longer actively maintained. Security patches and feature updates are not planned.
- You require commercial support or SLAs — No commercial support structure is evident from the data. The project is archived and community-maintained at best.
- You depend on frequent dependency updates — An archived TypeScript project will accumulate stale dependencies over time, creating supply-chain and security debt.
- You need JetBrains plugin reliability — The README explicitly recommends using the CLI over the JetBrains plugin, signaling lower confidence in that extension's stability.
License & commercial use
Apache License 2.0. Permits commercial use, modification, and distribution with attribution and clear license statements. No patent clause. Must include a copy of the license and document changes.
Apache 2.0 is a permissive OSI license that permits commercial use. However, because the repository is archived and read-only, you must evaluate your internal compliance, support, and maintenance strategy independently. No indemnification or warranties are provided. Review your legal position before adopting in commercial products.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Stale |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Possible |
| Assessment confidence | High |
As an archived project, Continue will not receive security patches or dependency updates. TypeScript dependencies will accumulate CVEs over time. If integrating into a security-sensitive workflow, plan for regular auditing and consider maintaining a private fork with patched dependencies. No explicit security model or audit trail is evident from the data.
Alternatives to consider
GitHub Copilot
Commercial, actively maintained IDE integration with broad language support and cloud backend. Opposite approach to Continue's local-first, open model.
Codeium
Open-source-friendly AI coding assistant with IDE plugins and CLI; actively maintained and offers both free and commercial tiers.
LangChain / LlamaIndex
Framework libraries for building custom AI agents; more flexible than Continue but require greater engineering effort to integrate into IDE workflows.
Build on continue with DEV.co software developers
Continue is archived and no longer actively maintained. Before adopting, assess your internal capacity to patch dependencies, maintain security, and manage technical debt. Consider actively maintained alternatives like Codeium or GitHub Copilot for production workflows.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
continue FAQ
Can I still use Continue after the v2.0.0 release?
Is Continue suitable for production use?
Can I fork and maintain Continue myself?
What LLM models does Continue support?
Custom software development services
DEV.co builds and maintains ai coding agents systems for startups through enterprises. If continue fits your architecture, our custom software development services cover implementation, migration, and the long tail of maintenance.
Evaluating Continue for your team?
Continue is archived and no longer actively maintained. Before adopting, assess your internal capacity to patch dependencies, maintain security, and manage technical debt. Consider actively maintained alternatives like Codeium or GitHub Copilot for production workflows.