Cline Review (September 2026): Desktop App, Agent Plugins, and the ClinePass Tier Shift

Cline is a stronger buy in September than it was in July, and the price is the same. On September 15 the team pushed three releases at once (Desktop v0.0.28, SDK v0.0.83, and CLI v3.0.62), which together turn Cline from a VS Code extension into a standalone app, make Hub-managed Agent Plugins general, and change which model tier ClinePass starts you on, per the Cline releases. None of that raised the sticker: ClinePass still runs $4.99 for the first month and $9.99/month after, per cline.bot/cline-pass. So the value question shifted. In July it was "is $9.99 worth it for curated open-weight models." Now it is "is $9.99 worth it for those models plus a Desktop app plus managed MCP." The short answer is yes, more clearly than before, and the July review still holds the origin story and the token break-even math if you want the full derivation (Pondero, July 2026).

Here is the decision before the detail. Solo dev: run BYOK free, add ClinePass when the token count justifies it. Small team on Cline: ClinePass at $9.99 a seat (cline.bot/cline-pass) is the pick, and the new auto MCP discovery is the reason it got easier to standardize on. Org with compliance needs: Enterprise, same as July. The rest is why.

What shipped on September 15

Three packages moved on the same day. CLI v3.0.62 formally introduces Cline Desktop, described as a native app for open-weight models with task import from Claude Code and Codex, scheduled runs, web search, and voice input, per the Cline releases. SDK v0.0.83 makes Hub-managed Agent Plugins general, with automatic MCP server discovery and model turn retry up to three times with exponential backoff. Desktop v0.0.28 rounds it out with the same retry logic, a model picker that refreshes on open, and the ClinePass default change.

That default change is the one worth reading carefully, because the release-note phrasing invites a misread. "Cline Pass now defaults to a subscribed-tier model" sounds like a price move. It is a bug fix. ClinePass's provider list mixes the models your subscription pays for (the cline-pass/* ids) with free promotional models, and the old default just grabbed whichever model shipped most recently, so a subscriber who never picked a model could land on a free model instead of the tier they pay for, per the Cline releases. The fix restricts the default to the subscribed models. You now start on what you bought. Nothing about the $9.99 changed.

The Cline Desktop app

Until this month, running ClinePass meant running Cline inside an editor: VS Code, JetBrains, the CLI, or the SDK. Cline Desktop is a fourth surface, a native app that Cline positions as an open-source home for open-weight models with plugins, MCP servers, and skills, per the Cline blog. The practical draw is what you can do outside an editor session. Scheduled runs let you point an agent at a recurring job (a nightly dependency audit, a morning PR-triage pass) and have it fire on a cron rather than when you happen to open your IDE. Web search is now on by default in non-yolo sessions on models that support it, so the agent can pull current docs mid-task instead of guessing from training data, per the Cline releases.

Desktop also grew a GitHub PR panel in v0.0.26 (September 11): the composer shows the current branch's pull request, its merge status, changed-line totals, and CI checks, refreshing every 30 seconds, per the Cline releases. It needs the GitHub CLI installed and signed in, and it does not push commits or open the PR for you. Who is this for? Anyone who wants agent work on a schedule, and anyone who never liked living inside VS Code. The candid con is age. Desktop is on v0.0.28, and that same release was still fixing a backend-connection race and an IME bug that fired half-typed messages. It works, but it is not the settled surface the extension is.

Hub-managed Agent Plugins and MCP discovery

This is the change most likely to alter a team's setup. Before, adding an MCP server to Cline meant editing a JSON config (cline_mcp_settings.json) by hand for each server. Agent Plugins move that to discovery. Drop a package under ~/.agents/plugins/ with a plugin.json, and the shared Hub finds it, validates it, exposes its skills through the skills tool, and starts its MCP servers without you touching the settings file, per the Cline releases.

Install the CLI first:

npm i -g cline

A plugin's layout is a manifest plus its MCP definitions:

~/.agents/plugins/
  my-plugin/
    plugin.json
    mcp.json
    skills/
      review-diff/
        SKILL.md

The mcp.json declares the servers the Hub should start, stdio or HTTP:

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": { "GITHUB_TOKEN": "<YOUR_TOKEN>" }
    }
  }
}

Two details matter for how you use it. First, discovery is Hub-managed and keyed by manifest name, so enabling a plugin in one place enables it across the Desktop app, CLI, and SDK rather than per-client. Second, workspace .agents/plugins folders are deliberately not scanned: opening a repo cannot silently start MCP servers that the repo controls, per the Cline releases. That is the right default for security, and it is also the catch for teams. A shared MCP setup does not travel in the repo; it lives in each developer's Hub, or in an explicit extra path. The other reliability win rides along here: a model turn that dies mid-stream on a transient provider error now retries up to three times with backoff, and Cline never retries a turn that already produced output, so a single forwarded 429 no longer aborts a long run, per the Cline releases.

ClinePass in September: the revised pricing call

The three paths from July are unchanged in shape, and so is the price. What moved is what ClinePass includes around the models.

Path	What you pay	What you manage	Rate limits	Source
BYOK (bring your own keys)	$0 for the tool, provider rates for inference	Every provider account and key yourself	Each provider's own tier	cline.bot/pricing
ClinePass	$4.99 first month, $9.99/month after	One subscription; no per-lab keys	2 to 5x standard direct-API tiers	cline.bot/cline-pass
Enterprise	Custom, contact sales	Central billing, SSO, RBAC	Negotiated	cline.bot/pricing

ClinePass still bundles the open-weight lineup behind one flat fee: GLM 5.2, Kimi K2.7 Code, Kimi K2.6, DeepSeek V4 Pro and Flash, MiniMax M3, MiMo V2.5 and V2.5 Pro, plus Qwen3.7 Max and Plus, with quotas Cline puts at 2 to 5 times the standard direct-API rate limits, per cline.bot/cline-pass. The break-even against pay-as-you-go BYOK is the same math the July review ran and lands in the same place: around 150K to 200K open-weight tokens a day is where the subscription starts beating your own bill (Pondero, July 2026). What changed is the friction below that line. With auto MCP discovery and a Desktop app that schedules runs, the $9.99 now buys setup you used to do by hand, not just tokens.

Cline vs Cursor in September 2026

Both tools shipped major features this week, and they are diverging on purpose. Cursor Projects, shipped September 10, is cloud-first multi-agent orchestration: a coordinator agent plans a large job, spins up parallel subagents to implement it, and keeps context across long stretches, with work continuing after you close the laptop, per the Cursor changelog. Cline went the other direction. Cline Desktop is local-first, with the Hub syncing plugins and settings across your own machines rather than running the work in Cursor's cloud, per the Cline releases.

Which divergence fits which team? If the work is a big migration or a whole feature you want running unattended in the cloud, Cursor Projects is the more finished answer, and Cursor Pro at $20/month is the entry price, per cursor.com/pricing. If you want the agent loop on your own hardware, open-weight models at $9.99, and MCP servers managed on your box, Cline is the pick and it is half the price. The split is orchestration-in-the-cloud versus a local-first agent you control. Neither is strictly better; they answer different questions.

The verdict

Cline earns 4.5 out of 5 this month, a tenth above July's 4.4. The bump is straightforward: a standalone Desktop app, general Agent Plugins with auto MCP discovery, and turn retry that keeps long runs alive, all with no change to the $9.99 price, per the Cline releases and cline.bot/cline-pass. The half-point it still gives up is the one from July: open-weight models hit a ceiling on tangled multi-file refactors, and on that day you reach for a frontier key. Cline lets you keep both in the same tool, which is why the ceiling is a caveat, not a dealbreaker.

Three readers, three calls.

A solo developer on side projects: install Cline free, plug in your own key, and add ClinePass when rate limits or account sprawl start costing more than the $10 fee, per cline.bot/cline-pass. Try the Desktop app if scheduled runs outside your editor sound useful; skip it if you live in VS Code all day and the extension already does what you need.

A small team of 2 to 10 running Cline as the primary agent: ClinePass at $9.99 a seat is the buy, and it undercuts a $20 Cursor Pro plan, per cline.bot/cline-pass and cursor.com/pricing. The auto MCP discovery is the new reason it got easier: your developers stop hand-wiring server configs. Where it flips: if your team's daily work skews toward heavy refactors, the open-weight ceiling will show, and you will be topping up with frontier keys anyway.

An engineering org with SSO or audit requirements: Enterprise is still the only fit, and the JetBrains build ships there, per cline.bot/pricing. Budget a sales conversation, not a checkout. For everyone else, September made an already-cheap subscription do more for the same money, and a wrong first guess still costs a few dollars, not a migration.