Continue
Open-source AI coding agent for VS Code and JetBrains — free to fork since Cursor acquired Continue in January 2026.
Continue is a frozen reference implementation, not a product you buy. The codebase survives the Cursor acquisition and is genuinely useful to read, fork, or self-host, but nobody is shipping fixes and the homepage is a thank-you note rather than a roadmap. Pick it only if you want to own agent internals yourself — otherwise go with an actively maintained coding agent.
Verified 4d ago · liveness 87/100 · cite: rightaichoice.com/tools/continue
- Developers who want to study or fork a pioneering open-source AI coding agent
- Teams building an internal, self-hosted coding assistant on an auditable base
- Security-conscious orgs that need to read the source before deploying
- Engineers scripting agent workflows through CLI, TUI, or headless mode
- Teams that need ongoing security patches and guaranteed maintenance
- Production coding workflows that depend on vendor support and SLAs
- Developers unwilling to self-maintain compatibility with future IDE updates
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Continue if you need an actively maintained coding agent with vendor support, since the repository went read-only after the January 2026 Cursor acquisition and no one is shipping fixes.
Because the repository is read-only, the real cost after adoption is your own engineering time for security patches and IDE compatibility.
Continue's pricing model is not documented in the sources reached for this refresh, so no tier comparison against Cursor or GitHub Copilot can be made here. What is clear is that the open-source codebase remains freely available as a foundation for others following the January 2026 Cursor acquisition, which places it in a different category from actively supported commercial coding agents.
In short
Continue — Open-source AI coding agent for VS Code and JetBrains — free to fork since Cursor acquired Continue in January 2026. Best for Developers who want to study or fork a pioneering open-source AI coding agent, Teams building an internal, self-hosted coding assistant on an auditable base, Security-conscious orgs that need to read the source before deploying. Free to use.
What people actually say about Continue — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
29 mentions across 6 sources (Hacker News, YouTube, Product Hunt, Stack Overflow, GitHub, Lemmy), 79 more we could not attribute · researched Oct 8, 2026.
Weighted by the 108 posts each of 6 sources contributed.
- +Genuinely open source with a readable, self-hostable codebase teams can audit
- +Bring-your-own-model across providers means zero model lock-in
- +Runs local models for no subscription and no code leaving the machine
- +VS Code and JetBrains extension support covers the two dominant IDE families
- +36,156 GitHub stars indicate a large, knowledgeable user community for forking
- −Acquired by Cursor in January 2026 and no longer actively maintained
- −Open edit_existing_file bug crashes VS Code with no fix in sight
- −Breakage on IntelliJ 2025.3.1.1 remains open and unresolved
- −Ollama setup friction and 'Preview' settings frustrate new users
- −Refund requests for unusable credits sit open without resolution
- • Your own engineering time to fork, patch, and maintain since the project is unmaintained
- • Model provider API costs if you don't run local models
- • Billing friction reported in an open refund request for unusable credits
Viability Score
How well maintained and how widely used is Continue? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- AI code generation inside VS Code
- AI code generation inside JetBrains IDEs
- Refactoring and debugging assistance in-editor
- Bring your own model (BYOM) across providers
- GPT-5 Codex Responses API support
- Grok Code Fast 1 model support
- Shareable agents via public links
- Code review inbox with PR filters and one-click fixes
- Instant apply edits instead of streaming diffs
- Checks-as-code defined in markdown rules
- File access beyond IDE workspace with permissions
- Automated Sentry issue triage
- Snyk vulnerability patching
- CLI, TUI, and headless modes for scripting and CI
- Open-source codebase to inspect, fork, and self-host
About Continue
Continue is an open-source AI coding agent that runs inside VS Code and JetBrains IDEs, generating, refactoring, and debugging code without locking you to a single model vendor. It supports bring-your-own-model (BYOM) setups across providers, including the GPT-5 Codex Responses API and Grok Code Fast 1, so teams can swap backends as pricing and capability shift. Beyond the editor, Continue shipped shareable agents via public links, a code review inbox that filtered pull requests and offered one-click fixes, instant apply edits instead of streaming diffs, and checks-as-code written as markdown rules. It ran CLI, TUI, and headless modes for scripting and CI automation, read files beyond the IDE workspace with explicit permissions, and connected to GitHub, Slack, Sentry, and Snyk for triage and patching workflows. In January 2026, Continue was acquired by Cursor. The open-source codebase remains freely available as a foundation for others, but it is no longer actively maintained by the original team. That changes who this is for: Continue is now a codebase you inspect, fork, and adapt rather than a product you adopt for ongoing support. Security-conscious teams and researchers still get a readable, self-hostable foundation, and engineers can script agent workflows through CLI, TUI, or headless mode. Anyone who needs vendor support, a maintained roadmap, or guaranteed IDE compatibility should be evaluating Cursor or GitHub Copilot instead.
Behind the Verdict
The honest framing: Continue stopped being a product in January 2026 when Cursor acquired it. What's left is an open-source codebase, freely available as a foundation for others. That's not a small thing — a working, model-agnostic agent you can read end to end is rare, and most commercial tools won't show you their internals at all. We'd reach for Continue when the goal is learning or building, not buying. Teams that want to run an internal coding assistant on an auditable base, or researchers comparing agent architectures in real code, get a head start here. The BYOM plumbing, the checks-as-code markdown rules, and the CLI/TUI/headless modes are all patterns worth studying even if you never deploy them. Where it bites is maintenance. If your team runs Continue in production, you own IDE compatibility, dependency bumps, and security patches yourself. There is no vendor SLA, no support channel, no roadmap. Budget for that engineering time before you commit — it is real ongoing work, not a one-time setup. Compared with Cursor or GitHub Copilot, Continue loses on everything a buyer usually cares about: support, updates, integration freshness, and accountability. Where it wins is transparency. You can read the source before deploying it, and no one can change the terms under you. Selecting an alternative is straightforward. If you need an agent that keeps working after IDE and API changes, choose a maintained product. If you need to understand or modify the agent itself, Continue remains one of the cleanest starting points available. One caveat worth repeating: don't evaluate Continue against today's feature checklists. You're comparing a snapshot against actively developed tools, and the snapshot will keep losing. Judge it as a foundation, not a competitor.
Researching Continue? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Continue actually fits — and what changes day-one when you adopt it.
You fork the read-only Continue repository, pin it to your internal registry, and run checks-as-code markdown rules on every PR to catch architecture and security violations before merge.
Outcome: You get an auditable, self-hosted review gate you can read line by line, at the cost of owning maintenance yourself.
You drive Continue through its CLI and headless modes in CI, wiring GitHub and Slack so review notifications and PR fixes land in your existing workflow.
Outcome: Agent automation runs in your pipelines without asking a vendor for permission, though you are responsible for keeping it compatible.
You read the Continue codebase to compare how a model-agnostic agent handles instant apply edits, file permissions beyond the IDE workspace, and sharing agents via public links.
Outcome: You get a real reference implementation to learn from, with the caveat that it no longer tracks future IDE changes.
Use Cases
- Automate code review standards with markdown checks on every PR
- Enforce anti-slop, security, and architecture rules automatically
- Accelerate coding with AI autocomplete and chat in VS Code or JetBrains
- Run security review checks via markdown rules to catch vulnerabilities early
- Set up a privacy-first coding environment with local LLMs
- Automate Sentry triage and Snyk patching via cloud agents on Slack
- Turn Slack conversations into GitHub issues and PRs automatically
- Fork and self-host an auditable coding assistant for internal use
Models Under the Hood
as of 2026-10-16
Limitations
- The repository is now read-only and no longer actively maintained after the January 2026 acquisition by Cursor.
- You will need to self-maintain for security patches and IDE compatibility, and there is no vendor support commitment or roadmap.
- Anyone expecting a managed, cloud-hosted agent without forking effort should look at an actively maintained tool instead.
as of 2026-10-01
Verification history
We have re-verified Continue 21 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 21 verification passes.
Free to cite with attribution — this page re-verifies continuously.
Where the pricing makes sense
The company stage and team size where Continue's pricing actually pencils out — and where peers do it cheaper.
Continue's pricing model is not documented in the sources reached for this refresh, so no tier comparison against Cursor or GitHub Copilot can be made here. What is clear is that the open-source codebase remains freely available as a foundation for others following the January 2026 Cursor acquisition, which places it in a different category from actively supported commercial coding agents.
Setup time & first value
How long it actually takes to get something useful out of Continue — broken out by persona, not the marketing-page minute.
For a researcher reading the source, value comes within an hour of browsing the repository. For a team forking and self-hosting, expect days of engineering work to stand up your own registry, CI wiring, and check rules — and ongoing effort afterward to maintain IDE and provider compatibility. There is no vendor onboarding path to shorten this.
Switching to or from Continue
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From GitHub Copilot: fork Continue, point bring-your-own-model at a provider like GPT-5 Codex Responses API, and reproduce review rules as markdown checks.
- →From Cursor: if you need self-hosted auditability, fork Continue and rebuild your review inbox workflow as checks-as-code rather than relying on Cursor's managed service.
- →From a custom in-house agent: map your existing rules to Continue's markdown check format and reuse the GitHub and Slack connectors.
- ↗To Cursor: the acquiring company's managed agent is the natural destination if you want active maintenance over reading the source.
- ↗To GitHub Copilot: move to a commercially supported extension in VS Code and JetBrains if you want IDE compatibility handled for you.
- ↗To a maintained open-source agent: port your markdown check rules to a project that still ships releases, since Continue's repository is now read-only.
Integrations
Resources & Guides
Tutorials & Learning
VSCode + Cline + Continue | NEVER PAY for CURSOR again. Use this OPEN SOURCE & LOCAL Alternative
Nathan Sebhastian
VS Code with FREE Local AI - GitHub Copilot vs Continue.dev REVIEW & Setup Guide
xCreate
YouTube returned 6 videos for “Continue”, and we withheld 4: 4 could not be judged, because “Continue” is a single word that other videos use for other things. Showing the 2 we can prove are about Continue.
Official links
Tools that pair well with Continue
Common stack mates teams adopt alongside Continue, with the specific reason each pairing earns its keep.
Refact.ai
Open-source autonomous AI coding agent for VS Code and JetBrains that plans, executes, and deploys tasks with step-by-step reasoning.
DevoxxGenieIDEAPlugin
Free, open-source AI code assistant plugin for JetBrains IDEs with spec-driven development and Agent Mode
guard-skills
Five free, open-source quality-gate skills that catch hallucinated APIs, assertion-free tests, and stale docs in AI-generated code before your agent commits
Featured Head-to-Head Comparisons
Aider vs Continue
Continue vs Tabnine
If you're an enterprise that can't risk IP leaks and needs on-prem or air-gapped AI with governance, Tabnine is the clear pick — it's built for compliance and just earned a Gartner Visionary nod. If you're a developer who wants full control, transparency, and a free, hackable tool with BYOM, Continue is your playground — but be ready to self-maintain after the Cursor acquisition froze development. Choose based on whether you prioritize security and support over flexibility and openness.
Cline vs Aider vs Continue
Alternatives to Continue
View all
Refact.ai
Open-source autonomous AI coding agent for VS Code and JetBrains that plans, executes, and deploys tasks with step-by-step reasoning.
DevoxxGenieIDEAPlugin
Free, open-source AI code assistant plugin for JetBrains IDEs with spec-driven development and Agent Mode
guard-skills
Five free, open-source quality-gate skills that catch hallucinated APIs, assertion-free tests, and stale docs in AI-generated code before your agent commits
Frequently Asked Questions
Best-of guides
Used Continue? Help shape our editorial sentiment research.