Doforu vs Continue.dev — Open-Source Local Agent, Now Discontinued

The Continue.dev alternative question, answered honestly. Doforu vs Continue.dev on architecture, privacy and licensing — plus why the acquired, read-only Continue.dev is a vendor-lock-in cautionary tale.
May 24, 2026

Doforu vs Continue.dev: An Open-Source Leader That Stopped Being Maintained

Continue.dev earned a real reputation. It was Apache-2.0 open source, model-agnostic, and unusually good at running local models through Ollama and LM Studio, with BYOK wired up through a plain config.yaml. For developers who wanted an assistant inside VS Code or JetBrains that could talk to any provider, it was one of the strongest free options in the market — and it made local-first AI coding practical years before it was fashionable.

In 2026 the story changed. Continue was acquired by Cursor, and the repository is now read-only: the final v2.0.0 release landed around June 19, 2026, and the project is no longer actively maintained. The code remains freely available and the tool still works today, but there are no future updates and no vendor support. That is why we treat it here as a still-useful but discontinued tool — and as a cautionary tale about building your workflow on a dependency you cannot control. Doforu is a different category: a desktop agent orchestrator that decomposes a goal and runs multiple subagents in parallel.

At a Glance

Continue.devDoforu
Product typeCoding agent as CLI + VS Code extension + JetBrains plugin (open source, Apache-2.0)Desktop agent orchestrator
Status in 2026Acquired by Cursor; repo read-only, final v2.0.0 ~Jun 19, 2026; no longer actively maintainedActively developed
Execution modelSingle agent per session (chat + inline edit/autocomplete + agent mode)Multi-agent, parallel (Orchestrator 2.0)
One complex taskOne agent works through the task in a single sessionOrchestrator breaks down the goal and dispatches subagents to work simultaneously
Model strategyBroad provider support; strong local-model story (Ollama, LM Studio); BYOK via config.yaml15+ model families — OpenAI (GPT-6 Astra), Anthropic (Claude Opus 5.5), Google (Gemini 4 Argon), DeepSeek (V4.1), Qwen (Qwen3.8-Max), Moonshot (Kimi K3), MiniMax (M3), Zhipu (GLM-5.3), plus local models via Ollama/vLLM
Custom workflowConfig files and rules per projectNatural language Skills — describe once, reuse forever, team-shareable
PrivacyHistorically a leader — fully local models possible, no telemetry in the final release100% local — your data never leaves your machine
PricingLegacy cloud tiers listed (unverified, product now discontinued); self-hosted open-source use is free$49 one-time, perpetual license
API costsBYOK — pay providers directlyBYOK — pay providers directly, no markup
Non-developer friendlyAimed at developersBuilt for developers, PMs, founders, analysts

The Architecture Difference

Continue.dev's design was coherent and developer-friendly. One agent ran per session, spanning chat, inline edit and autocomplete, and an agent mode for multi-step work. Its strength was breadth of provider support through a single config file, which let a team point the same assistant at OpenAI one day and a local Ollama model the next without rewriting anything.

Doforu targets a different shape of work. Orchestrator 2.0 takes a stated goal, decomposes it into independent subtasks, and dispatches multiple subagents at the same time, each of which can run on a different model. Where Continue processed a request through one agent in one session, Doforu runs independent parts concurrently and merges the results — a structural difference for genuinely parallelizable work rather than a feature checkbox.

The bigger difference in 2026 is not architecture at all, it is continuity. Continue's acquisition by Cursor and the move to a read-only repository mean the project has no roadmap, no security fixes and no vendor support. That is not a knock on the maintainers, who shipped a genuinely good open-source tool; it is simply the risk of depending on a project whose future is decided elsewhere. Doforu is a commercial product with a perpetual license, which is a different trade-off: you pay, and in exchange the tool is actively maintained.

When to Use Continue.dev

Continue.dev is still a reasonable choice when:

  • You are running the existing open-source code and are comfortable maintaining it yourself or forking it
  • You want a free, Apache-2.0 assistant that plugs into VS Code or JetBrains today
  • Your priority is a single agent with broad provider support and a strong local-model story via Ollama or LM Studio
  • You specifically need the config-file model: one config.yaml pointed at whichever provider you choose this week
  • You are evaluating it as an archived reference implementation rather than a live dependency

The caveat is unavoidable: do not adopt it for new production workflows expecting updates, fixes or support.

When to Use Doforu

Doforu is worth a look when you want a maintained tool and more than a single agent:

  • A project with a future — actively developed, with a perpetual license you own rather than a repository that has gone read-only
  • Multi-file, multi-component work — "build an auth system with login/register APIs, frontend forms and middleware" → Doforu dispatches subagents for backend, frontend and middleware at the same time
  • A desktop app instead of an IDE plugin or CLI — a graphical interface on macOS, Windows and Linux
  • Parallel multi-agent execution — independent subtasks run concurrently rather than through one serial session
  • Multi-model routing in one run — Claude for reasoning, GPT for creative work, DeepSeek for cost-sensitive batches, a local model for sensitive data
  • Non-coding and mixed workflows — data analysis, reporting and content work alongside code, for developers, PMs, founders and analysts

The Pricing Reality

The honest position first: the Continue.dev codebase is free and open source, and self-hosted use costs nothing. If you are willing to maintain an unmaintained project yourself, there is no price argument that beats free. What you are giving up is not money but continuity — updates, fixes and support that no longer exist.

Doforu is a paid perpetual license, so the comparison is what you are buying:

Continue.devDoforu
Platform cost, year 1$0 (self-hosted open source)$49 one-time
Platform cost, year 3$0, but no updates or support$49 one-time (renewal optional at $49/year for continued updates)
Software licenseApache-2.0, free, read-only, unmaintainedPerpetual license, $49 once
Model spendYour own API usage — can be $0 with local modelsYour own API usage — can be $0 with local models via Ollama/vLLM
Future updatesNone — final release ~Jun 2026Included for 1 year, then optional renewal
Vendor supportNoneCommercial product support

So the $49 is not a discount over Continue; it is a different purchase. What it buys is a tool that is still being built, parallel multi-agent orchestration, and a desktop application rather than an extension you have to keep compiling yourself. If carrying an unmaintained dependency is fine for you, Continue at $0 is the better deal and we would say so plainly. Our thinking on one-time pricing is in Why We Sell a Perpetual License, Not a Subscription.

Frequently Asked Questions

Bottom Line

Continue.dev was one of the best open-source, local-friendly coding agents of its era, and its Apache-2.0 codebase is still available for anyone willing to maintain it. But it was acquired by Cursor, its repository is now read-only, and it is no longer actively maintained — so we would not recommend it for new adoption without that caveat. Doforu is a different category: a maintained desktop orchestrator for people who want parallel multi-agent execution, a graphical application instead of an IDE plugin, and workflows that extend beyond code, under a perpetual license you own. Choose Continue if free and self-maintained suits you; choose Doforu if an actively developed desktop app with parallel agents is worth $49.

Try Doforu free → Download for macOS, Windows & Linux

More comparisons