Continue
Programmers wanted an AI helper inside their code editor. Continue was one, but its README says the project is no longer maintained, so it is mainly worth studying.
How you use it: The last release is still linked from its README, but expect no fixes or updates.
In plain English
The README introduces Continue as a coding agent you can use as a CLI, a VS Code extension, or a JetBrains plugin. It points configuration help at docs.continue.dev.
The same README opens with a direct note: the repository is no longer actively maintained and is read-only for all users. It describes a final 2.0.0 release of the VS Code extension, the CLI, and the JetBrains plugin. That release removed anonymous telemetry and pulled out authentication. The README recommends the CLI instead of the JetBrains plugin.
Because the maintainers have said the repo is read-only, this page explains what the last release was. It is not a suggestion to build new work on it.
Practical ways to use it
Example 1
See how an editor coding agent was packaged
The README still links the VS Code marketplace item, the Open VSX listing, and the npm package for the CLI, so you can see the shape of the final release.
Example 2
Try the last CLI if you accept the warning
The README lists the CLI beside the editor plugins and says to prefer the CLI over the JetBrains plugin.
Example 3
Read the docs for how it was configured
docs.continue.dev is the documentation link in the README, for people studying the design rather than starting a new dependency.
Who it is for
Developer. The pieces are a VS Code extension, a CLI, and a JetBrains plugin. All of them assume you write code. The maintenance warning comes before any of that.
Difficulty: Takes some setup. Installing an editor extension is familiar to developers. The real difficulty is that the README says nobody is maintaining it.
Getting started
- 1
Read the maintenance note before you install
The README says the repository is no longer actively maintained and is read-only. Bug fixes are not coming from this repo.
- 2
If you still want the last release, use the links in the README
It points to the VS Code extension, the npm CLI, and JetBrains builds. It recommends the CLI rather than the JetBrains plugin.
- 3
Treat the docs as a snapshot
The README links docs.continue.dev for configuration. Expect those pages to describe the final 2.0.0 era, not a moving product.
What you need first
- Accounts
- The README says the final release pulled out authentication. A model connection may still be something you configure. Check the docs before you assume a sign-in.
- Hardware
- An editor or a terminal. The README does not list a special machine.
- Cost
- The code is Apache-2.0. Any model you connect can still bill you. The project itself does not list a price in the README.
Cautions
- The maintainers say the repository is read-only and no longer actively maintained. That is the first fact, not a footnote.
- A read-only project does not get security fixes from its authors. Be careful if you let it touch private code.
- The README recommends the CLI over the JetBrains plugin. Do not expect the plugin to be the supported path.
Questions people ask
What does Continue do?
It was a coding agent for the command line, VS Code, and JetBrains. The README says the GitHub repository is now read-only and no longer actively maintained.
Who is Continue for?
Developers who want to understand that project or try the final 2.0.0 release with the maintenance warning in mind.
What do I need first?
Read the warning. If you go on, the README links the VS Code extension and the npm CLI. It suggests the CLI instead of the JetBrains plugin.
What should I watch out for?
No active maintenance means no promised fixes. Do not make it a foundation for new work without accepting that risk.