What engineering leaders and their teams report about Continue, with every finding tied to its evidence.
Read the findingsPractitioner sentiment, all practitioners
−9 Mixed from 69 sources that take a side
How this figure is madeFrom 66 authors in 63 discussions. Use a task pilot to measure accepted work and review time.
Jan 2025 to Sep 2026.
95 sources from practitioners, by month and sentiment.
Local models and per-role model choice draw the most praise. Reliability is the concern raised most often, and autocomplete draws the most criticism, with 11 of the 15 that discuss it critical. Since June 2026 the newest sources turn to the end of maintenance and to the JetBrains plugin failing on 2026.2 IDEs.
Positive, mixed and negative sources
The score counts them as 17 positive, 26 mixed and 23 negative votes, one per author. See How the numbers work.
See the evidenceBelow: 5 praise themes, 5 concerns, 2 close to agreement and 2 disagreements.
Counted for All practitioners, from 95 sources. Change group
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
Counted for All practitioners.
Positive, 28
Positive
aaronsky, r/LocalLLaMA member
How I replaced Gemini CLI & Copilot with a local stack using Ollama, Continue.dev and MCP serversReddit post
Replaced Gemini CLI and Copilot with Continue on local Ollama models plus MCP servers, keeping code on the laptop, and uses it for refactors, PR summaries, and diff review.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control
Positive
dust42, Hacker News commenter
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopHacker News comment
Uses continue.dev with a local Qwen3-Coder 30B at about 50 tokens a second, chosen because it lets them set their own short system prompt.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Operational control
Mixed
platevoltage, Hacker News commenter
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopHacker News comment
Runs qwen2.5-coder through Continue in VS Code for assistance and completion; it works OK within 16GB of RAM.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Positive
dennemark, Hacker News commenter
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopHacker News comment
At work they run Qwen3 Coder 30B locally with continue.dev, which handles 90% of their cases well.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Positive
kergonath, Hacker News commenter
Comment on: Experimenting with Local LLMs on macOSHacker News comment
Got the continue.dev extension working in VSCodium with Ollama and Mistral models, entirely local and further than most tools they tried.
Practitioner account, pseudonymous; direct use; counts toward Operational control
Mixed
Christian Siebmanns, consultant and head of the Web and Mobile competence area at viadee
Der eigene, lokale KI-Coding-Assistent mit ContinueCompany blog post, viadee blog
Ran Continue on local LM Studio models for data protection and found results usable; a later note on the page says Cursor bought and discontinued it and points to OpenCode.
Practitioner account, name and role on their organization's own page; direct use; counts toward Operational control, Adoption and upkeep
Positive
navbaker, Hacker News commenter
Comment on: How I code with AI on a budget/freeHacker News comment
Finds the larger Qwen models and gpt-oss-120b great in Continue's agent mode.
Practitioner account, pseudonymous; direct use; counts toward Operational control
Positive
bluejay2387, Hacker News commenter
Comment on: Ask HN: What Does Your Self-Hosted LLM Stack Look Like in 2025?Hacker News comment
Moved to Devstral for coding through the Continue plugin, served by Ollama and vLLM on two 3090 GPUs at home.
Practitioner account, pseudonymous; direct use; not counted, takes no position
Positive
itissid, Hacker News commenter
Comment on: Nvidia on NixOS WSL - Ollama up 24/7 on your gaming PCHacker News comment
Hooks a self-hosted Ollama DeepSeek container to Continue for chat and code tasks and mixes in hosted models for completion.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
dabockster, Hacker News commenter
Comment on: New junior developers can't codeHacker News comment
An offline setup of Ollama, Qwen Coder 14B, and Continue.dev explains its changes with the codebase as context, slowly but at no cost.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control
Positive
atmanactive, Hacker News commenter
Comment on: Ask HN: Open-Source editor with local code completion?Hacker News comment
Has run Continue on Ollama in VSCodium for a few weeks and finds it much better than TabNine.
Practitioner account, pseudonymous; direct use; not counted, takes no position
Positive
mark-lord, r/LocalLLaMA member
Quick tutorial: How to run Cursor at home (R1-14b + Continue.dev)Reddit post
Published a short video setup for running DeepSeek R1 14B locally on a Mac behind Continue, as a free stand-in for Cursor.
Practitioner account, pseudonymous; direct use; counts toward Operational control
Positive
Sn0wCoder, Hacker News commenter
Comment on: Things we learned about LLMs in 2024Hacker News comment
Calls the Continue plugin the best AI option for IntelliJ, running local Phind and StarCoder models on a separate machine.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mixed
roscas, Hacker News commenter
Continue coding agent is dead. Alternatives?Hacker News post
Found Continue nice in VS Code with offline Ollama, then learned it is no longer updated and asked for alternatives.
Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep
Mixed
kpatucha, Hacker News commenter
Comment on: Ask HN: Is anyone experimenting with different ways of using LLMs for coding?Hacker News comment
Installed the continue.dev extension with a local model to try tab completion, noting the project was killed and will not be continued.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mixed
warpanomaly, r/LocalLLaMA member
I Can't Get Ollama running through Continue to write complex codeReddit post
Qwen3 Coder 30B through Continue handled routine functions and refactors well, but on a complex join it agreed with the user and wrote no code.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Positive
finah1995, r/LocalLLaMA member who uses this setup at work
Has used and recommended Continue on local Ollama models at work for a long time so no code leaves their control, and rates IBM's Granite models well for fill-in-the-middle completion.
Practitioner account, pseudonymous; direct use; counts toward Operational control
Mixed
reactordev, Hacker News commenter
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopHacker News comment
Runs GGUF models in LM Studio with Continue.dev; agent mode needs fast token generation, so they use it only on the RTX machine.
Practitioner account, pseudonymous; direct use; counts toward Operational control
Positive
wongarsu, Hacker News commenter using an employer's GPU server
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopHacker News comment
Connects continue.dev to an employer's Ollama GPU server, ignores the login prompts, and sets models in config.yaml; qwen2.5-coder 3B handles autocomplete.
Practitioner account, pseudonymous; direct use; counts toward Operational control
Positive
taneq, Hacker News commenter
Comment on: Claudia - Desktop companion for Claude codeHacker News comment
Runs Continue in VSCodium against Ollama, all local, and never signed up for anything.
Practitioner account, pseudonymous; direct use; counts toward Operational control
Mixed
ctbellmar, Hacker News commenter
Comment on: The Claude party is almost overHacker News comment
Qwen3-Coder gives reasonable suggestions in Continue chat, but they have not worked out how to make it call tools.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
reactordev, Hacker News commenter
Comment on: How I code with AI on a budget/freeHacker News comment
Recommends Continue.dev with models on Ollama or LM Studio; some are strong at completion, others reason and use tools, and Continue is their go-to copilot.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mixed
jameslai-dev, for a company that self-hosts its models
Trusted self-signed certificate works for chatting but not for auto-completionGitHub issue
Their company serves Codestral 22B from its own Ollama servers behind an HTTPS proxy; chat in Continue worked well, but autocomplete rejected the same trusted self-signed certificate.
Practitioner account, pseudonymous; direct use; counts toward Operational control
Positive
o_m, Hacker News commenter
Comment on: GitHub Copilot Pro+Hacker News comment
Uses only code completion and recently moved to the Continue extension with local models, which get the job done for free.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
LoungingLemur2, r/LocalLLaMA member
Help with local continue.dev autocompleteReddit post
Chat and code edits on local Ollama models worked flawlessly in Continue, but autocomplete returned no code with Codestral or Qwen2.5-Coder, while Copilot completed correctly.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Adoption and upkeep
Mixed
coder543, Hacker News commenter
Comment on: Zed now predicts your next edit with Zeta, our new open modelHacker News comment
Found codegemma-2b fine as a Continue completion model a few months back, but certainly not as good as Cursor.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Positive
ottah, Hacker News commenter whose company uses Continue internally
Comment on: Building Personal Software with ClaudeHacker News comment
Their company uses Continue internally in IntelliJ IDEs, which they rate among the better open-source options; at home they run it on OpenRouter and local servers.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
codingdave, Hacker News commenter
Comment on: Promising results from DeepSeek R1 for codeHacker News comment
Satisfied with continue.dev and Ollama for chat only: a drop-down switches between small models for syntax and larger ones for harder questions.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control, Adoption and upkeep
Mixed or negative, 3
Mixed
y42, Hacker News commenter
Comment on: Running local models on an M4 with 24GB memoryHacker News comment
Local Qwen models are easy to wire into Continue in VS Code, but for coding the results stay far from Codex or Claude.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
MidKnightXI, Continue user filing a GitHub issue
Qwen 3.5 and Gemma 4 can't call toolsGitHub issue
Qwen 3.5 and Gemma 4 served from LM Studio emitted tool calls that Continue did not register, so agent steps ended in the model's thinking text.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
mjgs, Hacker News commenter
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopHacker News comment
Mostly pairs the Continue extension with cloud models in devcontainers, since local models have not been that great.
Practitioner account, pseudonymous; direct use; not counted, takes no position
Counted for All practitioners.
Positive
SlackingOff123, Hacker News commenter
Comment on: Launch HN: Continue (YC S23) - Create custom AI code assistantsHacker News comment
Uses the Continue extension in IntelliJ and VS Code with their own providers, without the hosted Continue Hub, and finds it great.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
vunderba, Hacker News commenter
Comment on: JetBrains Fleet drops support for Kotlin MultiplatformHacker News comment
Recommends the Continue JetBrains plugin for bring-your-own-key or Ollama, with refactoring, inline edits, retrieval, and chat.
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Positive
ottah, Hacker News commenter whose company uses Continue internally
Comment on: Building Personal Software with ClaudeHacker News comment
Their company uses Continue internally in IntelliJ IDEs, which they rate among the better open-source options; at home they run it on OpenRouter and local servers.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
codingdave, Hacker News commenter
Comment on: Promising results from DeepSeek R1 for codeHacker News comment
Satisfied with continue.dev and Ollama for chat only: a drop-down switches between small models for syntax and larger ones for harder questions.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control, Adoption and upkeep
Positive
SV_BubbleTime, Hacker News commenter
Comment on: A three month review of kagi search and the orion web browser (2024)Hacker News comment
Put US$5 of Claude API credit into the Continue extension and months later had not used it up.
Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits
Mixed
manmal, Hacker News commenter
Comment on: Ask HN: Go deep into AI/LLMs or just use them as tools?Hacker News comment
In Continue.dev, Gemini 2.5 Pro through OpenRouter wrote almost perfect iOS tests where the Copilot agent failed, but a Continue change then broke that workflow.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Positive
itissid, Hacker News commenter
Comment on: Nvidia on NixOS WSL - Ollama up 24/7 on your gaming PCHacker News comment
Hooks a self-hosted Ollama DeepSeek container to Continue for chat and code tasks and mixes in hosted models for completion.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mixed
surak, who runs Helmholtz Blablador and recommends Continue to its users
Local openai LLM assistant option removedGitHub issue
Helmholtz Blablador made Continue the official way for its couple thousand users to reach its OpenAI-compatible service. A 1.0 release removed the UI option to add such an endpoint, leaving only manual config editing.
Practitioner account, pseudonymous; ran the rollout; counts toward Operational control, Adoption and upkeep
Counted for All practitioners.
Positive
phantagom, r/LocalLLaMA member
Continue had been genuinely good to use; after the acquisition they forked it into a completion-only VS Code extension that takes any model and sends no telemetry, and they use it daily.
Vendor material, pseudonymous; direct use; counts toward Adoption and upkeep
Mixed
Benj2005, JetBrains plugin user
Comment on: IntelliJ IDEA 2026.2.1 : Continue crashesGitHub issue comment
Fixed the JetBrains plugin issue by explicitly marking JCEF as a dependency in plugin.xml and building the plugin. Says commit cb273098d968906d25ee737b454f0b5f13ea2482 worked fine for them, for anyone having trouble building from the latest 2.x.x commits.
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Mixed
sridattasp, for a team that built tooling on Continue's data files
Their team built AI traceability on Continue's local session.json and autocomplete.jsonl files and asked, after the acquisition, whether future releases keep them.
Practitioner account, pseudonymous; ran the rollout; not counted, takes no position
Positive
dust42, Hacker News commenter
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopHacker News comment
Uses continue.dev with a local Qwen3-Coder 30B at about 50 tokens a second, chosen because it lets them set their own short system prompt.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Operational control
Mixed
Hakenadu, who provisions Continue for a company's developers
Add a configuration flag to hide the "Login to Continue Hub"-InfoGitHub issue
Provisions developers with a pre-generated config.yaml for the company's EU LLM gateway and, for regulatory reasons, asked for a setting to hide the Continue Hub sign-in prompt.
Practitioner account, pseudonymous; ran the rollout; counts toward Operational control
Counted for All practitioners.
Positive, 4
Mixed
beeboop0, Hacker News commenter
Comment on: The future of software development is software developersHacker News comment
Disabled DeepSeek 3.1's file writes in Continue, but its ability to read project files helps it find the nature of bugs.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Positive
colgandev, Hacker News commenter
Comment on: The new skill in AI is not prompting, it's context engineeringHacker News comment
Finds success dictating prompts and using continue.dev or Aider to supply context from project files.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Positive
the_renaissance_jack, r/LocalLLaMA member
Scrapping for local RAG?Reddit post
Points Continue's built-in documentation scraper at a URL and queries the saved docs, and wants the same for other local projects.
Practitioner account, pseudonymous; direct use; not counted, takes no position
Positive
dabockster, Hacker News commenter
Comment on: New junior developers can't codeHacker News comment
An offline setup of Ollama, Qwen Coder 14B, and Continue.dev explains its changes with the codebase as context, slowly but at no cost.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control
Mixed or negative, 2
Negative
SlimPerceptions, r/LocalLLaMA member
Can't get continue.dev to index my codebaseReddit post
After a day of troubleshooting, Continue still would not index the codebase, the feature it was installed for, even after a rebuild of the index.
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Negative
drplan, r/LocalLLaMA member
Ideal setup for local LLM Coding Assistant.Reddit post
Wanting Cursor-like coding with local inference and no telemetry, they found Continue and Cline only about 30% as enjoyable, blaming weaker codebase indexing and dumber local models.
Practitioner account, pseudonymous; direct use; not counted, takes no position
Counted for All practitioners.
Positive, 4
Mixed
omneity, Hacker News commenter
Comment on: Claudia - Desktop companion for Claude codeHacker News comment
Continue.dev does a decent job at autocomplete, but it needs a fast, large-context model that a fully local setup cannot yet run well.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Positive
phantagom, r/LocalLLaMA member
Continue had been genuinely good to use; after the acquisition they forked it into a completion-only VS Code extension that takes any model and sends no telemetry, and they use it daily.
Vendor material, pseudonymous; direct use; counts toward Adoption and upkeep
Positive
o_m, Hacker News commenter
Comment on: GitHub Copilot Pro+Hacker News comment
Uses only code completion and recently moved to the Continue extension with local models, which get the job done for free.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Positive
atmanactive, Hacker News commenter
Comment on: Ask HN: Open-Source editor with local code completion?Hacker News comment
Has run Continue on Ollama in VSCodium for a few weeks and finds it much better than TabNine.
Practitioner account, pseudonymous; direct use; not counted, takes no position
Mixed or negative, 11
Negative
dataflow, Hacker News commenter
Comment on: Qwen3.6-35B-A3B: Agentic coding power, now open to allHacker News comment
New to the models in the thread and lost on how to code with them: using them with Continue in VS Code on basic C, gets nonsensical autocompletions that end in a stray </fim_prefix> token.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Negative
KronisLV, Hacker News commenter
Comment on: A guide to local coding modelsHacker News comment
For local autocomplete they find no good software: Continue.dev autocomplete with Ollama is buggy and poor, and other agents do not offer completion.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
AIxHunter, Continue user filing a GitHub issue
Continue dev plugin: autocompletion is making VS-Code slowGitHub issue
With Codestral autocomplete on, VS Code became so laggy that saving and copy-paste took several attempts; disabling the plugin restored it.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
LoungingLemur2, r/LocalLLaMA member
Help with local continue.dev autocompleteReddit post
Chat and code edits on local Ollama models worked flawlessly in Continue, but autocomplete returned no code with Codestral or Qwen2.5-Coder, while Copilot completed correctly.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Adoption and upkeep
Negative
VirtualPanic6798, r/ChatGPTCoding member
Continue.Dev autocomplete too wastefull, going back to CopilotReddit post
To save on a US$10 Copilot plan they ran Continue autocomplete on Codestral through OpenRouter; it used US$3 of credit in three days with runaway suggestions, so they went back to Copilot.
Practitioner account, pseudonymous; direct use; counts toward Reliability, Cost predictability and limits
Negative
1Blue3Brown, r/LocalLLaMA member
Why does Zed's new LLM work great on their IDE and terrible with VS Code's ContinueReddit post
Zed's open Zeta completion model gave correct suggestions inside Zed but nonsense in Continue, such as imports suggested mid-file for modules already imported.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
coder543, Hacker News commenter
Comment on: Zed now predicts your next edit with Zeta, our new open modelHacker News comment
Found codegemma-2b fine as a Continue completion model a few months back, but certainly not as good as Cursor.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Negative
ChangeIsHard_, r/LocalLLaMA member
Local auto-complete for coding?Reddit post
On two RTX 4090s, chat with Qwen2.5-Coder-32B was workable, but every attempt at autocomplete in Continue either spun without suggestions or produced irrelevant ones.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Negative
theboldestgaze, r/LocalLLaMA member
Any joy with continue.dev?Reddit post
After a few days on local models, the poster found Continue fast but its tab completions useless, even after following the official recommendations.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
eslamo, Continue user filing a GitHub issue
Jetbrains freeze on autocompleteGitHub issue
JetBrains froze whenever Continue's autocomplete fired with a local qwen2.5-coder model; disabling the plugin fixed the IDE.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
MainManu, r/LocalLLaMA member
Replacing github copilot with continue.dev issuesReddit post
Trying to replace Copilot with Continue on Ollama, the poster got chat working but not inline autocomplete. Found the docs silent on running a chat and a completion model side by side.
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Every concern practitioners raise, most raised first.
Counted for All practitioners.
Negative
jwickster, Agent mode user
Continue 2.0.0 issue: Agent mode file tools fail with a local modelGitHub issue
On Continue 2.0.0 in VS Code Agent mode with a local LM Studio model, file tool calls repeatedly went out with missing or empty arguments. The author reports that the agent retried on speculation, leaving the exact error unreported, and says it "did not initially complete a verified write-and-reread cycle".
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Negative
anigbrowl, Hacker News commenter
Comment on: Computer use in Gemini 3.5 FlashHacker News comment
After paying for the Gemini API, the second headache was a lot of frustration with the Continue plugin in the IDE.
Practitioner account, pseudonymous; direct use; not counted, takes no position
Negative
liar666, running a coding agent on a self-hosted model server
Continue CLI does not work with external OpenAI-compatible model (Error: 400 status code (no body))GitHub issue
Reports that the cn CLI 1.5.47 fails with a 400 error against an OpenAI-compatible model on their own server that works perfectly in the "VSCod(ium) continue plugin", making the tool completely unusable. Notes similar reports were closed for lack of activity.
Practitioner account, pseudonymous; direct use; counts toward Reliability, Adoption and upkeep
Negative
Jorlen, r/LocalLLaMA member
If you use continue.dev and Qwen 3.6 (dense / MoE) - I could use your helpReddit post
Tried Continue for tighter context control than Roo Code; with Qwen 3.6 it stopped after thinking on any coding call and froze when applying code blocks.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Negative
HEAVYlight123, r/LocalLLaMA member
Any simple alternatives to Continue.dev?Reddit post
Continue had worked well, but updates hid the config file and truncated prompts despite a set context length, so they are looking to leave before it gets worse for local use.
Practitioner account, pseudonymous; direct use; counts toward Reliability, Adoption and upkeep
Negative
No_Flight_4473, r/vscode member
Continue.dev is buggy, but I still want an open source AI in my IDEReddit post
Loved Continue as an open-source Copilot but found features breaking or regressing every week, and is looking for something steadier.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
manmal, Hacker News commenter
Comment on: Ask HN: Go deep into AI/LLMs or just use them as tools?Hacker News comment
In Continue.dev, Gemini 2.5 Pro through OpenRouter wrote almost perfect iOS tests where the Copilot agent failed, but a Continue change then broke that workflow.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Mixed
jameslai-dev, for a company that self-hosts its models
Trusted self-signed certificate works for chatting but not for auto-completionGitHub issue
Their company serves Codestral 22B from its own Ollama servers behind an HTTPS proxy; chat in Continue worked well, but autocomplete rejected the same trusted self-signed certificate.
Practitioner account, pseudonymous; direct use; counts toward Operational control
Negative
dimal, Hacker News commenter
Comment on: Launch HN: Continue (YC S23) - Create custom AI code assistantsHacker News comment
Liked Continue's customizability, but almost every return after a few weeks away found the extension broken; after many reinstalls they moved to Cody.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
codingdave, Hacker News commenter
Comment on: Find and execute shell commands using OllamaHacker News comment
Runs Ollama behind continue.dev; it works, but often proposes one block of code and writes a different one into the file.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Negative
overgard, Hacker News commenter
Comment on: Open-weight AI is having its Kubernetes momentHacker News comment
Says the harness matters: the Continue VS Code extension worked horribly with a local Qwen, so they settled on Pi.
Practitioner account, pseudonymous; direct use; not counted, takes no position
Negative
calenti, Hacker News commenter
Comment on: Ask HN: Has anyone replaced Claude/GPT with a local model for daily coding?Hacker News comment
Was using Continue until the acquisition; its VS Code chat is now choking on Ollama responses.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Negative
KronisLV, Hacker News commenter
Comment on: A guide to local coding modelsHacker News comment
For local autocomplete they find no good software: Continue.dev autocomplete with Ollama is buggy and poor, and other agents do not offer completion.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
bdavj, contributor reporting for a set of managed endpoints
[JetBrains] Sidebar panel frequently freezes across all OS'GitHub issue
IntelliJ froze three to four times a day across a set of Mac and PC endpoints running Continue, needing a full restart; the issue spanned many versions.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
wiradikusuma, Hacker News commenter
Comment on: Google Is Winning on Every AI FrontHacker News comment
Chatting with Gemini Pro 2.5 Exp in the Continue IntelliJ plugin, found it even suggested improvements in other files in context, but more often than not stopped halfway, leaving unusable code. Unsure whether the plugin is the cause, but it never happens with Claude.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Mixed
AIxHunter, Continue user filing a GitHub issue
Continue dev plugin: autocompletion is making VS-Code slowGitHub issue
With Codestral autocomplete on, VS Code became so laggy that saving and copy-paste took several attempts; disabling the plugin restored it.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
KronisLV, Hacker News commenter
Comment on: JetBrains Fleet drops support for Kotlin MultiplatformHacker News comment
Likes Continue.dev with Ollama on a server, but finds it buggy in JetBrains: the SonarQube plugin breaks it and shortcut hints linger on screen.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
cobrafast, Continue user filing a GitHub issue
Continue freezes IDEGitHub issue
Continue 0.0.88 randomly froze JetBrains Rider so completely that it had to be killed from Task Manager; the problem was absent with the plugin off and on 0.0.83.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Counted for All practitioners.
Mixed
pilkyton, r/LocalLLaMA member
Continue was bought by Cursor. What do I do now?Reddit post
Called Continue the best open-source AI coding extension and asks whether to stay on the final release or move, now that Cursor owns it.
not counted until substantiated
Mixed
roscas, Hacker News commenter
Continue coding agent is dead. Alternatives?Hacker News post
Found Continue nice in VS Code with offline Ollama, then learned it is no longer updated and asked for alternatives.
Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep
Positive
phantagom, r/LocalLLaMA member
Continue had been genuinely good to use; after the acquisition they forked it into a completion-only VS Code extension that takes any model and sends no telemetry, and they use it daily.
Vendor material, pseudonymous; direct use; counts toward Adoption and upkeep
Mixed
Ignacio Heredia, researcher on the AI4EOSC platform at IFCA
Prepare dev-env for ARENAGitHub issue, ai4os/ai4os-dev-env
Ignacio Heredia opened an AI4EOSC platform issue to replace Continue as the VS Code extension for using AI4EOSC models as a code assistant, because Continue was discontinued after Cursor acquired it. His first choice was GitHub Copilot, for its VS Code integration and support for OpenAI-compatible endpoints.
"…as it got acquired by Cursor. So we should: * select a new extension to replace continue…"
"Copilot: my initial preferred option as it is very well integrated with VSCode and support OpenAI compatible endpoints…"
Practitioner account, pseudonymous; opinion; not counted until substantiated
Mixed
kpatucha, Hacker News commenter
Comment on: Ask HN: Is anyone experimenting with different ways of using LLMs for coding?Hacker News comment
Installed the continue.dev extension with a local model to try tab completion, noting the project was killed and will not be continued.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mixed
primadg, for a team at Cedra
Comment on: Suggestion to make a proper forkGitHub issue comment
Says their team at Cedra plans to fork Continue and continue its development.
Practitioner account, pseudonymous; opinion; not counted, takes no position
Mixed
sridattasp, for a team that built tooling on Continue's data files
Their team built AI traceability on Continue's local session.json and autocomplete.jsonl files and asked, after the acquisition, whether future releases keep them.
Practitioner account, pseudonymous; ran the rollout; not counted, takes no position
Positive
TobiasFP, Continue user
Suggestion to make a proper forkGitHub issue
Absolutely loved Continue.dev and is sad to see it go; with its discussion section closed, proposes a community fork and offers to help maintain it, though they have never properly contributed to open source.
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Mixed
guy4261, Hacker News commenter
Comment on: Continue has been acquired by CursorHacker News comment
Learned of the acquisition from an email sent because they had projects and leftover credits on continue.dev.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Negative
calenti, Hacker News commenter
Comment on: Ask HN: Has anyone replaced Claude/GPT with a local model for daily coding?Hacker News comment
Was using Continue until the acquisition; its VS Code chat is now choking on Ollama responses.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
Christian Siebmanns, consultant and head of the Web and Mobile competence area at viadee
Der eigene, lokale KI-Coding-Assistent mit ContinueCompany blog post, viadee blog
Ran Continue on local LM Studio models for data protection and found results usable; a later note on the page says Cursor bought and discontinued it and points to OpenCode.
Practitioner account, name and role on their organization's own page; direct use; counts toward Operational control, Adoption and upkeep
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Continue's repository states it is no longer actively maintained and is read-only. The Apache 2.0 code and documentation remain available, and the final 2.1.0 extension is still listed on the VS Code Marketplace and Open VSX. A report that the project ended does not establish that the final release stops working. continuedev/continue on GitHub
Open them in the recordCounted for All practitioners.
Mixed
MidKnightXI, Continue user filing a GitHub issue
Qwen 3.5 and Gemma 4 can't call toolsGitHub issue
Qwen 3.5 and Gemma 4 served from LM Studio emitted tool calls that Continue did not register, so agent steps ended in the model's thinking text.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Negative
Zed_Blade_CBS, r/vscode member
Frustration replacing Github Copilot with local models (with Continue.dev)Reddit post
Trying to replace Copilot with local models in Continue on a 36 GB MacBook, they hit context-window errors and memory lockups, and found local results well below Copilot's.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
warpanomaly, r/LocalLLaMA member
I Can't Get Ollama running through Continue to write complex codeReddit post
Qwen3 Coder 30B through Continue handled routine functions and refactors well, but on a complex join it agreed with the user and wrote no code.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
Balinares, Hacker News commenter
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopHacker News comment
Under continue.dev, Qwen3 Coder needs constant reminders to invoke its tools.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
reactordev, Hacker News commenter
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopHacker News comment
Runs GGUF models in LM Studio with Continue.dev; agent mode needs fast token generation, so they use it only on the RTX machine.
Practitioner account, pseudonymous; direct use; counts toward Operational control
Negative
Karl08534, r/LocalLLaMA member
VS Code, Continue, Local LLMs on a Mac. What can I expect?Reddit post
On a 128 GB Mac Studio, neither gpt-oss 120B nor Qwen3 Coder 30B in Continue could convert one 825-line file to an ES6 module, in chat or agent mode. That left them highly disappointed.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Mixed
planetf1a, r/LocalLLaMA member
continue.dev agent mode + ??agentReddit post
Tried a variety of mostly local models with Continue's agent mode but struggles to get anything remotely useful because Continue and the model misinterpret each other. Finds the Qwen3 code A3B-30B model interesting for chat, but it struggles with tool calls.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
wiradikusuma, Hacker News commenter
Comment on: Google Is Winning on Every AI FrontHacker News comment
Chatting with Gemini Pro 2.5 Exp in the Continue IntelliJ plugin, found it even suggested improvements in other files in context, but more often than not stopped halfway, leaving unusable code. Unsure whether the plugin is the cause, but it never happens with Claude.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Mixed
beeboop0, Hacker News commenter
Comment on: The future of software development is software developersHacker News comment
Disabled DeepSeek 3.1's file writes in Continue, but its ability to read project files helps it find the nature of bugs.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
omneity, Hacker News commenter
Comment on: Claudia - Desktop companion for Claude codeHacker News comment
Continue.dev does a decent job at autocomplete, but it needs a fast, large-context model that a fully local setup cannot yet run well.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Counted for All practitioners.
Raised as a concern, 10
Mixed
Silly-Ad667, evaluating tools for a financial services team
Tried a few copilot alternatives after our security team blocked GitHub's data retentionReddit post
After compliance blocked Copilot at their financial services firm, they spent a month on alternatives. Continue let the team use its own models but took more configuring than coding, so the team chose Tabnine.
Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep
Negative
unethical_ban, Hacker News commenter
Comment on: Claudia - Desktop companion for Claude codeHacker News comment
Could not find a fully private setup: even for local models, the Continue extension insisted on a sign-in to its service.
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Mixed
ctbellmar, Hacker News commenter
Comment on: The Claude party is almost overHacker News comment
Qwen3-Coder gives reasonable suggestions in Continue chat, but they have not worked out how to make it call tools.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mixed
surak, who runs Helmholtz Blablador and recommends Continue to its users
Local openai LLM assistant option removedGitHub issue
Helmholtz Blablador made Continue the official way for its couple thousand users to reach its OpenAI-compatible service. A 1.0 release removed the UI option to add such an endpoint, leaving only manual config editing.
Practitioner account, pseudonymous; ran the rollout; counts toward Operational control, Adoption and upkeep
Mixed
MainManu, r/LocalLLaMA member
Replacing github copilot with continue.dev issuesReddit post
Trying to replace Copilot with Continue on Ollama, the poster got chat working but not inline autocomplete. Found the docs silent on running a chat and a completion model side by side.
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Negative
dataflow, Hacker News commenter
Comment on: Qwen3.6-35B-A3B: Agentic coding power, now open to allHacker News comment
New to the models in the thread and lost on how to code with them: using them with Continue in VS Code on basic C, gets nonsensical autocompletions that end in a stray </fim_prefix> token.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
fragglerock, r/LocalLLaMA member
Continue.dev CLI with no account, is it possible?Reddit post
Runs the Continue extension in VSCodium against a local model so nothing reaches the large vendors, but the CLI demanded an external sign-in before it would start.
Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep
Negative
SlimPerceptions, r/LocalLLaMA member
Can't get continue.dev to index my codebaseReddit post
After a day of troubleshooting, Continue still would not index the codebase, the feature it was installed for, even after a rebuild of the index.
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Mixed
ron-zhong, who preconfigures Continue for users in an air-gapped network
Comment on: Add a configuration flag to hide the "Login to Continue Hub"-InfoGitHub issue comment
Their team preconfigures Bedrock models for users in an air-gapped network, and the sign-in page confused users who could not reach Continue's website.
Practitioner account, pseudonymous; ran the rollout; not counted, repeats a stronger account
Mixed
Hakenadu, who provisions Continue for a company's developers
Add a configuration flag to hide the "Login to Continue Hub"-InfoGitHub issue
Provisions developers with a pre-generated config.yaml for the company's EU LLM gateway and, for regulatory reasons, asked for a setting to hide the Continue Hub sign-in prompt.
Practitioner account, pseudonymous; ran the rollout; counts toward Operational control
Discussed without concern, 1
Positive
wongarsu, Hacker News commenter using an employer's GPU server
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopHacker News comment
Connects continue.dev to an employer's Ollama GPU server, ignores the login prompts, and sets models in config.yaml; qwen2.5-coder 3B handles autocomplete.
Practitioner account, pseudonymous; direct use; counts toward Operational control
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.The final release pulled out authentication and anonymous telemetry, so the sign-in prompts some sources describe are gone. Models, rules, and tools are set in a local config.yaml. A report of setup effort does not establish that a working configuration cannot be shared. continuedev/continue on GitHub
Open them in the recordCounted for All practitioners.
Raised as a concern, 7
Mixed
ecampidoglio, JetBrains Rider user
JetBrains plugin fails to load in 2026.2 IDEs with NoClassDefFoundError: com/intellij/ui/jcef/JBCefAppGitHub issue
Traced why Continue 1.0.67 crashes on JetBrains 2026.2 IDEs to a missing JCEF dependency in plugin.xml. Patching the one line into the installed plugin made it load normally in Rider 2026.2, and the author says a PR with the fix will follow.
Practitioner account, pseudonymous; structured test; counts toward Reliability
Mixed
Benj2005, JetBrains plugin user
Comment on: IntelliJ IDEA 2026.2.1 : Continue crashesGitHub issue comment
Fixed the JetBrains plugin issue by explicitly marking JCEF as a dependency in plugin.xml and building the plugin. Says commit cb273098d968906d25ee737b454f0b5f13ea2482 worked fine for them, for anyone having trouble building from the latest 2.x.x commits.
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Mixed
bdavj, contributor reporting for a set of managed endpoints
[JetBrains] Sidebar panel frequently freezes across all OS'GitHub issue
IntelliJ froze three to four times a day across a set of Mac and PC endpoints running Continue, needing a full restart; the issue spanned many versions.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
eslamo, Continue user filing a GitHub issue
Jetbrains freeze on autocompleteGitHub issue
JetBrains froze whenever Continue's autocomplete fired with a local qwen2.5-coder model; disabling the plugin fixed the IDE.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
KronisLV, Hacker News commenter
Comment on: JetBrains Fleet drops support for Kotlin MultiplatformHacker News comment
Likes Continue.dev with Ollama on a server, but finds it buggy in JetBrains: the SonarQube plugin breaks it and shortcut hints linger on screen.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
cobrafast, Continue user filing a GitHub issue
Continue freezes IDEGitHub issue
Continue 0.0.88 randomly froze JetBrains Rider so completely that it had to be killed from Task Manager; the problem was absent with the plugin off and on 0.0.83.
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
sebastian-loncar, r/ChatGPTCoding member
My Experience Evaluating Coding Assistants for JetBrains IntegrationReddit post
Comparing assistants in JetBrains IDEs, they found Continue the only plugin with an Apply button, but it was very slow and changed unrelated code, so they settled on Cursor beside JetBrains.
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Discussed without concern, 2
Positive
vunderba, Hacker News commenter
Comment on: JetBrains Fleet drops support for Kotlin MultiplatformHacker News comment
Recommends the Continue JetBrains plugin for bring-your-own-key or Ollama, with refactoring, inline edits, retrieval, and chat.
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Positive
Sn0wCoder, Hacker News commenter
Comment on: Things we learned about LLMs in 2024Hacker News comment
Calls the Continue plugin the best AI option for IntelliJ, running local Phind and StarCoder models on a separate machine.
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Statements this group's sources agree on, then the ones close to agreement.
Close to agreement: each needs 19 supporting sources
Developers and teams pick Continue so code and prompts stay on their own machines or on model endpoints their company controls.
14 supporting sourcesPeople run Continue as an open-source stand-in for GitHub Copilot on a model they bring, often where Copilot is not allowed or not paid for.
9 supporting sourcesQuestions the sources split on, with the count on each side.
Evidence remains mixed
Local models work, 8 sources
Many report usable chat and completion from Qwen, DeepSeek, Devstral, or Code Llama on their own hardware or a company server.
Frontier models needed, 7 sources
Others found local models slow or inaccurate and moved their coding work to GPT, Claude, or Codex.
Evidence remains mixed
Stayed with Continue, 4 sources
Some tried Cursor, Copilot, or Cody and came back to Continue for model control and their own editor; after the acquisition, others proposed a community fork to keep it.
Moved to another tool, 11 sources
Others left for Cline, Cursor, Zed, Claude Code, or OpenCode, citing stability, agent features, or the end of the project.
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 6 accounts; GILD prints their sentiment from 20.
13 sources. These accounts focus on model endpoints a company controls, rollout effort, and what changes for a team now that Continue is no longer maintained.
82 sources. These accounts focus on local and self-hosted models, model choice per role, autocomplete quality, and reliability in day-to-day use.
95 sources. This gives the broadest read, combining individual builders with the few team and leadership accounts.
95 sources from practitioners, by the context they work in. Filled rows count for this group.
Emphasizes Local models, model choice per role, and autocomplete quality
Emphasizes Company gateways, proxies, certificates, and tooling built on Continue's files
Emphasizes An EU research platform replacing Continue after the end of maintenance
Emphasizes Local models for data protection, and the move away after the acquisition
Emphasizes A research model service that recommended Continue to a couple thousand users
What changes with scale. Individual builders emphasize local models, model choice, and autocomplete quality. Team accounts move to the work of wiring Continue to endpoints the company controls, such as Amazon Bedrock, an internal gateway, or a shared GPU server. They also discuss what becomes of their tooling now that the project is frozen.
Where this group's sources were published.
Counted for All practitioners, from 95 sources. Change group
112 sources for this group, 17 of them documentation
Older evidence is retained when it still applies to the final release. Sources that depend on behavior the final release removed, or on bugs reported in issues since closed, stay in the history, marked Needs a recheck.
See sources by originWho each source is, how it knows, whether it still applies and what it counts toward.
Newest first, on its own page. Every count above opens its sources there.
Read all 112 sourcesAbout this read
A running review of what engineering teams report about Continue, from individual builders to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Flagged for a recheck, of the sources that take a side: leaders and teams 1 of 6, individual builders 6 of 63, all practitioners 7 of 69.
Each row opens its sources for the group you are reading.
| Finding | Engineering leaders and teams | Individual builders | All practitioners | Sources |
|---|---|---|---|---|
| Current readCurrent sentiment | 1 positive, 5 mixed, 0 negative | 17 positive, 23 mixed, 23 negative | 18 positive, 28 mixed, 23 negative | Sources |
| PraiseLocal and Self-Hosted Models | 4 of 4 positive (under the minimum) | 24 of 27 positive | 28 of 31 positive | Sources |
| PraiseModel and Provider Choice | 2 of 2 positive (under the minimum) | 6 of 6 positive | 8 of 8 positive | Sources |
| PraiseTab Autocomplete | 0 of 0 positive (under the minimum) | 4 of 15 positive | 4 of 15 positive | Sources |
| PraiseOpen Source and Configurable | 2 of 2 positive (under the minimum) | 3 of 3 positive (under the minimum) | 5 of 5 positive | Sources |
| PraiseCodebase and Docs Context | 0 of 0 positive (under the minimum) | 4 of 6 positive | 4 of 6 positive | Sources |
| ConcernReliability and Update Regressions | 2 of 2 raise it (under the minimum) | 16 of 16 raise it | 18 of 18 raise it | Sources |
| ConcernSetup and Configuration Effort | 4 of 5 raise it | 6 of 6 raise it | 10 of 11 raise it | Sources |
| ConcernResults Depend on the Model | 0 of 0 raise it (under the minimum) | 10 of 10 raise it | 10 of 10 raise it | Sources |
| ConcernJetBrains Plugin Stability | 1 of 1 raise it (under the minimum) | 6 of 8 raise it | 7 of 9 raise it | Sources |
| ConcernEnd of Maintenance | 4 of 4 raise it (under the minimum) | 7 of 7 raise it | 11 of 11 raise it | Sources |
| ConsensusUsed in place of Copilot | 0 supporting (under the minimum) | 9 supporting (below threshold) | 9 supporting (below threshold) | Sources |
| ConsensusChosen to keep code in-house | 8 supporting | 6 supporting (below threshold) | 14 supporting (below threshold) | Sources |
| DisagreementAre local or open-weight models good enough in Continue? | Local models work 1, Frontier models needed 0 (under the minimum) | Local models work 7, Frontier models needed 7 | Local models work 8, Frontier models needed 7 | Sources |
| DisagreementDoes Continue stay the main assistant, or does work move to another tool? | Stayed with Continue 1, Moved to another tool 3 (under the minimum) | Stayed with Continue 3, Moved to another tool 8 | Stayed with Continue 4, Moved to another tool 11 | Sources |
| DisagreementDoes Continue save time once its rough edges are counted? | Time saved 0, Gain absorbed 0 (under the minimum) | Time saved 0, Gain absorbed 2 (under the minimum) | Time saved 0, Gain absorbed 2 (under the minimum) | Sources |
| Current readEvidence mix | 30 sources | 99 sources | 112 sources | Sources |
GILD's checks of claims against official documentation, kept apart from the source counts.
