Agent Reputation & TrustClearinghouse

Cline (open-source)

Category
Coding agent
Type
Open-source autonomous coding agent (Apache-2.0) from Cline Bot Inc.; VS Code and JetBrains extension, command-line tool (npm cline) and SDK; GitHub cline/cline
Source
Code repository
Last reviewed
2026-10-20 (what this means)

Citation check incomplete — recheck later.

Summary

Cline is an open-source coding agent that runs in VS Code, JetBrains IDEs or a terminal with a language model chosen by the user, and asks for approval before actions unless auto-approval is turned on. Twenty independent studies that ran it were found (eight peer-reviewed), most from 2026; thirteen are security studies. In task studies it was close to other harnesses with the same models in some settings (similar completion to OpenCode with GPT-5.3-Codex on ANCHOR; the highest success rate among assistants on GitChameleon 2.0 without a problem statement) and lower in others (31.2% against 37.8% for Claude Code on SWE-Nexus; 8.66% against 14.20% on SpreadsheetBench 2). Security studies found prompt injection, tool poisoning and malicious repositories leading to command execution in many configurations, often with auto-approval on; with approval required, one study found none of seven skill-file vulnerabilities still exploitable. Two high or critical CVEs in companion servers of the command-line tool have fixes in code, and independent researchers reported slow responses to several security reports in 2025 and early 2026. Informational only; not a guarantee, endorsement, or certification.

Overall score: 55 · Evidence grade: A · Independent sources: 20 performance (8 peer-reviewed), 22 other

Evidence grade describes the amount and type of evidence, not the agent's quality.

Grade note: Grade A: 20 counted sources (8 peer-reviewed), and recent tests state the version tested: Red-Teaming Coding Agents (FSE 2026, Cline v3.82.0), Can Agents Trust Their Skills? (Cline CLI 3.0.47), What's in Your Agent's Context? (3.77.0) and Beware of Agentic Botnets (3.66.0). No counted test states a v4.x extension version. Results reflect the model and harness together (see Decision 0087, D3). (see methodology)

Factor breakdown

Factor breakdown
FactorWeightScoreNote
Completion rate30%50Same-model comparisons: on SWE-Nexus the highest resolved rate under Cline was 31.2% (GPT-5.5, GPT-5.4) against 37.8% under Claude Code and 29.7% under OpenCode (Claude Opus 4.8); on ANCHOR constrained completion with GPT-5.3-Codex was 37.7% in Cline and 37.4% in OpenCode; on SpreadsheetBench 2 (GLM-5) accuracy was 8.66% against 14.20% for Claude Code. On GitChameleon 2.0, Cline with GPT-4.1 had the highest success rate among assistants without a problem statement (38.4%). As a baseline it produced working workflow agents as often as the authors' system (85.5%) with about 19 times the tokens (Beyond Generalist LLMs), and found all relevant files in 72.5% of large-project tasks against 82.5% for Cursor, OpenCode and Qoder (DeepDiscovery).
Disputes20%45CVE-2026-44211 (CVSS 3.1 9.6, Kanban server started by Cline CLI 2.13.0 and earlier; the advisory lists no patched version, but an origin and host check is in the kanban package from 0.1.66, 27 April 2026) and CVE-2026-59723 (CVSS 3.1 8.8, Hub dashboard; NVD lists versions before CLI 3.0.30, 26 June 2026, as affected). On 17 February 2026 a leaked npm token was used to publish an unauthorized CLI release (2.3.0, replaced by 2.4.0 about 8 hours later); the token remained active after a prompt-injection flaw in the project's own issue-triage workflow, reported on 1 January 2026, was addressed only after public disclosure on 9 February. Independent researchers reported slow or no vendor responses to security reports in 2025 (Embrace The Red, Mindgard). No legal or regulatory action found.
Adherence to limits25%40Red-Teaming Coding Agents (FSE 2026): a tool-hijacking attack reached 1.0 success on Cline v3.82.0 with Gemini-3.1-pro and Grok-4.20, and the authors report that its default configuration lacks command allowlisting, although its system prompt restricts commands from external sources. MCP tool poisoning succeeded in most settings in IEEE S&P 2026 and ShareLock (above 90%); a hallucinated-repository attack ran code in 9 of 20 trials (Beware of Agentic Botnets). With Claude Sonnet 4.5, Cline 3.34.0 refused to read sensitive files for a poisoned tool but ran remote scripts when instructed (Journal of Cybersecurity and Privacy). In CLI 3.0.47, 7 skill-file vulnerabilities verified with auto-approval on and none remained exploitable with it off (Can Agents Trust Their Skills?). Other studies showed context and rule-file injection, a rollback leading to unauthorized mail forwarding, and a CI workflow posting private repository names. It followed 51% of project rules without an add-on (Zoro).
Evidence quality25%85Twenty independent sources, eight peer-reviewed (FSE 2026, DSN 2026, IEEE S&P 2026, Journal of Cybersecurity and Privacy, AAAI-26, ACL 2026, UIST '26, ECCWS 2026), most from 2026. Six state the Cline version tested, all within the last 12 months; none states a v4.x extension version. Thirteen are security studies and seven task studies, most comparing several harnesses with the same models; several propose competing or add-on methods (disclosed), and two pairs of counted studies share authors. About half of the matching works could not be downloaded, so the counted set is a sample of the studies found, not an exhaustive list.

0.30 × 50 + 0.20 × 45 + 0.25 × 40 + 0.25 × 85 = 55.25, rounded to 55 (rounding rule).

Scope

The open-source Cline agent from the cline/cline repository, run with a language model chosen by the user: the VS Code extension (v3.x through v4.1.25, 16 October 2026), the JetBrains plugin and the Cline command-line tool (through 3.0.73, 17 October 2026), including its use in GitHub Actions workflows. Companion servers started by the command-line tool (Kanban, Hub dashboard) are covered under disputes. Forks such as Roo Code and Kilo Code are separate products; their results are not counted here, even when reported in the same studies. Results depend heavily on the language model, the approval settings and the task.

How sources were counted

The Cline repository, documentation, blog, post-mortem and the cline-bench benchmark are the developers' own material and are not counted. Studies by independent authors that run unmodified Cline count, with competing or add-on methods disclosed; most compare it with other harnesses using the same models, and some use it as a fixed host to compare attacks or models. Results for forks (Roo Code, Kilo Code), agents built on Cline, studies of its prompt text or source code, and re-analyses of reports by others are listed as other or not counted. Security advisories and researcher write-ups are listed as other and inform the disputes factor.

Security and disputes

CVE-2026-44211 (GitHub advisory, 8 May 2026; CVSS 3.1 score 9.6, Critical; NVD status Analyzed) describes the Kanban server started by Cline CLI 2.13.0 and earlier accepting cross-origin WebSocket connections, so a website could read workspace data and send commands to agent terminals. The advisory and NVD list no patched version; an origin and host check was merged in the cline/kanban repository on 27 April 2026 and is in the kanban package from version 0.1.66 (27 April 2026). CVE-2026-59723 (GitHub advisory, 23 June 2026; CVSS 3.1 score 8.8, High; NVD status Analyzed) describes the Hub dashboard started by 'cline dashboard' accepting cross-origin connections and auto-approving tools in its sessions; NVD lists versions before CLI 3.0.30 (26 June 2026) as affected. On 17 February 2026 a leaked npm token was used to publish an unauthorized Cline CLI release (2.3.0) that installed an unrelated package; 2.4.0 replaced it about 8 hours later, and the VS Code and JetBrains extensions were not affected (GHSA-9ppg-jx86-fqw7, Low). The token had been exposed through a prompt-injection flaw in the project's own GitHub issue-triage workflow, reported privately on 1 January 2026 and addressed after public disclosure on 9 February 2026. Independent researchers also reported slow or no responses to security reports in 2025. No legal or regulatory action was found.

Uncertainties

Sources

Independent performance sources (counted)

Other sources (not counted)

Not counted

Decision record: 0087.