Skip to main content
Continue SignalsBack to the read

Every source behind the read

Every source GILD analyzed, newest first. Each says who the source is, how it knows, whether it still applies and which findings it counts toward. Open a count to see only its sources.

Whose sources count

Source

112 sources in All practitioners, with product documentation Showing all 112 sources

  1. 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".

    Published Sep 28, 2026self-described: VS Code Agent mode on a local model through LM Studio, filesystem MCP enabled

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Artifact checked (log); Observed on 2.0.0
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (log)
    Date and version
    2026-09-28, 2.0.0
    Counts toward
    Delivered outcomes, task completion: unfavorable, G3 (3 units before bounds)
    Counts toward
    Reliability, run stability: unfavorable, G2 (2 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Continue 2.0.0, local model in LM Studio

  2. 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.

    Published Aug 24, 2026self-described: Rider 2026.2 on macOS

    Practitioner account, pseudonymous; structured test; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Ran a structured test; Artifact checked (log); Observed on 1.0.67
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran a structured test
    Support
    1 artifact (log)
    Date and version
    2026-08-24, 1.0.67
    Counts toward
    Reliability, regressions: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    JetBrains plugin 1.0.67, Rider 2026.2

  3. 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.

    Published Aug 23, 2026self-described: VS Code with a Gemini API key and workspace context

    not counted until substantiated How GILD checked it
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-08-23
    Not counted
    Adoption and upkeep, continuity: a lead (G0), counts toward nothing until substantiated

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current

  4. 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.

    Published Aug 22, 2026self-described: VS Code with offline Ollama

    Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-08-22
    Counts toward
    Adoption and upkeep, continuity: unfavorable, G2 (2 units before bounds)
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Ollama

  5. Positive

    phantagom, r/LocalLLaMA member

    I got fed up with locked-down autocomplete, so I forked Continue and stripped it down to just tab-completionReddit post

    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.

    Published Aug 21, 2026self-described: Daily tab completion in VS Code on a model of their choice

    Vendor material, pseudonymous; direct use; counts toward Adoption and upkeep How GILD checked it
    Origin
    Vendor material
    Checked
    Pseudonymous; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    vendor published (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-08-21
    Counts toward
    Adoption and upkeep, continuity: unfavorable, G2 (2 units before bounds), capped: C-relationship

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current

  6. 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.

    Published Aug 15, 2026self-described: IntelliJ IDEA 2026.2

    Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Observed on 2.x.x
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-08-15, 2.x.x
    Counts toward
    Adoption and upkeep, setup: unfavorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    JetBrains plugin 1.0.67, IntelliJ IDEA 2026.2

  7. 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…"
    Excerpt, Ignacio Heredia
    "Copilot: my initial preferred option as it is very well integrated with VSCode and support OpenAI compatible endpoints…"
    Same speaker

    Published Aug 7, 2026EU research AI platform that offers its own hosted models as a code assistant in VS Code

    Practitioner account, pseudonymous; opinion; not counted until substantiated How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Opinion; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Opinion, no use stated
    Support
    1 artifact (organization page)
    Date and version
    2026-08-07
    Not counted
    Adoption and upkeep, continuity: a lead (G0), counts toward nothing until substantiated

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Professional team
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Continue as the documented VS Code code assistant for AI4EOSC models

  8. 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.

    Published Jul 25, 2026self-described: MacBook, local Qwen 3.6 27B

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-07-25
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Qwen 3.6 27B

  9. 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.

    Published Jul 6, 2026self-described: Data and ML work, trying tab completion

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-07-06
    Not counted
    Adoption and upkeep, continuity: repeats a stronger account in its group
    Not counted
    Operational control, models and deployment: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Local model

  10. 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.

    Published Jun 25, 2026self-described: IDE with a paid Gemini API key

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-25
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Gemini API

  11. 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.

    Published Jun 23, 2026self-described: Cedra, planning its own fork

    Practitioner account, pseudonymous; opinion; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Competitor staff: not counted as independent; Opinion
    Role
    Pseudonymous account; identity not pursued
    Relationship
    competitor employee (self disclosed)
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-23
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Very small team
    Evidence
    Reported
    Applies to
    Current

  12. 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.

    Published Jun 22, 2026self-described: cn CLI on Linux Mint and OpenBSD with a self-hosted OpenAI-compatible model

    Practitioner account, pseudonymous; direct use; counts toward Reliability, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Observed on 1.5.47
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (issue)
    Date and version
    2026-06-22, 1.5.47
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Adoption and upkeep, continuity: unfavorable, G2 (2 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    cn CLI 1.5.47

  13. Mixed

    sridattasp, for a team that built tooling on Continue's data files

    Impact of Cursor's Acquisition of Continue on existing customized traceability from session.json and autocomplete.jsonl files?GitHub issue

    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.

    Published Jun 22, 2026self-described: Team traceability solution built on session.json and autocomplete.jsonl

    Practitioner account, pseudonymous; ran the rollout; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Ran the rollout
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran the rollout
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-22
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Very small team
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Continue in VS Code on Windows

  14. 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.

    Published Jun 18, 2026self-described: Filed after the acquisition, once the repository's discussions had closed

    Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-18
    Counts toward
    Adoption and upkeep, continuity: unfavorable, G1 (1 unit before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current

  15. 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.

    Published Jun 18, 2026self-described: Had projects and leftover credits on Continue

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Customer of Continue; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-18
    Not counted
    Adoption and upkeep, continuity: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current

  16. 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.

    Published Jun 17, 2026self-described: Local models

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-17
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance
    Not counted
    Adoption and upkeep, continuity: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Ollama

  17. Mixed

    GaryBluto, Hacker News commenter

    Comment on: Continue has been acquired by CursorHacker News comment

    Had settled on Continue in VS Code to migrate from Copilot Chat less than 30 minutes before revisiting its site and finding the news the thread is about, posted as "Continue has been acquired by Cursor".

    Published Jun 16, 2026self-described: VS Code

    Practitioner account, pseudonymous; opinion; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Opinion
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-16
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current

  18. 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.

    Published May 18, 2026self-described: Qwen 3.6 on llama.cpp, moving from Roo Code

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Specific details; Observed on Qwen 3.6
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-05-18, Qwen 3.6
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Qwen 3.6 27B and 35B-A3B on llama.cpp

  19. 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.

    Published May 11, 2026self-described: M3 with 36GB

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-05-11
    Counts toward
    Delivered outcomes, task completion: mixed, G1 (1 unit before bounds), capped: C-relevance
    Not counted
    Adoption and upkeep, setup: repeats a stronger account in its group

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Qwen and similar local models

  20. 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.

    Published Apr 16, 2026self-described: Newcomer to local models

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Artifact checked (transcript)
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (transcript)
    Date and version
    2026-04-16
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Qwen3.6-35B-A3B

  21. 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.

    Published Apr 13, 2026self-described: LM Studio on a server, VS Code on a MacBook

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Artifact checked (log); Observed on 1.2.22
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (log)
    Date and version
    2026-04-13, 1.2.22
    Counts toward
    Reliability, run stability: unfavorable, G3 (3 units before bounds)

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Continue 1.2.22, LM Studio, Qwen 3.5 9B, Gemma 4 26B

  22. Positive

    Dan Guido, CEO at Trail of Bits

    How we made Trail of Bits AI-native (so far)Company blog post, Trail of Bits Blog

    Guido reports that Trail of Bits' AI Handbook bars Cursor from client code except on blockchain engagements, directing staff to Claude Code or Continue.dev instead.

    "The key part is the usage policy: what tools are approved, what isn’t, especially for sensitive data."
    Excerpt, Dan Guido
    "Cursor can’t be used on client code (except blockchain engagements; use Claude Code or Continue.dev instead)."
    Same speaker

    Published Mar 31, 2026140-person security consultancy with a written AI usage policy for client code

    Practitioner account, name and role on their organization's own page; opinion; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Name and role on their organization's own page; Opinion
    Role
    Name on a page the person does not control; employer on a page the person does not control; role on a page the person does not control (CEO and co-founder)
    Relationship
    customer (self disclosed)
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-03-31
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Engineering Blogs & Reviews
    Who
    Technical leadership
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Company AI Handbook tool policy

  23. 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.

    Published Mar 6, 2026self-described: Financial services company whose compliance team blocked Copilot

    Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-03-06
    Counts toward
    Adoption and upkeep, setup: unfavorable, G1 (1 unit before bounds), capped: C-relationship
    Counts toward
    Operational control, models and deployment: favorable, G1 (1 unit before bounds), capped: C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Very small team
    Evidence
    Reported
    Applies to
    Still applicable

  24. 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.

    Published Feb 27, 2026self-described: MacBook Pro M4 Max with 36 GB, LM Studio and Ollama, company bans DeepSeek

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-02-27
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    qwen2.5-coder 14B and other local models

  25. Mixed

    Gallows4574, Hacker News commenter

    Comment on: How AI assistance impacts the formation of coding skillsHacker News comment

    Was deep into Tabby and Continue.dev early, but after Claude Code with Opus it was hard to go back.

    Published Jan 30, 2026self-described: Local models on flights

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-01-30
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Claude Code with Opus

  26. 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.

    Published Jan 26, 2026self-described: Qwen3 Coder 30B on Ollama with an RTX 5090, VSCodium

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Observed on qwen3-coder:30b
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-01-26, qwen3-coder:30b
    Counts toward
    Delivered outcomes, task completion: mixed, G1 (1 unit before bounds), capped: C-relationship

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Qwen3 Coder 30B on Ollama

  27. Positive

    yowlingcat, Hacker News commenter

    Comment on: GLM-4.7-FlashHacker News comment

    Hears good things about Roo, Cline, and Kilo Code as Cursor alternatives, but still uses Continue out of habit.

    Published Jan 19, 2026self-described: Continue in VS Code, weighing Roo, Cline, and Kilo Code

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-01-19
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  28. 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.

    Published Dec 30, 2025self-described: VS Code

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Observed on Deepseek 3.1
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-30, Deepseek 3.1
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds)
    Counts toward
    Delivered outcomes, context handling: mixed, G1 (1 unit before bounds)
    Not counted
    Operational control, execution control: repeats a stronger account in its group

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    DeepSeek 3.1

  29. 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.

    Published Dec 22, 2025self-described: Local and hosted models

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-22
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama, Qwen

  30. 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.

    Published Nov 25, 2025self-described: Windows 11 laptop with 8 GB VRAM, Ollama models and MCP servers

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Observed on Nemotron-9B; Qwen3-8B; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    1 artifact (repository)
    Date and version
    2025-11-25, Nemotron-9B; Qwen3-8B
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds), capped: C-relationship
    Counts toward
    Delivered outcomes, context handling: favorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Nemotron 9B, Qwen3 8B on Ollama

  31. 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.

    Published Nov 9, 2025self-described: VSCodium with a local llama install

    Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    1 artifact (screenshot)
    Date and version
    2025-11-09
    Counts toward
    Operational control, models and deployment: favorable, G1 (1 unit before bounds), capped: C-relationship
    Counts toward
    Adoption and upkeep, setup: unfavorable, G2 (2 units before bounds), capped: C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck

  32. Positive

    finah1995, r/LocalLLaMA member who uses this setup at work

    IBM Developer - Setting up local co-pilot using Ollama with VS Code (or VSCodium for no telemetry air-gapped) with Continue extension.Reddit post

    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.

    Published Nov 3, 2025self-described: Ollama with Continue in VS Code or VSCodium, Granite and Qwen Coder models

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-11-03
    Counts toward
    Operational control, data control: favorable, G1 (1 unit before bounds), capped: C-relationship
    Counts toward
    Operational control, models and deployment: favorable, G1 (1 unit before bounds), capped: C-relationship

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    IBM Granite, Qwen2.5 Coder on Ollama

  33. 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.

    Published Nov 1, 2025self-described: Qwen3 Coder in agent mode

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Observed on Qwen3 Coder
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-11-01, Qwen3 Coder
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Qwen3 Coder

  34. 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.

    Published Oct 31, 2025self-described: MacBook Air M1 and an RTX 3080 laptop

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-10-31
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    LM Studio GGUF models

  35. 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.

    Published Oct 31, 2025self-described: Employer GPU server running Ollama

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Observed on qwen2.5-coder:3b
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-10-31, qwen2.5-coder:3b
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Very small team
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama, qwen2.5-coder 3B for autocomplete

  36. 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.

    Published Oct 31, 2025self-described: MacBook Pro 64GB, travel and off-grid

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Observed on Qwen3-Coder-30B-A3B Q4 quant; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-10-31, Qwen3-Coder-30B-A3B Q4 quant
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Reliability, service availability: favorable, G1 (1 unit before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Measured
    Applies to
    Still applicable
    Observed on
    llama.cpp, Qwen3-Coder-30B-A3B Q4

  37. 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.

    Published Oct 31, 2025self-described: MacBook Air M4, devcontainers

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-10-31
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    llama.cpp containers; cloud models

  38. 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.

    Published Oct 31, 2025self-described: M2 MacBook Pro, 16GB

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Observed on qwen2.5-coder; mistral:7b-instruct
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-10-31, qwen2.5-coder; mistral:7b-instruct
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    qwen2.5-coder, mistral 7B instruct

  39. 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.

    Published Oct 31, 2025self-described: Work laptop with AMD Strix Halo

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Observed on Qwen3 Coder 30B-3A
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-10-31, Qwen3 Coder 30B-3A
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds)

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Lemonade server, Qwen3 Coder 30B-A3B

  40. 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.

    Published Oct 16, 2025self-described: Local models in a chat panel with @ context

    Practitioner account, pseudonymous; direct use; counts toward Reliability, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-10-16, needs a recheck
    Counts toward
    Reliability, regressions: unfavorable, G1 (1 unit before bounds), capped: C-relationship
    Counts toward
    Adoption and upkeep, continuity: unfavorable, G1 (1 unit before bounds), capped: C-relationship

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  41. 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.

    Published Oct 3, 2025self-described: IntelliJ IDEA on a set of Mac and PC endpoints

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (screenshot)
    Date and version
    2025-10-03, 1.0.46, needs a recheck
    Counts toward
    Reliability, run stability: unfavorable, G2 (2 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Very small team
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Continue 1.0.46, IntelliJ IDEA 2025.2.1, Claude

  42. 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.

    Published Sep 14, 2025self-described: Mac Studio M4 Max with 128 GB, gpt-oss 120B and Qwen3 Coder 30B on Ollama

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-09-14, gpt-oss:120b; qwen3-coder:30b, needs a recheck
    Counts toward
    Delivered outcomes, task completion: unfavorable, G2 (2 units before bounds), capped: C-relationship
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relationship

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    gpt-oss 120B, Qwen3 Coder 30B

  43. 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.

    Published Sep 8, 2025self-described: VSCodium on macOS

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-09-08, codestral, devstral and mistral-small, needs a recheck
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)
    Not counted
    Adoption and upkeep, setup: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama, Codestral, Devstral, Mistral Small

  44. 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.

    Published Sep 4, 2025self-described: VS Code, alongside Aider for agent work

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-09-04, needs a recheck
    Counts toward
    Reliability, regressions: unfavorable, G1 (1 unit before bounds), capped: C-relationship

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  45. 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.

    Published Aug 20, 2025self-described: Local models with LM Studio; LiteLLM to scale across a company

    Practitioner account, name and role on their organization's own page; direct use; counts toward Operational control, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Name and role on their organization's own page; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Name on a page the person does not control; employer on a page the person does not control; role on a page the person does not control (Berater & Kompetenzbereichsleiter Web / Mobile)
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-08-20, needs a recheck
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds), capped: C-relationship
    Counts toward
    Adoption and upkeep, setup: mixed, G2 (2 units before bounds), capped: C-relationship
    Not counted
    Adoption and upkeep, continuity: repeats a stronger account in its group
    Not counted
    Operational control, data control: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Engineering Blogs & Reviews
    Who
    Technical leadership
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Continue in VS Code, LM Studio, Devstral and Qwen 2.5 Coder 1.5B

  46. 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.

    Published Aug 18, 2025self-described: M3 Max, local agent with Roo

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-08-18, needs a recheck
    Counts toward
    Delivered outcomes, task completion: mixed, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Local models

  47. 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.

    Published Aug 17, 2025self-described: LM Studio, wants no accounts

    Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-08-17, needs a recheck
    Counts toward
    Adoption and upkeep, setup: unfavorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    LM Studio

  48. 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.

    Published Aug 17, 2025self-described: VSCodium

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-08-17, needs a recheck
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)
    Not counted
    Adoption and upkeep, setup: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama

  49. 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.

    Published Aug 14, 2025self-described: Local 8B to 14B models on a 32 GB M1 MacBook

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-08-14, needs a recheck
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Qwen3 Coder 30B and smaller local models

  50. Negative

    englishrookie, Hacker News commenter

    Comment on: Ask HN: With all the AI hype, how are software engineers feeling?Hacker News comment

    Struggles to get value from Continue.dev with Gemini 2.0 Flash and often goes back to pasting code into ChatGPT.

    Published Aug 11, 2025self-described: VS Code

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-08-11, Gemini 2.0 Flash, needs a recheck
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Gemini 2.0 Flash

  51. 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.

    Published Aug 11, 2025self-described: LM Studio

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-08-11, Qwen3-Coder, needs a recheck
    Not counted
    Adoption and upkeep, setup: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Qwen3-Coder

  52. 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.

    Published Aug 10, 2025self-described: Own models

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-08-10, needs a recheck
    Not counted
    Operational control, models and deployment: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama or LM Studio, gpt-oss

  53. 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.

    Published Aug 10, 2025self-described: VS Code

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-08-10, bigger Qwen models plus gpt-oss-120b, needs a recheck
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Qwen models, gpt-oss-120b

  54. Mixed

    AstroBen, Hacker News commenter

    Comment on: How I code with AI on a budget/freeHacker News comment

    Finds Zed a step up from continue.dev, noting you can use your own models there too.

    Published Aug 10, 2025self-described: Own models

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-08-10, needs a recheck
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  55. 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.

    Published Jul 29, 2025self-described: VS Code with Qwen2.5 Coder

    Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-07-29, qwen2.5 coder, needs a recheck
    Counts toward
    Adoption and upkeep, setup: unfavorable, G2 (2 units before bounds), capped: C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Qwen2.5 Coder

  56. Positive

    ActorNightly, Hacker News commenter

    Comment on: Ask HN: How do you stay on top of AI tech?Hacker News comment

    Finds VS Code with Continue as capable as any LLM-focused IDE.

    Published Jul 18, 2025self-described: VS Code

    Practitioner account, pseudonymous; opinion; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Opinion; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-07-18, needs a recheck
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Small quantized models

  57. 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.

    Published Jul 6, 2025self-described: Air-gapped environment with preconfigured Amazon Bedrock models

    Practitioner account, pseudonymous; ran the rollout; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Ran the rollout; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran the rollout
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-07-06, needs a recheck
    Not counted
    Operational control, admin control: repeats a stronger account in its group

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Very small team
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Continue 1.x with a hosted sign-in prompt, since removed

  58. 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.

    Published Jul 2, 2025self-described: Company LLM gateway in the EU, developers given a pre-generated config.yaml

    Practitioner account, pseudonymous; ran the rollout; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Ran the rollout; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran the rollout
    Support
    1 artifact (screenshot)
    Date and version
    2025-07-02, needs a recheck
    Counts toward
    Operational control, admin control: unfavorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Very small team
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Continue 1.x with a hosted sign-in prompt, since removed

  59. 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.

    Published Jun 30, 2025self-described: VS Code with speech to text

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-06-30, needs a recheck
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  60. Mixed

    McMezoplayz, r/LocalLLaMA member

    Cursor and Bolt free alternative in VSCodeReddit post

    Installed Continue in place of Copilot on a new 16 GB GPU with DeepSeek R1 8B, and asks which local model works for both Continue and agent extensions.

    Published Jun 15, 2025self-described: RTX 5060 Ti 16 GB with DeepSeek R1 8B on Ollama

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-06-15, needs a recheck
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    DeepSeek R1 8B on Ollama

  61. 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.

    Published Jun 5, 2025self-described: Personal, 2x 3090 GPUs

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-06-05, needs a recheck
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama, vLLM, Devstral

  62. 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.

    Published May 24, 2025self-described: iOS development

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-05-24, Gemini 2.5 Pro, needs a recheck
    Counts toward
    Delivered outcomes, correctness: favorable, G1 (1 unit before bounds)
    Counts toward
    Reliability, regressions: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Gemini 2.5 Pro via OpenRouter

  63. 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.

    Published Apr 12, 2025self-described: IntelliJ plugin

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-04-12, Gemini Pro 2.5 Exp, needs a recheck
    Counts toward
    Delivered outcomes, context handling: favorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Gemini 2.5 Pro; Claude

  64. 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.

    Published Apr 11, 2025self-described: Company-hosted Ollama behind an HTTPS reverse proxy with a self-signed root certificate

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Artifact checked (log); Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (log)
    Date and version
    2025-04-11, 1.0.5, needs a recheck
    Counts toward
    Operational control, models and deployment: unfavorable, G3 (3 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Very small team
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Continue 1.0.5, VS Code 1.99.2, Codestral 22B on Ollama

  65. 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.

    Published Apr 11, 2025self-described: Ollama on a TrueNAS Kubernetes host

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-04-11, needs a recheck
    Not counted
    Operational control, models and deployment: repeats a stronger account in its group

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama DeepSeek for chat; hosted models for completion

  66. 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.

    Published Apr 11, 2025self-described: Ollama on a Mac Mini M4 Pro with 64 GB, no telemetry

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-04-11, needs a recheck
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  67. 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.

    Published Apr 8, 2025self-described: VS Code on Linux

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (screenshot)
    Date and version
    2025-04-08, v1.0.5, needs a recheck
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Continue 1.0.5, Codestral for autocomplete, Gemini 2.0 Flash

  68. 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.

    Published Apr 5, 2025self-described: Code completion only

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-04-05, needs a recheck
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds), capped: C-relevance
    Not counted
    Operational control, models and deployment: repeats a stronger account in its group
    Not counted
    Cost predictability and limits, cost transparency: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Local models

  69. 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.

    Published Mar 27, 2025self-described: RustRover and other JetBrains IDEs on Windows

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Artifact checked (log); Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (log)
    Date and version
    2025-03-27, 1.0.2 - 1.0.6, needs a recheck
    Counts toward
    Reliability, run stability: unfavorable, G3 (3 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Continue 1.0.2 to 1.0.6, qwen2.5-coder 14B

  70. 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.

    Published Mar 27, 2025self-described: IntelliJ and VS Code

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-03-27, needs a recheck
    Not counted
    Operational control, models and deployment: repeats a stronger account in its group

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Own providers

  71. 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.

    Published Mar 27, 2025self-described: Switches between tools

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-03-27, needs a recheck
    Counts toward
    Reliability, regressions: unfavorable, G1 (1 unit before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  72. 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.

    Published Mar 20, 2025self-described: Local Ollama models through an Open WebUI API

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    1 artifact (screenshot)
    Date and version
    2025-03-20, qwen2.5-coder:14b, needs a recheck
    Counts toward
    Adoption and upkeep, setup: unfavorable, G2 (2 units before bounds), capped: C-relationship
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    qwen2.5-coder 14B and Codestral on Ollama

  73. 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.

    Published Mar 14, 2025self-described: Helmholtz Blablador, an OpenAI-compatible model service for German academia

    Practitioner account, pseudonymous; ran the rollout; counts toward Operational control, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Ran the rollout; Needs recheck after 12 months; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran the rollout
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-03-14, latest (1.0.3), needs a recheck
    Counts toward
    Adoption and upkeep, continuity: unfavorable, G2 (2 units before bounds)
    Counts toward
    Adoption and upkeep, setup: unfavorable, G2 (2 units before bounds)
    Counts toward
    Operational control, models and deployment: favorable, G1 (1 unit before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Organization-wide
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Continue 1.0.3, VS Code 1.98.2

  74. 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.

    Published Mar 13, 2025self-described: Local projects with Open WebUI

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-03-13, needs a recheck
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  75. 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.

    Published Feb 27, 2025self-described: Part-time coding in VS Code, Codestral through OpenRouter

    Practitioner account, pseudonymous; direct use; counts toward Reliability, Cost predictability and limits How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-02-27, Mistral: Codestral 2501, needs a recheck
    Counts toward
    Cost predictability and limits, cost predictability: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Codestral 2501 via OpenRouter

  76. Negative

    geuis, Hacker News commenter

    Comment on: Microsoft cancels leases for AI data centers, analyst saysHacker News comment

    Tried the continue.dev extension and Cursor over a year with many models and found the results frustrating and mostly unrelated output.

    Published Feb 24, 2025self-described: Hosted and local models

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-02-24, needs a recheck
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    DeepSeek, Qwen, Claude

  77. Mixed

    remuskaos, Hacker News commenter

    Comment on: Show HN: Cline - Open-Source VS Code AI Coding Agent with a New MCP MarketplaceHacker News comment

    Used Continue.dev for quite a while and liked it, but found Cline's act mode better and had not realized what was missing.

    Published Feb 20, 2025self-described: Long-time Continue user, compared with Cline

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-02-20, needs a recheck
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  78. 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.

    Published Feb 17, 2025self-described: Offline, on-device

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-02-17, Qwen Coder 14b, needs a recheck
    Counts toward
    Delivered outcomes, context handling: favorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama, Qwen Coder 14B

  79. 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.

    Published Feb 16, 2025self-described: Zed's open Zeta model in LM Studio, compared in Zed and in VS Code

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    1 artifact (screenshot)
    Date and version
    2025-02-16, zed-industries_zeta, needs a recheck
    Counts toward
    Delivered outcomes, correctness: unfavorable, G2 (2 units before bounds), capped: C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    zed-industries zeta, Q6_K_L, LM Studio

  80. 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.

    Published Feb 14, 2025self-described: codegemma-2b as the completion model, compared with Cursor

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-02-14, codegemma-2b (base), needs a recheck
    Counts toward
    Delivered outcomes, correctness: mixed, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    codegemma-2b base

  81. 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.

    Published Feb 12, 2025self-described: JetBrains IDEs

    Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Opinion; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-02-12, needs a recheck
    Not counted
    Operational control, models and deployment: repeats a stronger account in its group

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Own keys or Ollama

  82. 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.

    Published Feb 12, 2025self-described: JetBrains IDEs, Ollama on a server

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-02-12, needs a recheck
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance
    Not counted
    Operational control, models and deployment: repeats a stronger account in its group

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama, larger models

  83. 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.

    Published Feb 11, 2025self-described: JetBrains Rider on Windows

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (log)
    Date and version
    2025-02-11, 0.0.88, needs a recheck
    Counts toward
    Reliability, run stability: unfavorable, G2 (2 units before bounds)
    Counts toward
    Reliability, regressions: unfavorable, G2 (2 units before bounds)

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Continue 0.0.88, JetBrains Rider 2024.3.5

  84. 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.

    Published Feb 10, 2025self-described: Company use in IntelliJ IDEs; at home with OpenRouter and local servers

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-02-10, needs a recheck
    Not counted
    Operational control, models and deployment: repeats a stronger account in its group

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Very small team
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    OpenRouter, Ollama, vLLM, llama.cpp

  85. 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.

    Published Feb 4, 2025self-described: Local models on two RTX 4090s in VS Code

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-02-04, needs a recheck
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Qwen2.5-Coder-32B

  86. 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.

    Published Feb 2, 2025self-described: JetBrains IDEs, two days comparing assistants

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-02-02, needs a recheck
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  87. 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.

    Published Jan 31, 2025self-described: Self-hosted Ollama models in VS Code, replacing Copilot

    Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-01-31, needs a recheck
    Counts toward
    Adoption and upkeep, setup: unfavorable, G1 (1 unit before bounds), capped: C-relationship

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  88. 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.

    Published Jan 28, 2025self-described: VS Code, chat only

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-01-28, needs a recheck
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)
    Counts toward
    Adoption and upkeep, setup: favorable, G2 (2 units before bounds)
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama models of several sizes, DeepSeek R1

  89. 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.

    Published Jan 26, 2025self-described: VSCodium

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-01-26, needs a recheck
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama

  90. Negative

    eklavya, Hacker News commenter

    Comment on: Llama.vim - Local LLM-assisted text completionHacker News comment

    After trying the VS Code plugin linked in the thread, disabled the continue.dev extension and Ollama, finding the alternative far faster.

    Published Jan 24, 2025self-described: VS Code

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-01-24, needs a recheck
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama

  91. 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.

    Published Jan 21, 2025self-described: DeepSeek R1 14B as an MLX model on a Mac

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    1 artifact (recording)
    Date and version
    2025-01-21, R1-14b, needs a recheck
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds), capped: C-relationship

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    DeepSeek R1 14B, MLX

  92. 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.

    Published Jan 20, 2025self-described: VS Code

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-01-20, needs a recheck
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Ollama

  93. 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.

    Published Jan 10, 2025self-described: VS Code, Claude API

    Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Specific details; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-01-10, needs a recheck
    Counts toward
    Cost predictability and limits, cost predictability: favorable, G2 (2 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Measured
    Applies to
    Still applicable
    Observed on
    Claude API

  94. 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.

    Published Jan 7, 2025self-described: Continue on local models

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-01-07, needs a recheck
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  95. 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.

    Published Jan 1, 2025self-described: IntelliJ, with a box running local models

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Continue found in GILD's check; Used it directly; Needs recheck after 12 months
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Continue found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-01-01, needs a recheck
    Not counted
    Operational control, models and deployment: repeats a stronger account in its group

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Phind, StarCoder, small embeddings models

Product documentation 17

Pages from Continue Dev, Inc., used to check facts for every group.

  1. Continue (acquired by Cursor)

    States that Cursor acquired Continue, that the Apache 2.0 source and documentation stay on GitHub, that recurring billing is disabled with unused paid credits refunded, and that user data has been deleted.

    Checked Oct 12, 2026

  2. continuedev/continue on GitHub

    The README says the repository is no longer actively maintained and is read-only, and that a final 2.0.0 release removed anonymous telemetry and authentication; it recommends the CLI over the JetBrains plugin.

    Checked Oct 12, 2026

  3. Continue releases on GitHub

    Lists VS Code extension 2.0.0 and 2.1.0 on June 19, 2026, and JetBrains plugin 1.0.67 on March 27, 2026, as the last releases.

    Checked Oct 12, 2026

  5. Continue on Open VSX

    Lists version 2.1.0, published June 19, 2026, with about 1.68 million downloads on October 12, 2026.

    Checked Oct 12, 2026

  7. Model providers overview

    Covers the supported providers, including Anthropic, OpenAI, Azure, Bedrock, Vertex AI, Mistral, Ollama, LM Studio, and llama.cpp, with the roles each can serve.

    Checked Oct 12, 2026

  8. config.yaml reference

    Documents the local config.yaml: models and their roles, context providers, rules, prompts, docs, MCP servers, and development data destinations.

    Checked Oct 12, 2026

  9. Autocomplete setup

    Recommends Codestral through the Mistral API for autocomplete, or qwen2.5-coder 1.5B on Ollama for a local model.

    Checked Oct 12, 2026

  10. How Agent mode works

    Documents the tool handshake: the user approves each tool call unless its policy is Automatic, and Plan mode offers read-only tools only.

    Checked Oct 12, 2026

  11. CLI tool permissions

    Sets out allow, ask, and exclude per tool, with writes and Bash on ask by default, a persistent permissions.yaml, and auto and read-only modes.

    Checked Oct 12, 2026

  12. CLI headless mode

    Documents cn -p for scripts and CI, where tools that would ask for approval are excluded unless explicitly allowed.

    Checked Oct 12, 2026

  13. Rules

    Project rules live as markdown files in .continue/rules, applied always or when relevant.

    Checked Oct 12, 2026

  14. MCP

    Documents MCP servers in .continue/mcpServers over stdio, SSE, or streamable HTTP, including JSON configs copied from Claude, Cursor, or Cline.

    Checked Oct 12, 2026

  15. Development data

    Describes local development data in .continue/dev_data and custom destinations for those events.

    Checked Oct 12, 2026

  16. Running Continue without internet

    Documents installing the extension from a release VSIX and pointing config.yaml at a local model for air-gapped use.

    Checked Oct 12, 2026

  17. FAQs

    Answers how secrets resolve from .env files, which certificate settings apply on corporate networks, and why codebase indexing needs AVX2 on x64 Linux.

    Checked Oct 12, 2026

Source index

Provenance at a glance

Every source GILD read, with the original address and the context used to count it. Open a finding to filter the full cards above. On smaller screens the index lists each source once by name, cohort and date; its full record above carries the address, context and findings.

Provenance for every analyzed Signals source
SourceOriginal URLAuthor and contextWhoPublishedReview dateAppliesFindings
Continue 2.0.0 issue: Agent mode file tools fail with a local modelID dc-92 | Developer Communitiesgithub.com/continuedev/continue/issues/13323jwickster, Agent mode userself-described: VS Code Agent mode on a local model through LM Studio, filesystem MCP enabledIndividual practitionerPublished Sep 28, 2026Assessment reviewed Nov 1, 2026Current
JetBrains plugin fails to load in 2026.2 IDEs with NoClassDefFoundError: com/intellij/ui/jcef/JBCefAppID dc-91 | Developer Communitiesgithub.com/continuedev/continue/issues/13185ecampidoglio, JetBrains Rider userself-described: Rider 2026.2 on macOSIndividual practitionerPublished Aug 24, 2026Assessment reviewed Nov 1, 2026Current
Continue was bought by Cursor. What do I do now?ID dc-90 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1vvvbtj/continue_was_bought_by_cursor_and_then_cursor_was_bought_by/pilkyton, r/LocalLLaMA memberself-described: VS Code with a Gemini API key and workspace contextIndividual practitionerPublished Aug 23, 2026Assessment reviewed Nov 1, 2026Current
Continue coding agent is dead. Alternatives?ID dc-89 | Developer Communitiesnews.ycombinator.com/item?id=49398366roscas, Hacker News commenterself-described: VS Code with offline OllamaIndividual practitionerPublished Aug 22, 2026Assessment reviewed Nov 1, 2026Current
I got fed up with locked-down autocomplete, so I forked Continue and stripped it down to just tab-completionID dc-88 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1vubpn4/i_got_fed_up_with_lockeddown_autocomplete_so_i/phantagom, r/LocalLLaMA memberself-described: Daily tab completion in VS Code on a model of their choiceIndividual practitionerPublished Aug 21, 2026Assessment reviewed Nov 1, 2026Current
Comment on: IntelliJ IDEA 2026.2.1 : Continue crashesID dc-87 | Developer Communitiesgithub.com/continuedev/continue/issues/13119#issuecomment-5301447542Benj2005, JetBrains plugin userself-described: IntelliJ IDEA 2026.2Individual practitionerPublished Aug 15, 2026Assessment reviewed Nov 1, 2026Current
Prepare dev-env for ARENAID ld-02 | Developer Communitiesgithub.com/ai4os/ai4os-dev-env/issues/3Ignacio Heredia, researcher on the AI4EOSC platform at IFCAEU research AI platform that offers its own hosted models as a code assistant in VS CodeProfessional teamPublished Aug 7, 2026Assessment reviewed Nov 1, 2026Current
Comment on: Open-weight AI is having its Kubernetes momentID dc-86 | Developer Communitiesnews.ycombinator.com/item?id=49050931overgard, Hacker News commenterself-described: MacBook, local Qwen 3.6 27BIndividual practitionerPublished Jul 25, 2026Assessment reviewed Nov 1, 2026Current
Comment on: Ask HN: Is anyone experimenting with different ways of using LLMs for coding?ID dc-85 | Developer Communitiesnews.ycombinator.com/item?id=48801622kpatucha, Hacker News commenterself-described: Data and ML work, trying tab completionIndividual practitionerPublished Jul 6, 2026Assessment reviewed Nov 1, 2026Current
Comment on: Computer use in Gemini 3.5 FlashID dc-84 | Developer Communitiesnews.ycombinator.com/item?id=48667192anigbrowl, Hacker News commenterself-described: IDE with a paid Gemini API keyIndividual practitionerPublished Jun 25, 2026Assessment reviewed Nov 1, 2026Current
Comment on: Suggestion to make a proper forkID dc-83 | Developer Communitiesgithub.com/continuedev/continue/issues/12764#issuecomment-4783557686primadg, for a team at Cedraself-described: Cedra, planning its own forkVery small teamPublished Jun 23, 2026Assessment reviewed Nov 1, 2026Current
Continue CLI does not work with external OpenAI-compatible model (Error: 400 status code (no body))ID dc-81 | Developer Communitiesgithub.com/continuedev/continue/issues/12875liar666, running a coding agent on a self-hosted model serverself-described: cn CLI on Linux Mint and OpenBSD with a self-hosted OpenAI-compatible modelIndividual practitionerPublished Jun 22, 2026Assessment reviewed Nov 1, 2026Current
Impact of Cursor's Acquisition of Continue on existing customized traceability from session.json and autocomplete.jsonl files?ID dc-82 | Developer Communitiesgithub.com/continuedev/continue/issues/12876sridattasp, for a team that built tooling on Continue's data filesself-described: Team traceability solution built on session.json and autocomplete.jsonlVery small teamPublished Jun 22, 2026Assessment reviewed Nov 1, 2026Current
Suggestion to make a proper forkID dc-79 | Developer Communitiesgithub.com/continuedev/continue/issues/12764TobiasFP, Continue userself-described: Filed after the acquisition, once the repository's discussions had closedIndividual practitionerPublished Jun 18, 2026Assessment reviewed Nov 1, 2026Current
Comment on: Continue has been acquired by CursorID dc-80 | Developer Communitiesnews.ycombinator.com/item?id=48580219guy4261, Hacker News commenterself-described: Had projects and leftover credits on ContinueIndividual practitionerPublished Jun 18, 2026Assessment reviewed Nov 1, 2026Current
Comment on: Ask HN: Has anyone replaced Claude/GPT with a local model for daily coding?ID dc-78 | Developer Communitiesnews.ycombinator.com/item?id=48573138calenti, Hacker News commenterself-described: Local modelsIndividual practitionerPublished Jun 17, 2026Assessment reviewed Nov 1, 2026Current
Comment on: Continue has been acquired by CursorID dc-77 | Developer Communitiesnews.ycombinator.com/item?id=48563348GaryBluto, Hacker News commenterself-described: VS CodeIndividual practitionerPublished Jun 16, 2026Assessment reviewed Nov 1, 2026Current
If you use continue.dev and Qwen 3.6 (dense / MoE) - I could use your helpID dc-76 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1tgkyud/if_you_use_continuedev_and_qwen_36_dense_moe_i/Jorlen, r/LocalLLaMA memberself-described: Qwen 3.6 on llama.cpp, moving from Roo CodeIndividual practitionerPublished May 18, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Running local models on an M4 with 24GB memoryID dc-75 | Developer Communitiesnews.ycombinator.com/item?id=48091480y42, Hacker News commenterself-described: M3 with 36GBIndividual practitionerPublished May 11, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Qwen3.6-35B-A3B: Agentic coding power, now open to allID dc-74 | Developer Communitiesnews.ycombinator.com/item?id=47793569dataflow, Hacker News commenterself-described: Newcomer to local modelsIndividual practitionerPublished Apr 16, 2026Assessment reviewed Nov 1, 2026Still applicable
Qwen 3.5 and Gemma 4 can't call toolsID dc-73 | Developer Communitiesgithub.com/continuedev/continue/issues/12131MidKnightXI, Continue user filing a GitHub issueself-described: LM Studio on a server, VS Code on a MacBookIndividual practitionerPublished Apr 13, 2026Assessment reviewed Nov 1, 2026Needs a recheck
How we made Trail of Bits AI-native (so far)ID ld-01 | Engineering Blogs & Reviewsblog.trailofbits.com/2026/03/31/how-we-made-trail-of-bits-ai-native-so-far/Dan Guido, CEO at Trail of Bits140-person security consultancy with a written AI usage policy for client codeTechnical leadershipPublished Mar 31, 2026Assessment reviewed Nov 1, 2026Current
Tried a few copilot alternatives after our security team blocked GitHub's data retentionID dc-72 | Developer Communitieswww.reddit.com/r/vscode/comments/1rm6x7k/tried_a_few_copilot_alternatives_after_our/Silly-Ad667, evaluating tools for a financial services teamself-described: Financial services company whose compliance team blocked CopilotVery small teamPublished Mar 6, 2026Assessment reviewed Nov 1, 2026Still applicable
Frustration replacing Github Copilot with local models (with Continue.dev)ID dc-71 | Developer Communitieswww.reddit.com/r/vscode/comments/1rgdpvb/frustration_replacing_github_copilot_with_local/Zed_Blade_CBS, r/vscode memberself-described: MacBook Pro M4 Max with 36 GB, LM Studio and Ollama, company bans DeepSeekIndividual practitionerPublished Feb 27, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: How AI assistance impacts the formation of coding skillsID dc-70 | Developer Communitiesnews.ycombinator.com/item?id=46826919Gallows4574, Hacker News commenterself-described: Local models on flightsIndividual practitionerPublished Jan 30, 2026Assessment reviewed Nov 1, 2026Still applicable
I Can't Get Ollama running through Continue to write complex codeID dc-69 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1qn552r/i_cant_get_ollama_running_through_continue_to/warpanomaly, r/LocalLLaMA memberself-described: Qwen3 Coder 30B on Ollama with an RTX 5090, VSCodiumIndividual practitionerPublished Jan 26, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: GLM-4.7-FlashID dc-68 | Developer Communitiesnews.ycombinator.com/item?id=46685149yowlingcat, Hacker News commenterself-described: Continue in VS Code, weighing Roo, Cline, and Kilo CodeIndividual practitionerPublished Jan 19, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: The future of software development is software developersID dc-67 | Developer Communitiesnews.ycombinator.com/item?id=46435975beeboop0, Hacker News commenterself-described: VS CodeIndividual practitionerPublished Dec 30, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: A guide to local coding modelsID dc-66 | Developer Communitiesnews.ycombinator.com/item?id=46352939KronisLV, Hacker News commenterself-described: Local and hosted modelsIndividual practitionerPublished Dec 22, 2025Assessment reviewed Nov 1, 2026Still applicable
How I replaced Gemini CLI & Copilot with a local stack using Ollama, Continue.dev and MCP serversID dc-65 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1p6nf1r/how_i_replaced_gemini_cli_copilot_with_a_local/aaronsky, r/LocalLLaMA memberself-described: Windows 11 laptop with 8 GB VRAM, Ollama models and MCP serversIndividual practitionerPublished Nov 25, 2025Assessment reviewed Nov 1, 2026Still applicable
Continue.dev CLI with no account, is it possible?ID dc-64 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1ospyy3/continuedev_cli_with_no_account_is_it_possible/fragglerock, r/LocalLLaMA memberself-described: VSCodium with a local llama installIndividual practitionerPublished Nov 9, 2025Assessment reviewed Nov 1, 2026Needs a recheck
IBM Developer - Setting up local co-pilot using Ollama with VS Code (or VSCodium for no telemetry air-gapped) with Continue extension.ID dc-63 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1ongwyo/ibm_developer_setting_up_local_copilot_using/finah1995, r/LocalLLaMA member who uses this setup at workself-described: Ollama with Continue in VS Code or VSCodium, Granite and Qwen Coder modelsIndividual practitionerPublished Nov 3, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopID dc-62 | Developer Communitiesnews.ycombinator.com/item?id=45781786Balinares, Hacker News commenterself-described: Qwen3 Coder in agent modeIndividual practitionerPublished Nov 1, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopID dc-56 | Developer Communitiesnews.ycombinator.com/item?id=45773267reactordev, Hacker News commenterself-described: MacBook Air M1 and an RTX 3080 laptopIndividual practitionerPublished Oct 31, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopID dc-57 | Developer Communitiesnews.ycombinator.com/item?id=45773720wongarsu, Hacker News commenter using an employer's GPU serverself-described: Employer GPU server running OllamaVery small teamPublished Oct 31, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopID dc-58 | Developer Communitiesnews.ycombinator.com/item?id=45773793dust42, Hacker News commenterself-described: MacBook Pro 64GB, travel and off-gridIndividual practitionerPublished Oct 31, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopID dc-59 | Developer Communitiesnews.ycombinator.com/item?id=45773970mjgs, Hacker News commenterself-described: MacBook Air M4, devcontainersIndividual practitionerPublished Oct 31, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopID dc-60 | Developer Communitiesnews.ycombinator.com/item?id=45776641platevoltage, Hacker News commenterself-described: M2 MacBook Pro, 16GBIndividual practitionerPublished Oct 31, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopID dc-61 | Developer Communitiesnews.ycombinator.com/item?id=45777371dennemark, Hacker News commenterself-described: Work laptop with AMD Strix HaloIndividual practitionerPublished Oct 31, 2025Assessment reviewed Nov 1, 2026Still applicable
Any simple alternatives to Continue.dev?ID dc-55 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1o8ieap/any_simple_alternatives_to_continuedev/HEAVYlight123, r/LocalLLaMA memberself-described: Local models in a chat panel with @ contextIndividual practitionerPublished Oct 16, 2025Assessment reviewed Nov 1, 2026Still applicable
[JetBrains] Sidebar panel frequently freezes across all OS'ID dc-54 | Developer Communitiesgithub.com/continuedev/continue/issues/8085bdavj, contributor reporting for a set of managed endpointsself-described: IntelliJ IDEA on a set of Mac and PC endpointsVery small teamPublished Oct 3, 2025Assessment reviewed Nov 1, 2026Needs a recheck
VS Code, Continue, Local LLMs on a Mac. What can I expect?ID dc-53 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1nh434j/vs_code_continue_local_llms_on_a_mac_what_can_i/Karl08534, r/LocalLLaMA memberself-described: Mac Studio M4 Max with 128 GB, gpt-oss 120B and Qwen3 Coder 30B on OllamaIndividual practitionerPublished Sep 14, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Experimenting with Local LLMs on macOSID dc-52 | Developer Communitiesnews.ycombinator.com/item?id=45173980kergonath, Hacker News commenterself-described: VSCodium on macOSIndividual practitionerPublished Sep 8, 2025Assessment reviewed Nov 1, 2026Still applicable
Continue.dev is buggy, but I still want an open source AI in my IDEID dc-51 | Developer Communitieswww.reddit.com/r/vscode/comments/1n8byjc/continuedev_is_such_a_buggy_piece_of_garbage_but/No_Flight_4473, r/vscode memberself-described: VS Code, alongside Aider for agent workIndividual practitionerPublished Sep 4, 2025Assessment reviewed Nov 1, 2026Still applicable
Der eigene, lokale KI-Coding-Assistent mit ContinueID ir-01 | Engineering Blogs & Reviewswww.viadee.de/en/blog/der-eigene-lokale-ki-coding-assistent-mit-continue/Christian Siebmanns, consultant and head of the Web and Mobile competence area at viadeeself-described: Local models with LM Studio; LiteLLM to scale across a companyTechnical leadershipPublished Aug 20, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Claudia - Desktop companion for Claude codeID dc-50 | Developer Communitiesnews.ycombinator.com/item?id=44936532omneity, Hacker News commenterself-described: M3 Max, local agent with RooIndividual practitionerPublished Aug 18, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Claudia - Desktop companion for Claude codeID dc-48 | Developer Communitiesnews.ycombinator.com/item?id=44935498unethical_ban, Hacker News commenterself-described: LM Studio, wants no accountsIndividual practitionerPublished Aug 17, 2025Assessment reviewed Nov 1, 2026Needs a recheck
Comment on: Claudia - Desktop companion for Claude codeID dc-49 | Developer Communitiesnews.ycombinator.com/item?id=44935857taneq, Hacker News commenterself-described: VSCodiumIndividual practitionerPublished Aug 17, 2025Assessment reviewed Nov 1, 2026Still applicable
continue.dev agent mode + ??agentID dc-47 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1mqcuy1/continuedev_agent_mode_agent/planetf1a, r/LocalLLaMA memberself-described: Local 8B to 14B models on a 32 GB M1 MacBookIndividual practitionerPublished Aug 14, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: With all the AI hype, how are software engineers feeling?ID dc-45 | Developer Communitiesnews.ycombinator.com/item?id=44861248englishrookie, Hacker News commenterself-described: VS CodeIndividual practitionerPublished Aug 11, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: The Claude party is almost overID dc-46 | Developer Communitiesnews.ycombinator.com/item?id=44864424ctbellmar, Hacker News commenterself-described: LM StudioIndividual practitionerPublished Aug 11, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: How I code with AI on a budget/freeID dc-42 | Developer Communitiesnews.ycombinator.com/item?id=44851655reactordev, Hacker News commenterself-described: Own modelsIndividual practitionerPublished Aug 10, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: How I code with AI on a budget/freeID dc-43 | Developer Communitiesnews.ycombinator.com/item?id=44852116navbaker, Hacker News commenterself-described: VS CodeIndividual practitionerPublished Aug 10, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: How I code with AI on a budget/freeID dc-44 | Developer Communitiesnews.ycombinator.com/item?id=44852254AstroBen, Hacker News commenterself-described: Own modelsIndividual practitionerPublished Aug 10, 2025Assessment reviewed Nov 1, 2026Still applicableListed, no finding position
Can't get continue.dev to index my codebaseID dc-41 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1mbxx64/cant_get_continuedev_to_index_my_codebase/SlimPerceptions, r/LocalLLaMA memberself-described: VS Code with Qwen2.5 CoderIndividual practitionerPublished Jul 29, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: How do you stay on top of AI tech?ID dc-40 | Developer Communitiesnews.ycombinator.com/item?id=44607375ActorNightly, Hacker News commenterself-described: VS CodeIndividual practitionerPublished Jul 18, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Add a configuration flag to hide the "Login to Continue Hub"-InfoID dc-39 | Developer Communitiesgithub.com/continuedev/continue/issues/6399#issuecomment-3041173000ron-zhong, who preconfigures Continue for users in an air-gapped networkself-described: Air-gapped environment with preconfigured Amazon Bedrock modelsVery small teamPublished Jul 6, 2025Assessment reviewed Nov 1, 2026Needs a recheck
Add a configuration flag to hide the "Login to Continue Hub"-InfoID dc-38 | Developer Communitiesgithub.com/continuedev/continue/issues/6399Hakenadu, who provisions Continue for a company's developersself-described: Company LLM gateway in the EU, developers given a pre-generated config.yamlVery small teamPublished Jul 2, 2025Assessment reviewed Nov 1, 2026Needs a recheck
Comment on: The new skill in AI is not prompting, it's context engineeringID dc-37 | Developer Communitiesnews.ycombinator.com/item?id=44428423colgandev, Hacker News commenterself-described: VS Code with speech to textIndividual practitionerPublished Jun 30, 2025Assessment reviewed Nov 1, 2026Still applicable
Cursor and Bolt free alternative in VSCodeID dc-36 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1lbxdwm/cursor_and_bolt_free_alternative_in_vscode/McMezoplayz, r/LocalLLaMA memberself-described: RTX 5060 Ti 16 GB with DeepSeek R1 8B on OllamaIndividual practitionerPublished Jun 15, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: What Does Your Self-Hosted LLM Stack Look Like in 2025?ID dc-35 | Developer Communitiesnews.ycombinator.com/item?id=44191436bluejay2387, Hacker News commenterself-described: Personal, 2x 3090 GPUsIndividual practitionerPublished Jun 5, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: Go deep into AI/LLMs or just use them as tools?ID dc-34 | Developer Communitiesnews.ycombinator.com/item?id=44079896manmal, Hacker News commenterself-described: iOS developmentIndividual practitionerPublished May 24, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Google Is Winning on Every AI FrontID dc-33 | Developer Communitiesnews.ycombinator.com/item?id=43662523wiradikusuma, Hacker News commenterself-described: IntelliJ pluginIndividual practitionerPublished Apr 12, 2025Assessment reviewed Nov 1, 2026Still applicable
Trusted self-signed certificate works for chatting but not for auto-completionID dc-30 | Developer Communitiesgithub.com/continuedev/continue/issues/5115jameslai-dev, for a company that self-hosts its modelsself-described: Company-hosted Ollama behind an HTTPS reverse proxy with a self-signed root certificateVery small teamPublished Apr 11, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Nvidia on NixOS WSL - Ollama up 24/7 on your gaming PCID dc-31 | Developer Communitiesnews.ycombinator.com/item?id=43652380itissid, Hacker News commenterself-described: Ollama on a TrueNAS Kubernetes hostIndividual practitionerPublished Apr 11, 2025Assessment reviewed Nov 1, 2026Still applicable
Ideal setup for local LLM Coding Assistant.ID dc-32 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1jwru49/ideal_setup_for_local_llm_coding_assistant/drplan, r/LocalLLaMA memberself-described: Ollama on a Mac Mini M4 Pro with 64 GB, no telemetryIndividual practitionerPublished Apr 11, 2025Assessment reviewed Nov 1, 2026Still applicable
Continue dev plugin: autocompletion is making VS-Code slowID dc-29 | Developer Communitiesgithub.com/continuedev/continue/issues/5055AIxHunter, Continue user filing a GitHub issueself-described: VS Code on LinuxIndividual practitionerPublished Apr 8, 2025Assessment reviewed Nov 1, 2026Needs a recheck
Comment on: GitHub Copilot Pro+ID dc-28 | Developer Communitiesnews.ycombinator.com/item?id=43597652o_m, Hacker News commenterself-described: Code completion onlyIndividual practitionerPublished Apr 5, 2025Assessment reviewed Nov 1, 2026Still applicable
Jetbrains freeze on autocompleteID dc-25 | Developer Communitiesgithub.com/continuedev/continue/issues/4845eslamo, Continue user filing a GitHub issueself-described: RustRover and other JetBrains IDEs on WindowsIndividual practitionerPublished Mar 27, 2025Assessment reviewed Nov 1, 2026Needs a recheck
Comment on: Launch HN: Continue (YC S23) - Create custom AI code assistantsID dc-26 | Developer Communitiesnews.ycombinator.com/item?id=43495921SlackingOff123, Hacker News commenterself-described: IntelliJ and VS CodeIndividual practitionerPublished Mar 27, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Launch HN: Continue (YC S23) - Create custom AI code assistantsID dc-27 | Developer Communitiesnews.ycombinator.com/item?id=43498738dimal, Hacker News commenterself-described: Switches between toolsIndividual practitionerPublished Mar 27, 2025Assessment reviewed Nov 1, 2026Still applicable
Help with local continue.dev autocompleteID dc-24 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1jfz31l/help_with_local_continuedev_autocomplete/LoungingLemur2, r/LocalLLaMA memberself-described: Local Ollama models through an Open WebUI APIIndividual practitionerPublished Mar 20, 2025Assessment reviewed Nov 1, 2026Still applicable
Local openai LLM assistant option removedID dc-23 | Developer Communitiesgithub.com/continuedev/continue/issues/4649surak, who runs Helmholtz Blablador and recommends Continue to its usersself-described: Helmholtz Blablador, an OpenAI-compatible model service for German academiaOrganization-widePublished Mar 14, 2025Assessment reviewed Nov 1, 2026Still applicable
Scrapping for local RAG?ID dc-22 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1jakwkz/scrapping_for_local_rag/the_renaissance_jack, r/LocalLLaMA memberself-described: Local projects with Open WebUIIndividual practitionerPublished Mar 13, 2025Assessment reviewed Nov 1, 2026Still applicable
Continue.Dev autocomplete too wastefull, going back to CopilotID dc-21 | Developer Communitieswww.reddit.com/r/ChatGPTCoding/comments/1izkilg/continuedev_autocomplete_too_wastefull_going_back/VirtualPanic6798, r/ChatGPTCoding memberself-described: Part-time coding in VS Code, Codestral through OpenRouterIndividual practitionerPublished Feb 27, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Microsoft cancels leases for AI data centers, analyst saysID dc-20 | Developer Communitiesnews.ycombinator.com/item?id=43158666geuis, Hacker News commenterself-described: Hosted and local modelsIndividual practitionerPublished Feb 24, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Show HN: Cline - Open-Source VS Code AI Coding Agent with a New MCP MarketplaceID dc-19 | Developer Communitiesnews.ycombinator.com/item?id=43116346remuskaos, Hacker News commenterself-described: Long-time Continue user, compared with ClineIndividual practitionerPublished Feb 20, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: New junior developers can't codeID dc-18 | Developer Communitiesnews.ycombinator.com/item?id=43083891dabockster, Hacker News commenterself-described: Offline, on-deviceIndividual practitionerPublished Feb 17, 2025Assessment reviewed Nov 1, 2026Still applicable
Why does Zed's new LLM work great on their IDE and terrible with VS Code's ContinueID dc-17 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1iqykw5/why_does_zeds_new_llm_work_great_on_their_ide_and/1Blue3Brown, r/LocalLLaMA memberself-described: Zed's open Zeta model in LM Studio, compared in Zed and in VS CodeIndividual practitionerPublished Feb 16, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Zed now predicts your next edit with Zeta, our new open modelID dc-16 | Developer Communitiesnews.ycombinator.com/item?id=43046627coder543, Hacker News commenterself-described: codegemma-2b as the completion model, compared with CursorIndividual practitionerPublished Feb 14, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: JetBrains Fleet drops support for Kotlin MultiplatformID dc-14 | Developer Communitiesnews.ycombinator.com/item?id=43021144vunderba, Hacker News commenterself-described: JetBrains IDEsIndividual practitionerPublished Feb 12, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: JetBrains Fleet drops support for Kotlin MultiplatformID dc-15 | Developer Communitiesnews.ycombinator.com/item?id=43025433KronisLV, Hacker News commenterself-described: JetBrains IDEs, Ollama on a serverIndividual practitionerPublished Feb 12, 2025Assessment reviewed Nov 1, 2026Still applicable
Continue freezes IDEID dc-13 | Developer Communitiesgithub.com/continuedev/continue/issues/4098cobrafast, Continue user filing a GitHub issueself-described: JetBrains Rider on WindowsIndividual practitionerPublished Feb 11, 2025Assessment reviewed Nov 1, 2026Needs a recheck
Comment on: Building Personal Software with ClaudeID dc-12 | Developer Communitiesnews.ycombinator.com/item?id=43003657ottah, Hacker News commenter whose company uses Continue internallyself-described: Company use in IntelliJ IDEs; at home with OpenRouter and local serversVery small teamPublished Feb 10, 2025Assessment reviewed Nov 1, 2026Still applicable
Local auto-complete for coding?ID dc-11 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1ihnvjk/local_autocomplete_for_coding/ChangeIsHard_, r/LocalLLaMA memberself-described: Local models on two RTX 4090s in VS CodeIndividual practitionerPublished Feb 4, 2025Assessment reviewed Nov 1, 2026Still applicable
My Experience Evaluating Coding Assistants for JetBrains IntegrationID dc-10 | Developer Communitieswww.reddit.com/r/ChatGPTCoding/comments/1ifujrk/my_experience_evaluating_coding_assistants_for/sebastian-loncar, r/ChatGPTCoding memberself-described: JetBrains IDEs, two days comparing assistantsIndividual practitionerPublished Feb 2, 2025Assessment reviewed Nov 1, 2026Still applicable
Replacing github copilot with continue.dev issuesID dc-09 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1iegp48/replacing_github_copilot_with_continuedev_issues/MainManu, r/LocalLLaMA memberself-described: Self-hosted Ollama models in VS Code, replacing CopilotIndividual practitionerPublished Jan 31, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Promising results from DeepSeek R1 for codeID dc-08 | Developer Communitiesnews.ycombinator.com/item?id=42857428codingdave, Hacker News commenterself-described: VS Code, chat onlyIndividual practitionerPublished Jan 28, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: Open-Source editor with local code completion?ID dc-07 | Developer Communitiesnews.ycombinator.com/item?id=42833810atmanactive, Hacker News commenterself-described: VSCodiumIndividual practitionerPublished Jan 26, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Llama.vim - Local LLM-assisted text completionID dc-06 | Developer Communitiesnews.ycombinator.com/item?id=42812223eklavya, Hacker News commenterself-described: VS CodeIndividual practitionerPublished Jan 24, 2025Assessment reviewed Nov 1, 2026Still applicable
Quick tutorial: How to run Cursor at home (R1-14b + Continue.dev)ID dc-05 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1i6g7zd/quick_tutorial_how_to_run_cursor_at_home_r114b/mark-lord, r/LocalLLaMA memberself-described: DeepSeek R1 14B as an MLX model on a MacIndividual practitionerPublished Jan 21, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Find and execute shell commands using OllamaID dc-04 | Developer Communitiesnews.ycombinator.com/item?id=42764045codingdave, Hacker News commenterself-described: VS CodeIndividual practitionerPublished Jan 20, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: A three month review of kagi search and the orion web browser (2024)ID dc-03 | Developer Communitiesnews.ycombinator.com/item?id=42652929SV_BubbleTime, Hacker News commenterself-described: VS Code, Claude APIIndividual practitionerPublished Jan 10, 2025Assessment reviewed Nov 1, 2026Still applicable
Any joy with continue.dev?ID dc-02 | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1hvnhdt/any_joy_with_continuedev/theboldestgaze, r/LocalLLaMA memberself-described: Continue on local modelsIndividual practitionerPublished Jan 7, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Things we learned about LLMs in 2024ID dc-01 | Developer Communitiesnews.ycombinator.com/item?id=42564045Sn0wCoder, Hacker News commenterself-described: IntelliJ, with a box running local modelsIndividual practitionerPublished Jan 1, 2025Assessment reviewed Nov 1, 2026Still applicable
Continue (acquired by Cursor)ID pd-01 | Product Documentationcontinue.dev/Continue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
continuedev/continue on GitHubID pd-02 | Product Documentationgithub.com/continuedev/continueContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
Continue releases on GitHubID pd-03 | Product Documentationgithub.com/continuedev/continue/releasesContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
Continue on the Visual Studio MarketplaceID pd-04 | Product Documentationmarketplace.visualstudio.com/items?itemName=Continue.continueContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
Continue on Open VSXID pd-05 | Product Documentationopen-vsx.org/extension/Continue/continueContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
Continue on JetBrains MarketplaceID pd-06 | Product Documentationplugins.jetbrains.com/plugin/22707-continueContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
Model providers overviewID pd-07 | Product Documentationdocs.continue.dev/customize/model-providers/overviewContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
config.yaml referenceID pd-08 | Product Documentationdocs.continue.dev/referenceContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
Autocomplete setupID pd-09 | Product Documentationdocs.continue.dev/customize/deep-dives/autocompleteContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
How Agent mode worksID pd-10 | Product Documentationdocs.continue.dev/ide-extensions/agent/how-it-worksContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
CLI tool permissionsID pd-11 | Product Documentationdocs.continue.dev/cli/tool-permissionsContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
CLI headless modeID pd-12 | Product Documentationdocs.continue.dev/cli/headless-modeContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
RulesID pd-13 | Product Documentationdocs.continue.dev/customize/deep-dives/rulesContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
MCPID pd-14 | Product Documentationdocs.continue.dev/customize/deep-dives/mcpContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
Development dataID pd-15 | Product Documentationdocs.continue.dev/customize/deep-dives/development-dataContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
Running Continue without internetID pd-16 | Product Documentationdocs.continue.dev/guides/running-continue-without-internetContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only
FAQsID pd-17 | Product Documentationdocs.continue.dev/faqsContinue Dev, Inc.Official product documentation and listingsNot counted (documentation)No date statedDocumentation checked Oct 12, 2026CurrentVerification only