A Post-Mortem for a Pioneer
Continue is a eulogy. It’s a review of a project that, by its own admission, is no longer with us. The README plainly states the repository is read-only and no longer actively maintained. So why are we talking about it? Because Continue, in its final form, represents a fascinating and valuable artifact: a complete, polished, and pioneering open-source AI coding agent, now preserved in amber. It was a serious contender in the race to build a truly open alternative to GitHub Copilot, and for that, it deserves a proper look back.
At its peak, Continue was everything you could want from an open-source AI tool. It was a coding agent that lived in your IDE—primarily VS Code and JetBrains—or on your command line. It gave you an interactive chat pane, code generation, and editing capabilities, all powered by large language models. Its key differentiator was customizability. You could connect it to a variety of models, from OpenAI's latest to local models running on your own machine, giving you full control over your data, privacy, and costs. It was a tool for developers who wanted the power of AI without being locked into a specific vendor's ecosystem.
The Final Graceful Bow
Instead of quietly fading away, the maintainers of Continue did something admirable: they shipped a final, definitive 2.0.0 release. This wasn't just a last commit; it was a deliberate act of packaging the project for posterity. In this final version, they squashed bugs, polished the user experience, and, most importantly, ripped out all anonymous telemetry and authentication. This was a final gift to the open-source community, transforming the project from a service-oriented product into a pure, standalone tool. It’s a statement of principles, ensuring that the last version is as private and user-owned as possible.
This final release is available on the VS Code Marketplace, OpenVSX, and npm, making it remarkably accessible for an archived project. It feels less like an abandoned building and more like a museum exhibit that you can still touch. The core functionality remains impressive, offering a glimpse into what a mature, open-source AI assistant looks and feels like.
Strengths as a Foundation
The primary strength of Continue today is its codebase. With over 35,000 stars, this was a project with significant traction and, presumably, a well-architected design to support its features across multiple platforms (VS Code, JetBrains, CLI). The Apache 2.0 license makes it an invaluable resource. If you or your company are thinking about building a custom AI coding tool, you don't need to start from scratch. You can fork Continue and have a feature-rich, battle-tested foundation from day one. It’s a complete blueprint for building a coding agent.
Another strength is its documented flexibility. The project was built to be configured. The still-available documentation details how to connect different models and customize its behavior. For a researcher or a team building an internal tool, this is a massive head start. You can focus on experimenting with new models or proprietary data sources instead of reinventing the UI and IDE integration plumbing.
The Unavoidable Reality: It's Over
Let's be blunt: for 99% of developers, Continue is not a viable tool for daily work anymore. The single biggest weakness is existential: it is unmaintained. The world of software development, and especially AI, moves at a breakneck pace. An IDE extension that isn't updated will eventually break as the host IDE (like VS Code) evolves. An AI tool that isn't updated will be unable to leverage new models, prompting techniques, or APIs that emerge weekly.
The repository has nearly 1,000 open issues. These are bugs, feature requests, and compatibility problems that will never be addressed. If you install Continue and it works perfectly, that’s great. But the moment it doesn't, you are completely on your own. There is no community forum to ask for help, no developer to tag in a GitHub issue. It’s a ghost ship.
This makes it a significant risk. Relying on an unmaintained tool in your core professional workflow is a bad idea. A future VS Code update could render it useless overnight, leaving you scrambling for a replacement. Security vulnerabilities, should any be discovered in its dependencies, will go unpatched. The stability of the v2.0.0 release is its peak; from here, it's only a matter of time until bit rot sets in.
Its Place in a Modern Stack
So where does Continue fit? It doesn't fit in a production developer's active toolchain. Its place has shifted. Today, Continue is an educational resource, a case study, and a launchpad. Use it to learn how a sophisticated AI extension is built. Use it as the boilerplate for your own, new project that you intend to maintain. For a company, it could be the 80% solution for an internal coding assistant, with the remaining 20% being the custom integration and ongoing maintenance your team provides.
For everyone else—the vast majority of developers just looking for a great AI assistant to help them write code—the answer is to look elsewhere. Actively maintained projects like Tabby (for self-hosting) or CodeGPT (for model flexibility) offer similar benefits without the looming threat of obsolescence. Continue walked so that other projects could run. We should thank it for its contribution and choose a tool that's still in the race.