Skip to main content

AI Coding Agent

Continue

Open-source coding assistant and agent for VS Code, JetBrains IDEs, and the terminal, with chat, edits, tab autocomplete, and Agent mode on the model provider or local models you configure. Cursor acquired Continue in June 2026; the hosted service closed and the Apache 2.0 repository is read-only.

The 30-Second Take

Keep Continue only as a bridge, because Cursor acquired it in June 2026 and left the repository read-only.

Its hosted service closed with the acquisition. The final release still runs in VS Code, JetBrains IDEs and the terminal with no Continue account.

Best fit
Teams already on Continue, running local or company-hosted models while they plan a move.
Main constraint
Fixes and new model support stop at the final 2.0.0 release and its 2.1.0 pre-release build.
First move
Pin the final release on every machine and set a date to choose a maintained successor.

Why

Watch who fixes it: every fix and every new model is now your team's job. That is worth it only if code must stay on models you pick or host locally.

Practitioner sentiment, all practitioners−9 Mixed

66 practitioners, 112 sources reviewed, Updated Nov 1, 2026How this is measured

Read the GILD Review
Save a product your organization uses.Keep up with Continue without adding it to your stack.Visit Website
Operating stack
Agentic Software Development

Comparisons

How does Continue compare with the alternatives?

  1. Continue vs Cline

    • AI Coding Agents

    Pick Cline to stay open source on your own models with releases that still ship, and Enterprise SSO when you need it. Keep Continue's frozen final release only while you pilot the move.

  2. Continue vs GitHub Copilot

    • AI Developer Assistant

    Pick GitHub Copilot for a maintained subscription with admin policy, included AI credits and local bring-your-own-key. Keep Continue only where models must stay local, and only while you plan the move.

  3. Continue vs Cursor

    • AI Developer Assistant

    Pick Cursor if engineers will switch to its maintained editor with included model usage. Keep Continue's final release only while you move, mainly where completion must run on local models, which Cursor's Tab does not support.

Operator Insights

What are engineering leaders learning from deploying Continue?

Buying and deployment

What engineering leaders should verify before a broader rollout.

Sourced from Continue documentation

How you buy it

Free, Apache 2.0

Paid plans ended with the Cursor acquisition, and unused credits are refunded.

Source 1, Continue Dev, Inc., Continue (acquired by Cursor): Continue (acquired by Cursor)Source 5, continue.dev, continue.dev FAQ (site script): continue.dev FAQ (site script)Source 2, Continue Dev, Inc., Continue on GitHub: Continue on GitHub

Details

You no longer buy it. Paid plans ended when Cursor acquired Continue: recurring billing is disabled and unused paid credits are refunded. The extension, plugin, and CLI stay free under Apache 2.0.

Cost drivers

Model usage only

You pay your provider or run local models. Continue charges nothing and has no seats.

Source 3, Continue Dev, Inc., Continue on the Visual Studio Marketplace: Continue on the Visual Studio MarketplaceSource 4, Continue Dev, Inc., config.yaml reference: config.yaml reference

Details

Model usage only. You pay your own provider for cloud models or run local models on your own hardware; Continue charges nothing and has no seats.

Where it runs

VS Code, JetBrains, CLI

Extension 2.0.0, plugin 1.0.67, and the cn CLI, configured from one local file.

Source 6, Continue Dev, Inc., Continue releases on GitHub: Continue releases on GitHubSource 7, open-vsx.org, Open VSX API: Continue: Open VSX API: ContinueSource 3, Continue Dev, Inc., Continue on the Visual Studio Marketplace: Continue on the Visual Studio MarketplaceSource 8, registry.npmjs.org, npm registry: @continuedev/cli: npm registry: @continuedev/cliSource 4, Continue Dev, Inc., config.yaml reference: config.yaml reference

Details

VS Code extension 2.0.0 on the Marketplace and Open VSX, with a 2.1.0 pre-release build the same day (June 19, 2026), JetBrains plugin 1.0.67 (March 27, 2026), and the cn CLI 1.5.47, each reading config.yaml on the engineer's machine.

What to verify

No maintainer

The repository is read-only and unmaintained, with no admin console, SSO, or central policy.

Source 2, Continue Dev, Inc., Continue on GitHub: Continue on GitHubSource 9, GitHub, SECURITY.md: SECURITY.mdSource 10, api.github.com, Pull request #12570: final release cleanup (GitHub API): Pull request #12570: final release cleanup (GitHub API)

Details

The repository is read-only and no longer actively maintained, so plan on no further releases, security fixes included, although SECURITY.md still lists security@continue.dev. The final release removed sign-in, so there is no admin console, SSO, or central policy; governance rests on shared files and your own endpoint management.

Signals

What is the current evidence saying about Continue?

What developers and teams report publicly about Continue, from January 2025 through the months after Cursor acquired it, with every finding linked to its sources.

Whose sources count

Practitioner sentiment, all practitioners

−9 Mixed net

of 69 sources that take a side, each author counted once.

How this figure is made

25 more state no overall view and cast no vote.

Leaders and teams have 6 accounts; GILD prints their sentiment from 20.

Current sentiment

Positive, mixed and negative sources

The score counts them as 17 positive, 26 mixed and 23 negative votes, one per author.

Local models and per-role model choice draw the most praise. Reliability is the concern raised most often, and autocomplete draws the most criticism, with 11 of the 15 that discuss it critical. Since June 2026 the newest sources turn to the end of maintenance and to the JetBrains plugin failing on 2026.2 IDEs.

Use a task pilot to measure accepted work and review time.

Evidence field. All 112 sources, one mark each.

Arrange by

Each mark is one source: positive, mixed, negative, no opinion stated, or documentation (not counted).

By sentiment, All practitioners. Every source GILD read, grouped as the field draws it.
GroupSourcesPositiveMixedNegativeNo opinion stated and not counted in the scoreDocumentation, checked and not counted
Positive18180000
Mixed28028000
Negative23002300
Not counted26000260
Documentation17000017
Every source GILD read, by the quarter it was published, as the field's time axis counts it. Documentation is dated by the day it was checked.
QuarterSources
Q1 202527
Q2 202510
Q3 202517
Q4 202514
Q1 20266
Q2 202612
Q3 20269
Q4 20260
Documentation, checked17

By sentiment

17 documentation pages check facts and are not counted.

Hover a mark for a quick look, click it or press Enter to open its source.Tap a mark to open its source, then step to its neighbors with Previous and Next.

What practitioners praise

Top praise of 5. Each mark is a source on it; filled marks praise it.

  1. Local and Self-Hosted Models28 of 31 sources on it praise it

Most common concerns

Top concern of 5. Each mark is a source on it; filled marks raise it.

  1. Reliability and Update RegressionsAll 18 sources on it raise it as a concern
All 112 sources behind these findings
  1. Continue (acquired by Cursor)Continue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  2. continuedev/continue on GitHubContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  3. Continue releases on GitHubContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  4. Continue on the Visual Studio MarketplaceContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  5. Continue on Open VSXContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  6. Continue on JetBrains MarketplaceContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  7. Model providers overviewContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  8. config.yaml referenceContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  9. Autocomplete setupContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  10. How Agent mode worksContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  11. CLI tool permissionsContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  12. CLI headless modeContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  13. RulesContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  14. MCPContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  15. Development dataContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  16. Running Continue without internetContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  17. FAQsContinue Dev, Inc. (Official product documentation and listings), Product documentation, checked Oct 12, 2026
  18. Continue 2.0.0 issue: Agent mode file tools fail with a local modeljwickster, Agent mode user (self-described: VS Code Agent mode on a local model through LM Studio, filesystem MCP enabled), GitHub issue, published Sep 28, 2026
  19. JetBrains plugin fails to load in 2026.2 IDEs with NoClassDefFoundError: com/intellij/ui/jcef/JBCefAppecampidoglio, JetBrains Rider user (self-described: Rider 2026.2 on macOS), GitHub issue, published Aug 24, 2026
  20. Continue was bought by Cursor. What do I do now?pilkyton, r/LocalLLaMA member (self-described: VS Code with a Gemini API key and workspace context), Reddit post, published Aug 23, 2026
  21. Continue coding agent is dead. Alternatives?roscas, Hacker News commenter (self-described: VS Code with offline Ollama), Hacker News post, published Aug 22, 2026
  22. I got fed up with locked-down autocomplete, so I forked Continue and stripped it down to just tab-completionphantagom, r/LocalLLaMA member (self-described: Daily tab completion in VS Code on a model of their choice), Reddit post, published Aug 21, 2026
  23. Comment on: IntelliJ IDEA 2026.2.1 : Continue crashesBenj2005, JetBrains plugin user (self-described: IntelliJ IDEA 2026.2), GitHub issue comment, published Aug 15, 2026
  24. Prepare dev-env for ARENAIgnacio Heredia, researcher on the AI4EOSC platform at IFCA (EU research AI platform that offers its own hosted models as a code assistant in VS Code), GitHub issue, ai4os/ai4os-dev-env, published Aug 7, 2026
  25. Comment on: Open-weight AI is having its Kubernetes momentovergard, Hacker News commenter (self-described: MacBook, local Qwen 3.6 27B), Hacker News comment, published Jul 25, 2026
  26. Comment on: Ask HN: Is anyone experimenting with different ways of using LLMs for coding?kpatucha, Hacker News commenter (self-described: Data and ML work, trying tab completion), Hacker News comment, published Jul 6, 2026
  27. Comment on: Computer use in Gemini 3.5 Flashanigbrowl, Hacker News commenter (self-described: IDE with a paid Gemini API key), Hacker News comment, published Jun 25, 2026
  28. Comment on: Suggestion to make a proper forkprimadg, for a team at Cedra (self-described: Cedra, planning its own fork), GitHub issue comment, published Jun 23, 2026
  29. Continue CLI does not work with external OpenAI-compatible model (Error: 400 status code (no body))liar666, running a coding agent on a self-hosted model server (self-described: cn CLI on Linux Mint and OpenBSD with a self-hosted OpenAI-compatible model), GitHub issue, published Jun 22, 2026
  30. Impact of Cursor's Acquisition of Continue on existing customized traceability from session.json and autocomplete.jsonl files?sridattasp, for a team that built tooling on Continue's data files (self-described: Team traceability solution built on session.json and autocomplete.jsonl), GitHub issue, published Jun 22, 2026
  31. Suggestion to make a proper forkTobiasFP, Continue user (self-described: Filed after the acquisition, once the repository's discussions had closed), GitHub issue, published Jun 18, 2026
  32. Comment on: Continue has been acquired by Cursorguy4261, Hacker News commenter (self-described: Had projects and leftover credits on Continue), Hacker News comment, published Jun 18, 2026
  33. Comment on: Ask HN: Has anyone replaced Claude/GPT with a local model for daily coding?calenti, Hacker News commenter (self-described: Local models), Hacker News comment, published Jun 17, 2026
  34. Comment on: Continue has been acquired by CursorGaryBluto, Hacker News commenter (self-described: VS Code), Hacker News comment, published Jun 16, 2026
  35. If you use continue.dev and Qwen 3.6 (dense / MoE) - I could use your helpJorlen, r/LocalLLaMA member (self-described: Qwen 3.6 on llama.cpp, moving from Roo Code), Reddit post, published May 18, 2026
  36. Comment on: Running local models on an M4 with 24GB memoryy42, Hacker News commenter (self-described: M3 with 36GB), Hacker News comment, published May 11, 2026
  37. Comment on: Qwen3.6-35B-A3B: Agentic coding power, now open to alldataflow, Hacker News commenter (self-described: Newcomer to local models), Hacker News comment, published Apr 16, 2026
  38. Qwen 3.5 and Gemma 4 can't call toolsMidKnightXI, Continue user filing a GitHub issue (self-described: LM Studio on a server, VS Code on a MacBook), GitHub issue, published Apr 13, 2026
  39. How we made Trail of Bits AI-native (so far)Dan Guido, CEO at Trail of Bits (140-person security consultancy with a written AI usage policy for client code), Company blog post, Trail of Bits Blog, published Mar 31, 2026
  40. Tried a few copilot alternatives after our security team blocked GitHub's data retentionSilly-Ad667, evaluating tools for a financial services team (self-described: Financial services company whose compliance team blocked Copilot), Reddit post, published Mar 6, 2026
  41. Frustration replacing Github Copilot with local models (with Continue.dev)Zed_Blade_CBS, r/vscode member (self-described: MacBook Pro M4 Max with 36 GB, LM Studio and Ollama, company bans DeepSeek), Reddit post, published Feb 27, 2026
  42. Comment on: How AI assistance impacts the formation of coding skillsGallows4574, Hacker News commenter (self-described: Local models on flights), Hacker News comment, published Jan 30, 2026
  43. I Can't Get Ollama running through Continue to write complex codewarpanomaly, r/LocalLLaMA member (self-described: Qwen3 Coder 30B on Ollama with an RTX 5090, VSCodium), Reddit post, published Jan 26, 2026
  44. Comment on: GLM-4.7-Flashyowlingcat, Hacker News commenter (self-described: Continue in VS Code, weighing Roo, Cline, and Kilo Code), Hacker News comment, published Jan 19, 2026
  45. Comment on: The future of software development is software developersbeeboop0, Hacker News commenter (self-described: VS Code), Hacker News comment, published Dec 30, 2025
  46. Comment on: A guide to local coding modelsKronisLV, Hacker News commenter (self-described: Local and hosted models), Hacker News comment, published Dec 22, 2025
  47. How I replaced Gemini CLI & Copilot with a local stack using Ollama, Continue.dev and MCP serversaaronsky, r/LocalLLaMA member (self-described: Windows 11 laptop with 8 GB VRAM, Ollama models and MCP servers), Reddit post, published Nov 25, 2025
  48. Continue.dev CLI with no account, is it possible?fragglerock, r/LocalLLaMA member (self-described: VSCodium with a local llama install), Reddit post, published Nov 9, 2025
  49. IBM Developer - Setting up local co-pilot using Ollama with VS Code (or VSCodium for no telemetry air-gapped) with Continue extension.finah1995, r/LocalLLaMA member who uses this setup at work (self-described: Ollama with Continue in VS Code or VSCodium, Granite and Qwen Coder models), Reddit post, published Nov 3, 2025
  50. Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopBalinares, Hacker News commenter (self-described: Qwen3 Coder in agent mode), Hacker News comment, published Nov 1, 2025
  51. Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopreactordev, Hacker News commenter (self-described: MacBook Air M1 and an RTX 3080 laptop), Hacker News comment, published Oct 31, 2025
  52. Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopwongarsu, Hacker News commenter using an employer's GPU server (self-described: Employer GPU server running Ollama), Hacker News comment, published Oct 31, 2025
  53. Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopdust42, Hacker News commenter (self-described: MacBook Pro 64GB, travel and off-grid), Hacker News comment, published Oct 31, 2025
  54. Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopmjgs, Hacker News commenter (self-described: MacBook Air M4, devcontainers), Hacker News comment, published Oct 31, 2025
  55. Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopplatevoltage, Hacker News commenter (self-described: M2 MacBook Pro, 16GB), Hacker News comment, published Oct 31, 2025
  56. Comment on: Ask HN: Who uses open LLMs and coding assistants locally? Share setup and laptopdennemark, Hacker News commenter (self-described: Work laptop with AMD Strix Halo), Hacker News comment, published Oct 31, 2025
  57. Any simple alternatives to Continue.dev?HEAVYlight123, r/LocalLLaMA member (self-described: Local models in a chat panel with @ context), Reddit post, published Oct 16, 2025
  58. [JetBrains] Sidebar panel frequently freezes across all OS'bdavj, contributor reporting for a set of managed endpoints (self-described: IntelliJ IDEA on a set of Mac and PC endpoints), GitHub issue, published Oct 3, 2025
  59. VS Code, Continue, Local LLMs on a Mac. What can I expect?Karl08534, r/LocalLLaMA member (self-described: Mac Studio M4 Max with 128 GB, gpt-oss 120B and Qwen3 Coder 30B on Ollama), Reddit post, published Sep 14, 2025
  60. Comment on: Experimenting with Local LLMs on macOSkergonath, Hacker News commenter (self-described: VSCodium on macOS), Hacker News comment, published Sep 8, 2025
  61. Continue.dev is buggy, but I still want an open source AI in my IDENo_Flight_4473, r/vscode member (self-described: VS Code, alongside Aider for agent work), Reddit post, published Sep 4, 2025
  62. Der eigene, lokale KI-Coding-Assistent mit ContinueChristian Siebmanns, consultant and head of the Web and Mobile competence area at viadee (self-described: Local models with LM Studio; LiteLLM to scale across a company), Company blog post, viadee blog, published Aug 20, 2025
  63. Comment on: Claudia - Desktop companion for Claude codeomneity, Hacker News commenter (self-described: M3 Max, local agent with Roo), Hacker News comment, published Aug 18, 2025
  64. Comment on: Claudia - Desktop companion for Claude codeunethical_ban, Hacker News commenter (self-described: LM Studio, wants no accounts), Hacker News comment, published Aug 17, 2025
  65. Comment on: Claudia - Desktop companion for Claude codetaneq, Hacker News commenter (self-described: VSCodium), Hacker News comment, published Aug 17, 2025
  66. continue.dev agent mode + ??agentplanetf1a, r/LocalLLaMA member (self-described: Local 8B to 14B models on a 32 GB M1 MacBook), Reddit post, published Aug 14, 2025
  67. Comment on: Ask HN: With all the AI hype, how are software engineers feeling?englishrookie, Hacker News commenter (self-described: VS Code), Hacker News comment, published Aug 11, 2025
  68. Comment on: The Claude party is almost overctbellmar, Hacker News commenter (self-described: LM Studio), Hacker News comment, published Aug 11, 2025
  69. Comment on: How I code with AI on a budget/freereactordev, Hacker News commenter (self-described: Own models), Hacker News comment, published Aug 10, 2025
  70. Comment on: How I code with AI on a budget/freenavbaker, Hacker News commenter (self-described: VS Code), Hacker News comment, published Aug 10, 2025
  71. Comment on: How I code with AI on a budget/freeAstroBen, Hacker News commenter (self-described: Own models), Hacker News comment, published Aug 10, 2025
  72. Can't get continue.dev to index my codebaseSlimPerceptions, r/LocalLLaMA member (self-described: VS Code with Qwen2.5 Coder), Reddit post, published Jul 29, 2025
  73. Comment on: Ask HN: How do you stay on top of AI tech?ActorNightly, Hacker News commenter (self-described: VS Code), Hacker News comment, published Jul 18, 2025
  74. Comment on: Add a configuration flag to hide the "Login to Continue Hub"-Inforon-zhong, who preconfigures Continue for users in an air-gapped network (self-described: Air-gapped environment with preconfigured Amazon Bedrock models), GitHub issue comment, published Jul 6, 2025
  75. Add a configuration flag to hide the "Login to Continue Hub"-InfoHakenadu, who provisions Continue for a company's developers (self-described: Company LLM gateway in the EU, developers given a pre-generated config.yaml), GitHub issue, published Jul 2, 2025
  76. Comment on: The new skill in AI is not prompting, it's context engineeringcolgandev, Hacker News commenter (self-described: VS Code with speech to text), Hacker News comment, published Jun 30, 2025
  77. Cursor and Bolt free alternative in VSCodeMcMezoplayz, r/LocalLLaMA member (self-described: RTX 5060 Ti 16 GB with DeepSeek R1 8B on Ollama), Reddit post, published Jun 15, 2025
  78. Comment on: Ask HN: What Does Your Self-Hosted LLM Stack Look Like in 2025?bluejay2387, Hacker News commenter (self-described: Personal, 2x 3090 GPUs), Hacker News comment, published Jun 5, 2025
  79. Comment on: Ask HN: Go deep into AI/LLMs or just use them as tools?manmal, Hacker News commenter (self-described: iOS development), Hacker News comment, published May 24, 2025
  80. Comment on: Google Is Winning on Every AI Frontwiradikusuma, Hacker News commenter (self-described: IntelliJ plugin), Hacker News comment, published Apr 12, 2025
  81. Trusted self-signed certificate works for chatting but not for auto-completionjameslai-dev, for a company that self-hosts its models (self-described: Company-hosted Ollama behind an HTTPS reverse proxy with a self-signed root certificate), GitHub issue, published Apr 11, 2025
  82. Comment on: Nvidia on NixOS WSL - Ollama up 24/7 on your gaming PCitissid, Hacker News commenter (self-described: Ollama on a TrueNAS Kubernetes host), Hacker News comment, published Apr 11, 2025
  83. Ideal setup for local LLM Coding Assistant.drplan, r/LocalLLaMA member (self-described: Ollama on a Mac Mini M4 Pro with 64 GB, no telemetry), Reddit post, published Apr 11, 2025
  84. Continue dev plugin: autocompletion is making VS-Code slowAIxHunter, Continue user filing a GitHub issue (self-described: VS Code on Linux), GitHub issue, published Apr 8, 2025
  85. Comment on: GitHub Copilot Pro+o_m, Hacker News commenter (self-described: Code completion only), Hacker News comment, published Apr 5, 2025
  86. Jetbrains freeze on autocompleteeslamo, Continue user filing a GitHub issue (self-described: RustRover and other JetBrains IDEs on Windows), GitHub issue, published Mar 27, 2025
  87. Comment on: Launch HN: Continue (YC S23) - Create custom AI code assistantsSlackingOff123, Hacker News commenter (self-described: IntelliJ and VS Code), Hacker News comment, published Mar 27, 2025
  88. Comment on: Launch HN: Continue (YC S23) - Create custom AI code assistantsdimal, Hacker News commenter (self-described: Switches between tools), Hacker News comment, published Mar 27, 2025
  89. Help with local continue.dev autocompleteLoungingLemur2, r/LocalLLaMA member (self-described: Local Ollama models through an Open WebUI API), Reddit post, published Mar 20, 2025
  90. Local openai LLM assistant option removedsurak, who runs Helmholtz Blablador and recommends Continue to its users (self-described: Helmholtz Blablador, an OpenAI-compatible model service for German academia), GitHub issue, published Mar 14, 2025
  91. Scrapping for local RAG?the_renaissance_jack, r/LocalLLaMA member (self-described: Local projects with Open WebUI), Reddit post, published Mar 13, 2025
  92. Continue.Dev autocomplete too wastefull, going back to CopilotVirtualPanic6798, r/ChatGPTCoding member (self-described: Part-time coding in VS Code, Codestral through OpenRouter), Reddit post, published Feb 27, 2025
  93. Comment on: Microsoft cancels leases for AI data centers, analyst saysgeuis, Hacker News commenter (self-described: Hosted and local models), Hacker News comment, published Feb 24, 2025
  94. Comment on: Show HN: Cline - Open-Source VS Code AI Coding Agent with a New MCP Marketplaceremuskaos, Hacker News commenter (self-described: Long-time Continue user, compared with Cline), Hacker News comment, published Feb 20, 2025
  95. Comment on: New junior developers can't codedabockster, Hacker News commenter (self-described: Offline, on-device), Hacker News comment, published Feb 17, 2025
  96. Why does Zed's new LLM work great on their IDE and terrible with VS Code's Continue1Blue3Brown, r/LocalLLaMA member (self-described: Zed's open Zeta model in LM Studio, compared in Zed and in VS Code), Reddit post, published Feb 16, 2025
  97. Comment on: Zed now predicts your next edit with Zeta, our new open modelcoder543, Hacker News commenter (self-described: codegemma-2b as the completion model, compared with Cursor), Hacker News comment, published Feb 14, 2025
  98. Comment on: JetBrains Fleet drops support for Kotlin Multiplatformvunderba, Hacker News commenter (self-described: JetBrains IDEs), Hacker News comment, published Feb 12, 2025
  99. Comment on: JetBrains Fleet drops support for Kotlin MultiplatformKronisLV, Hacker News commenter (self-described: JetBrains IDEs, Ollama on a server), Hacker News comment, published Feb 12, 2025
  100. Continue freezes IDEcobrafast, Continue user filing a GitHub issue (self-described: JetBrains Rider on Windows), GitHub issue, published Feb 11, 2025
  101. Comment on: Building Personal Software with Claudeottah, Hacker News commenter whose company uses Continue internally (self-described: Company use in IntelliJ IDEs; at home with OpenRouter and local servers), Hacker News comment, published Feb 10, 2025
  102. Local auto-complete for coding?ChangeIsHard_, r/LocalLLaMA member (self-described: Local models on two RTX 4090s in VS Code), Reddit post, published Feb 4, 2025
  103. My Experience Evaluating Coding Assistants for JetBrains Integrationsebastian-loncar, r/ChatGPTCoding member (self-described: JetBrains IDEs, two days comparing assistants), Reddit post, published Feb 2, 2025
  104. Replacing github copilot with continue.dev issuesMainManu, r/LocalLLaMA member (self-described: Self-hosted Ollama models in VS Code, replacing Copilot), Reddit post, published Jan 31, 2025
  105. Comment on: Promising results from DeepSeek R1 for codecodingdave, Hacker News commenter (self-described: VS Code, chat only), Hacker News comment, published Jan 28, 2025
  106. Comment on: Ask HN: Open-Source editor with local code completion?atmanactive, Hacker News commenter (self-described: VSCodium), Hacker News comment, published Jan 26, 2025
  107. Comment on: Llama.vim - Local LLM-assisted text completioneklavya, Hacker News commenter (self-described: VS Code), Hacker News comment, published Jan 24, 2025
  108. Quick tutorial: How to run Cursor at home (R1-14b + Continue.dev)mark-lord, r/LocalLLaMA member (self-described: DeepSeek R1 14B as an MLX model on a Mac), Reddit post, published Jan 21, 2025
  109. Comment on: Find and execute shell commands using Ollamacodingdave, Hacker News commenter (self-described: VS Code), Hacker News comment, published Jan 20, 2025
  110. Comment on: A three month review of kagi search and the orion web browser (2024)SV_BubbleTime, Hacker News commenter (self-described: VS Code, Claude API), Hacker News comment, published Jan 10, 2025
  111. Any joy with continue.dev?theboldestgaze, r/LocalLLaMA member (self-described: Continue on local models), Reddit post, published Jan 7, 2025
  112. Comment on: Things we learned about LLMs in 2024Sn0wCoder, Hacker News commenter (self-described: IntelliJ, with a box running local models), Hacker News comment, published Jan 1, 2025

Jan 2025 to Sep 2026.

95 sources from practitioners, by month and sentiment.

The full readExplore all Continue Signals5 praise themes, 5 concerns, 2 points of agreement and 3 disagreements across all three groups, with all 112 sources open to inspect.

Where It Fits

Where does Continue belong in the stack?

Open Where It Fits: the Stack Field and the full map

Continue is Core across Build, supports Validate, and touches Plan, Ship, and Operate.

Business area
Product & Engineering
Function
Software Development
Operating stack
Agentic Software Development
Primary role
Open-Source IDE Assistant on Your Own Models
Continue beside the rest of its stackThe Stack Field, every product on every layer
FootprintContinue across the Agentic Software Development stack. Bar height is its role on each layer.

  1. Plan

    1. Work planning: Touches

      Work planning, touches. Plan mode explores the codebase with read-only tools before Agent mode edits, but Continue is not where a team plans or tracks work.

  2. Build

    1. Codebase context: Supports

      Codebase context, supports. Agent mode reads the repository through file search, grep, a repo map, and a local codebase index, and Continue can index documentation sites, while repository-wide code intelligence stays with a dedicated product.

    2. Coding: Core

      Coding, core. This is Continue's primary role: chat, inline edits, tab autocomplete, and Agent mode write and change code inside VS Code and JetBrains IDEs.

    3. Agent runtime: Core

      Agent runtime, core. The VS Code extension, the JetBrains plugin, and the cn CLI are where developers run Continue, approve tool calls, and apply its diffs.

    4. Tool execution: Supports

      Tool execution, supports. Agent mode and the CLI run terminal commands and MCP server tools behind per-tool policies, while the team's other integrations run outside Continue.

  3. Validate

    1. Debugging: Supports

      Debugging, supports. Developers add files, terminal output, and diffs to the context and ask Continue to explain or fix an error, but it does not investigate production issues.

    2. Testing: Supports

      Testing, supports. Continue can write tests and, in Agent mode, run them from the terminal, but it does not replace the team's test infrastructure.

    3. Code review: Touches

      Code review, touches. The CLI's headless mode can review staged changes from a Git hook or CI job; the hosted service behind Continue's pull request checks closed after the acquisition.

    4. Application security: Touches

      Application security, touches. Tool policies and local models limit what Continue can run and where code goes, but it is not an application-security product.

  4. Ship

    1. Source control: Touches

      Source control, touches. Continue can read diffs and write commit messages, while branches, history, and pull requests stay in the team's source control.

    2. CI/CD: Touches

      CI/CD, touches. The cn CLI runs headless in scripts and CI pipelines, but Continue is not a delivery platform.

  5. Operate

    1. Observability: Touches

      Observability, touches. Continue records development data locally and can send it to a team's own endpoint, but it does not observe running systems.

Market mapThe layers Continue covers, and who else owns each one.

  1. Coding & implementation

    CoreBuild

  2. Agent interface & developer runtime

    CoreBuild

  3. Codebase context & intelligence

    SupportsBuild

  4. Tool execution & integrations

    SupportsBuild

  5. Debugging & investigation

    SupportsValidate

7 more layers on the full map. Core, Supports and Touches describe coverage. They say nothing about quality.

More on Continue

  1. GILD ReviewGILD's evaluation, with the buying facts
  2. Research1 piece
  3. Guides3 guides
  4. Operator Insights1 operator account
  5. Where It FitsOn the Agentic Software Development stack
  6. Related Products8 products