// the find
continuedev/continue
⏩ Source-controlled AI checks, enforceable in CI. Powered by the open-source Continue CLI
Continue was one of the more serious open-source AI coding assistants — VS Code and JetBrains plugins plus a CLI, with a genuine attempt at source-controlled AI checks enforceable in CI. The repo is now archived: read-only, final 2.0.0 release shipped, no active maintenance. You're looking at a finished artifact, not an active project.
- The .continue/checks/ pattern is worth stealing: source-controlled AI review rules (security-audit, anti-slop, react-best-practices) that run as CI checks is a concrete idea most teams haven't implemented, and the config format is simple enough to adapt independently.
- The autocomplete subsystem is well-engineered — streaming pipeline with tree-sitter context, LRU caching, root-path context service, and actual negative test cases from real model outputs (Qwen, StarCoder). Not toy code.
- Broad test coverage using vitest throughout core logic, with e2e tests for the VS Code extension and separate integration paths — the testing infrastructure is more complete than most open-source dev tools.
- Multi-provider LLM support with a YAML config layer means it wasn't locked to one API, and the MCP integration (MCPConnection, MCPManagerSingleton) was added before most tools bothered.
- It's archived. The README says explicitly it is read-only for all users and no longer actively maintained. Forking it means you inherit a large TypeScript monorepo with no upstream fixes.
- The monorepo complexity is real: binary layer, core, VS Code extension, JetBrains plugin, CLI, and a separate packages tree all wired together. Following data flow from a context provider through the binary IPC layer into the extension is not quick.
- The GitHub description ('Source-controlled AI checks, enforceable in CI') doesn't match what most of the codebase actually does. It reads like a late-stage pivot toward a CI product that didn't fully ship before the project ended.
- JetBrains support is explicitly de-recommended in favor of the CLI in the README itself — signals the plugin was always second-class and likely has rough edges the team never resolved.