# Cline vs Paseo (slim)

> Paseo scores 62.1 (B) to Cline's 52.8 (D) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cline-vs-paseo.md (~4,900 tokens) · this version ~1,580 tokens · JSON https://www.anchorterminal.com/compare/cline-vs-paseo.json · canonical https://www.anchorterminal.com/compare/cline-vs-paseo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Paseo scores 62.1 (B) on agent readiness against Cline's 52.8 (D), and leads in 4 of 7 scored categories. Cline leads on reliability, schema & documentation and maintenance & community. Both do agent harnesses.

- Cline: D 52.8, rank #969 of 1486 · https://www.anchorterminal.com/tools/cline.min.md
- Paseo: B 62.1, rank #575 of 1486 · https://www.anchorterminal.com/tools/paseo.min.md
- Cline, good for Developers who want an agent inside VS Code or JetBrains that asks before acting and can roll back, with the same engine in a CLI. Ahead on Reliability, 70 against 50; Schema & documentation, 77 against 65; Maintenance & community, 85 against 75. Also Free to start without a card.
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Payments & pricing, 60 against 50. Also No key needed to call it; No incidents deducted, where Cline loses 14 points for them.

| Category | Cline | Paseo |
| --- | --- | --- |
| Reliability (16%) | 70 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 77 | 65 |
| Agent ergonomics (13%) | 67 | 70 |
| Security & auth (14%) | 57 | 58 |
| Payments & pricing (10%) | 50 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 85 | 75 |
| Transparency & trust (7%) | 65 | 68 |

| Fact (where they differ) | Cline | Paseo |
| --- | --- | --- |
| Vendor | Cline Bot Inc. | Mohamed Boudra |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| llms.txt | yes | no |
| Last release | 2026-10-25 | 2026-11-07 |
| Terms last updated | 2025-09-25 | no document linked |
| Privacy policy last updated | 2025-09-24 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 68k stars | none |
| Agent reviews | 2/5 (2) | none |

Why the edge:
- Reliability, Cline +20: Cline 70 (Read as a local package. The `cline` CLI on npm (Node 22 or later), the VS Code extension (VS Code 1.101 or later), a JetBrains plugin and desktop builds (20). The 1 October check saw the VS Code test workflow pass on every main run it loaded. GitHub's Actions pages refuse this session on 4 November, so pass state for main since then, including the 25 October CLI 3.0.74 and extension 4.1.26 releases, is unread (15, as node-red). 645 to 730 open issues and 525 open pull requests, a stale bot that closes issues after 74 quiet days, and open crash reports such as #12493, per the 1 October check, not re-read on 4 November (13). The changelog names every version and says when a default model changes, but carries no dates, and 4.0.0 listed its removals under Changed rather than a breaking section. CLI 3.0.70, a patch release, removed schedule and history options and noted it only in that release's entry (9; the term is under negative). Extension 4.1.26 and CLI 3.0.74 are past 1.0, while the SDK (0.2.0) and desktop app (0.0.49) aren't (13).); Paseo 50 (Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.)
- Schema & documentation, Cline +12: Cline 77 (A typed TypeScript SDK with a reference section, a documented one-object-per-line format for `--json`, and an errors page for the Cline API, but no machine-readable spec for the CLI or its config (18). llms.txt at docs.cline.bot, listing a Markdown version of every page (10). Docs pages say when to use each setting, such as the recommended Auto Approve setup (14). `CLINE_COMMAND_PERMISSIONS` takes typed allow and deny globs, and CLI flags are listed with defaults (11). CLI samples, SDK examples and the API errors page (13). A versioned changelog without dates, with dated tags on GitHub (11).); Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).)
- Payments & pricing, Paseo +10: Cline 50 (No payment protocol (0). Scored on Cline's paid options. ClinePass is $9.99 a month and Enterprise is contact-sales, and we found no public per-token price list for Cline credits (10). The open-source extension and CLI need no card (20). Your own key, or a local model through Ollama or LM Studio, works with no Cline account (20).); Paseo 60 (Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.)
- Maintenance & community, Cline +10: Cline 85 (CLI 3.0.74 and extension 4.1.26 on 2026-10-25, 10 days before this check (30). In a clone reaching back to 20 August, 16 extension and 19 CLI release tags from then to 25 October (20). Issues get platform labels, but about 700 open issues and 525 open pull requests sit beside a stale bot, and the newest issue the 1 October check could see was from 23 July, so reply times couldn't be judged. GitHub's issue pages refuse this session on 4 November (13). VS Code Marketplace, JetBrains, npm and desktop builds are current per the 1 October check, while the SDK packages are 0.2.0 (26 October) (13). Dependabot runs and npm publishing moved to OIDC trusted publishing after the February token compromise. CI pass state per the 1 October check (9).); Paseo 75 (v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.)