What people actually say about Continue
108 mentions across 6 sources · 48% positive · researched Oct 8, 2026
Hacker News, YouTube, Product Hunt, Stack Overflow, GitHub, Lemmy
What users praise
- • 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
What frustrates them
- • 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
This is a summary. The full report adds every quote we found, a per-source breakdown, recurring themes, hidden costs and the learning curve — run a free scan below, or see the full Continue review.
What comes up again and again about Continue
Recurring themes across everything we collected, with where each one showed up.
The Cursor acquisition killed the roadmap — this is a codebase to fork, not a product to adopt
criticised · seen on GitHub, Product Hunt
Open-source plus local-model support is the core reason people loved it
praised · seen on Product Hunt, YouTube
Unresolved crashes and IDE incompatibility undermine day-to-day reliability
criticised · seen on GitHub
Setup friction around local models like Ollama trips up non-experts
mixed · seen on YouTube, Stack Overflow
Out-of-the-box focus and staying inside the editor was the original selling point
praised · seen on Product Hunt
No support path for billing and refund issues now that the team has moved on
criticised · seen on GitHub
How hard is Continue to learn?
Users describe it as intermediate · typically A few hours to get going
Where people get stuck
- • Configuring a local model like Ollama — users report settings buried under 'Preview'
- • Distinguishing Windows vs Mac and local vs remote model setup in guides
- • Understanding when you're on your own versus when the extension still just works
- • Reading the codebase once you decide to fork and maintain it
Who Continue actually suits
Works well for
- • Engineering teams who want a self-hostable AI coding foundation they can fork and audit
- • Security-conscious orgs that need code to never leave the local machine
- • Researchers and tinkerers experimenting with BYOM and local models like Ollama
- • Developers who want a free VS Code or JetBrains AI agent with no subscription
- • Teams with in-house platform engineers who can absorb maintenance themselves
Not the right fit for
- • Anyone who needs vendor support, SLAs, or a maintained release roadmap
- • Teams on the latest IntelliJ or bleeding-edge VS Code builds expecting reliability
- • Buyers evaluating a commercial AI coding assistant and comparing it to Cursor, Copilot, or Windsurf
- • Non-technical users who want a setup-and-go tool with curated documentation
- • Organizations with compliance requirements that assume an actively patched dependency
What people are discussing right now
Discussion volume is low and trending down
- Cursor acquisition and end of maintenance
- Open VS Code and IntelliJ compatibility bugs
- Local model and BYOM setup friction
- Whether forking the codebase is worth it
- Billing and credit refund issues
What people really think about Continue
A real-time sweep of the open web — social media, forums, review sites, video reviews and live community discussions — distilled into one honest verdict with the actual mentions behind it.
What's inside your Continue report
Everything you need to decide — distilled from real, current user opinion.
Live mentions
The actual posts, reviews & complaints about Continue — with links and dates.
Honest verdict
A straight answer on whether it lives up to the hype — and who it’s really for.
Praise & gripes
What users genuinely love and the frustrations that keep coming up.
Real quotes
Representative voices from real users, not marketing copy.
Recurring themes
The patterns across hundreds of opinions, surfaced at a glance.
Red flags
Hidden costs and dealbreakers people only discover after signing up.
How it works
Sign up free
Create an account in seconds — get 5 free scans, no card.
We sweep the web
Live social media, forums, reviews & video opinions — in ~30–60s.
Get your report
An honest, downloadable verdict with the real mentions behind it.
Ready to see the real verdict on Continue?
Your scan is ready in under a minute · $1.
Compare Continue head-to-head
See how it stacks up against the tools people weigh it against.
Top alternatives to Continue
Researching options? Explore the closest alternatives.
Aider
Open-source AI pair programming in your terminal, Git-native, with whole-codebase awareness.
Tabnine
Enterprise AI coding assistant with an Enterprise Context Engine and air-gapped deployment for regulated teams
Cline
Cline is an open-source coding agent that edits files, runs bash commands, and works in your IDE, terminal, or desktop.
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
Check sentiment on these too
Run a live scan on the alternatives before you decide.
Continue — questions buyers ask
What do people complain about most with Continue?
The complaints that recur most often are acquired by Cursor in January 2026 and no longer actively maintained, open edit_existing_file bug crashes VS Code with no fix in sight and breakage on IntelliJ 2025.3.1.1 remains open and unresolved. Drawn from 108 mentions across 6 sources.
What do users like about Continue?
Users consistently praise genuinely open source with a readable, self-hostable codebase teams can audit, bring-your-own-model across providers means zero model lock-in and runs local models for no subscription and no code leaving the machine.
Is Continue hard to learn?
Users describe it as intermediate; most people are up and running in a few hours; the usual sticking points are configuring a local model like Ollama — users report settings buried under 'Preview' and distinguishing Windows vs Mac and local vs remote model setup in guides.
Who should not use Continue?
Based on what users report, it is a poor fit for anyone who needs vendor support, SLAs, or a maintained release roadmap, teams on the latest IntelliJ or bleeding-edge VS Code builds expecting reliability and buyers evaluating a commercial AI coding assistant and comparing it to Cursor, Copilot, or Windsurf.
What are people saying about Continue right now?
Discussion volume is low and trending down. Current topics: cursor acquisition and end of maintenance, open VS Code and IntelliJ compatibility bugs and local model and BYOM setup friction.
How current is this report?
Each scan runs live the moment you click — it reflects what people are saying now, and every report lists the dated mentions behind it.
Can I download it?
Yes — download the full report as a polished, shareable PDF.