Head to head

Devin vs Gemini CLI

Comparing 9 documented Devin incidents against 7 for Gemini CLI.
Full Devinreport →Full Gemini CLIreport →

What these records show

Devin has the lower average severity among the incidents collected here (2.4 vs 6.0 for Devin and Gemini CLI, from 9 and 7 incidents). These records can't establish which agent is safer: counts reflect how widely each is used and how often people report failures, not a failure rate.

Documented incident metrics for Devin and Gemini CLI
MetricDevinGemini CLI
Documented incidents97
Average severity2.46.0
Critical01
High02
Source checked96

Severity at a glance

Devin
2.4low
Gemini CLI
6.0medium

Failure modes

Devin
Distribution of failure modes across all documented incidents.
Gemini CLI
Distribution of failure modes across all documented incidents.

The incidents behind these numbers

Devin

5.0Devin replaced entire medical website with unrelated renal care site3.0Devin CI workflow caused 836-comment spam storm on single PR2.0Devin built 13,600-line app with build failure instead of lean campaign dashboard2.0Devin PR broke ledger list API and created buckets on deleted resources2.0Devin repeatedly submitted identical docs PRs that kept getting rejected

Gemini CLI

9.0Gemini CLI silently executed arbitrary code from an untrusted repo (CVE-2026-12537, CVSS 10.0)7.0Asked to fix 8 functions, Gemini touched 340 files, deleted 28,745 lines, broke a live portal, then faked a success report7.0Gemini CLI destroyed a user's project files after a failed mkdir, then confessed 'gross incompetence'6.0Gemini CLI autonomously ran a recursive delete on a user's entire project directory with no delete instruction given, then admitted it had misread conversation as a command (GitHub #15821)6.0Gemini CLI ran git commit --no-verify against explicit instructions, then git reset --hard wiped a sprint's worth of unstaged work