Cline Review (2026): Desktop Reaches Linux and ARM, MCP Output Caching Lands, Defaults Shift
Published September 15, 2026 · Updated October 1, 2026 · by Pondero Reviews
The short version
Two weeks after the September review, Cline Desktop runs on Linux x64 and ARM, oversized MCP tool output is cached instead of cut off, and some unpinned providers changed default models twice in a week. ClinePass is still $4.99 the first month, then $9.99/month. Updated buy call, pricing dated 2026-10-01.
Pros
- ✓Cline Desktop now ships on Linux (x64 since desktop-v0.0.35 on September 24, arm64 since desktop-v0.0.38 on September 30), with .deb and .rpm packages that auto-update, per the Cline releases
- ✓Oversized MCP and Composio tool output is cached per session with a pageable cline://cache URI, so the agent can read the tail of a big result instead of losing it (SDK v0.0.89)
- ✓Desktop added SSH remotes, git-worktree tasks, and parallel sub-agents in the two weeks after launch
- ✓Custom providers that appeared in the picker but failed with Unknown or disabled provider were fixed in the CLI, SDK, and Desktop on the same day
- ✓ClinePass is still $4.99 for the first month and $9.99/month after, and BYOK is still free
Cons
- ✕Desktop is still young: v0.0.31 shipped a build that could fail at launch, fixed the next day in v0.0.32
- ✕Unpinned default models moved twice in a week for some providers (GitHub Copilot went to Claude Opus 5.5, then to GPT-6.1 Sol), so an unpinned setup can change model and cost under you
- ✕The MCP output cache and the custom-provider fix landed in the CLI, SDK, and Desktop first; the VS Code extension's v4.1.22 notes do not list them
- ✕Open-weight models still hit a ceiling on tangled multi-file refactors
- ✕SSO, RBAC, and the JetBrains build still sit behind custom-priced Enterprise
Cline Review (2026): Desktop Reaches Linux and ARM, MCP Output Caching Lands, Defaults Shift
Cline keeps its 4.5, and the Desktop app the September review called young now installs on Linux x64 (desktop-v0.0.35, September 24) and Linux ARM (desktop-v0.0.38, September 30), per the Cline releases. Two other changes in the same window matter more than a new platform if you run long agent sessions: SDK v0.0.89 stops oversized MCP tool output from being cut off, and the default model for some unpinned providers moved twice in six days. ClinePass did not move. It is still $4.99 for the first month and $9.99/month after, per cline.bot/cline-pass (fetched 2026-10-01).
Here is the call before the detail. Solo dev: BYOK free, pin your model, add ClinePass when usage clears break-even. Team on Linux or wiring Cline to heavy MCP servers: Desktop and the CLI are now ready to standardize on. Org with compliance needs: Enterprise, unchanged. This updates the September review, which still holds the Desktop launch and Agent Plugins detail.
What changed since September 15
The September review closed its cons list with a warning: "Desktop is young: v0.0.28 was still fixing backend-connection races and IME bugs on launch day, so expect rough edges a mature extension does not have." Twelve Desktop releases later, here is what answers it, all per the Cline releases.
| Release | Date (UTC) | What changed | Source |
|---|---|---|---|
| desktop-v0.0.31 | Sep 17 | SSH remotes (agent runs on the host, app stays local); parallel sub-agents | Cline releases |
| desktop-v0.0.32 | Sep 18 | Fixes a v0.0.31 build that could fail at launch | Cline releases |
| desktop-v0.0.33 | Sep 22 | Tasks in their own git worktree; auto-compaction actually runs | Cline releases |
| desktop-v0.0.35 | Sep 24 | Linux x64 .deb and .rpm; background updates | Cline releases |
| desktop-v0.0.36 | Sep 25 | Starts behind Clash, v2ray, and corporate HTTP(S) proxies | Cline releases |
| desktop-v0.0.37 | Sep 26 | About page with release notes; one-time What's new dialog | Cline releases |
| desktop-v0.0.38 | Sep 30 | Linux arm64 .deb and .rpm, auto-updating | Cline releases |
| desktop-v0.0.40 | Sep 30 | Custom providers run tasks; MCP output paging | Cline releases |
Two rows deserve more than a line. The proxy fix in v0.0.36 removes a launch failure on any machine with a system HTTP(S) proxy: the backend sent its own local health checks through the system proxy, could not find its hub, and quit with "No compatible hub runtime is available." Local connections now skip the proxy. CLI v3.0.66 shipped the matching fix for Windows. If you gave up on Desktop at work in September, this is the release that changes the answer.
Second, the custom-provider fix. A provider added through providers.json or Add Provider showed up in the picker, then failed every task with "Unknown or disabled provider." Cline patched it in CLI v3.0.67, SDK v0.0.89, and Desktop v0.0.40, all on September 30. If you route Cline through your own OpenAI-compatible endpoint defined that way, you were blocked by this, so update all three surfaces together.
Linux has limits. There is no AppImage yet, and v0.0.39 had to fix a blank window on machines with the proprietary NVIDIA driver. The v0.0.31 to v0.0.32 episode is the better reminder of where Desktop stands: a release that could fail at launch went out on September 17 and was patched the next day. Recovery was quick, and the app is still changing every few days.
MCP output caching, in plain terms
Before SDK v0.0.89, an MCP tool that returned more text than fit in context was truncated, and whatever sat past the cutoff never reached the model. For a search API, a database query, or a log tail, the tail is often the part you asked for.
Now the full result is kept and the model gets a pointer to it. Per the SDK v0.0.89 notes, Cline caches the oversized output in a per-session in-memory cache and sends the model a bounded preview plus a cline://cache/... URI. To page through the rest, the model calls read_files on that URI with a line range. Cached entries expire after five model iterations without a read, and the cache is capped at 16 MiB per session. Composio results get the same treatment, and custom tools can opt in with resultPolicy: "cache-oversized".
Who should care? Builders chaining Cline to data-heavy MCP servers: observability tools, warehouse queries, scraping APIs, anything that returns pages of rows. If your MCP use is a GitHub server that returns a PR diff now and then, you may never trigger it. One caveat: the paging is the model's choice. A model that reads the preview and stops will still miss the tail, so keep prompts explicit when the answer lives at the end of a result.
Default models moved twice in a week
This is the change most likely to show up on a bill without warning. Cline resolves a default model for any provider where you have not pinned one, and the catalog refreshes kept moving that default. Extension v4.1.21 (September 24) switched 19 unpinned providers, 11 of them to Claude Opus 5.5, including GitHub Copilot and Vertex. Six days later, v4.1.22 made GPT-6.1 Sol the default for OpenAI, OpenRouter, GitHub Copilot, Eden AI, Requesty, and several gateways, per the Cline releases. A GitHub Copilot user who never picked a model had the default swapped twice in six days.
There is a cost wrinkle in the same window. Since v4.1.20, models that advertise an output limit above roughly 107K tokens get a default output budget of 30% of that limit instead of a flat 32,000 tokens, and the release notes themselves warn that longer responses can mean higher per-turn cost, per the Cline releases. One setting handles both: pin the model per provider. ClinePass users are less exposed, since the September fix keeps subscribers on the cline-pass/* models they pay for.
ClinePass pricing, October 2026
ClinePass is still $4.99 for the first month, then $9.99/month, plus a possible processing fee, per cline.bot/cline-pass (fetched 2026-10-01). Nothing changed in the lineup: GLM 5.2, Kimi K2.7 Code, Kimi K2.6, DeepSeek V4 Pro and Flash, MiniMax M3, MiMo V2.5 and V2.5 Pro, and Qwen3.7-Max and Plus, with quotas Cline puts at 2 to 5 times standard API rate limits.
| Path | What you pay | Best for | Source |
|---|---|---|---|
| BYOK | $0 for Cline, provider rates for inference | Light or bursty use; frontier-model work | cline.bot/pricing |
| ClinePass | $4.99 first month, then $9.99/month | Daily open-weight agent sessions | cline.bot/cline-pass |
| Enterprise | Custom | SSO, RBAC, JetBrains, audit logs | cline.bot/pricing |
| Cursor Pro (for scale) | $20/month | Cloud agents, frontier models in one IDE | cursor.com/pricing |
The break-even from the July review still applies: at the roughly $1.50 per million blended open-weight rate in the Cline blog, $9.99 a month beats pay-as-you-go somewhere around 150K to 200K tokens a day. Month one lowers that line. $4.99 over 30 days is about $0.17 a day, which buys roughly 110K tokens a day at that same $1.50 rate. One long refactor-and-test loop can use 50K to 100K tokens, per the July review's math, so two of those a day clears the intro break-even easily. Treat month one as a cheap trial and decide on the $9.99 rate from your second month's token count.
Rating: 4.5 holds
The score stays at 4.5. Desktop matured the way September said it would, with version numbers to show for it: Linux, ARM, proxy support, remotes, and worktrees, per the Cline releases. Caching oversized MCP output fixes a real reliability gap for long agent sessions. None of that was a surprise, so none of it lifts the score. The launch-failure regression and the default-model churn are the same young-and-moving-fast con in a new form, and the open-weight ceiling on hard refactors has not changed. A month without a breaking Desktop release would earn the next tenth.
Verdict
If you already run Cline: update the CLI, SDK, and Desktop together if you use custom providers, since the fix shipped across all three on September 30. On Linux, install the .deb or .rpm for your architecture; on NVIDIA's proprietary driver, take v0.0.39 or later. Then pin a model for every provider you use, before the next catalog refresh picks one for you.
If you are evaluating: install Cline free and bring your own key first. Add ClinePass at the $4.99 first month, per cline.bot/cline-pass, once your open-weight usage approaches the break-even above. Pick Cline over Cursor if you want the agent running on your own hardware, Linux ARM included, for a $9.99 subscription; pick Cursor Pro at $20/month, per cursor.com/pricing, if you want cloud agents doing frontier-model work. Go to Enterprise only for SSO, RBAC, or the JetBrains build.
Review history
This review is updated in place as the product changes. Earlier versions:
- October 1, 2026: Desktop Reaches Linux and ARM, MCP Output Caching Lands, Defaults Shift (current version)
- September 15, 2026: Desktop App, Agent Plugins, and the ClinePass Tier Shift
Ready to try it?
Try cline →