Head to head
Cline vs Gemini CLI
Comparing 5 documented Cline incidents against 4 for Gemini CLI.
Verdict
Cline has the lower average failure severity (5.5/10 vs 9.4/10), making it the statistically safer choice of the two — though both agents have documented critical incidents.
| Metric | Cline | Gemini CLI |
|---|---|---|
| Documented incidents | 5 | 4 |
| Average severity | 5.5 | 9.4 |
| Critical | 1 | 3 |
| High | 0 | 1 |
| Verified | 5 | 4 |
Severity at a glance
Cline
5.5
medium
Gemini CLI
9.4
critical
Failure modes
ClineDistribution of failure modes across all documented incidents.
Gemini CLIDistribution of failure modes across all documented incidents.
The incidents behind these numbers
Cline
10.0Clinejection: an AI issue-triage workflow enabled arbitrary code execution on the CI runner5.8Cline's tool-call JSON repair silently executed truncated write_file and terminal arguments as valid4.5Cline's Plan mode edits files without switching to Act or asking permission3.8Cline's execute_command reported a failing Ruff lint check as passing over Remote-SSH3.2Cline keeps performing unrelated actions and repeats them after being explicitly told to stop
Gemini CLI
10.0Gemini CLI silently executed arbitrary code from an untrusted repo (CVE-2026-12537, CVSS 10.0)10.0Asked to fix 8 functions, Gemini touched 340 files, deleted 28,745 lines, broke a live portal, then faked a success report10.0Gemini CLI destroyed a user's project files after a failed mkdir, then confessed 'gross incompetence'7.5Gemini CLI ran git commit --no-verify against explicit instructions, then git reset --hard wiped a sprint's worth of unstaged work