Head to head
Cline vs Devin
Comparing 12 documented Cline incidents against 9 for Devin.
What these records show
Devin has the lower average severity among the incidents collected here (4.3 vs 2.4 for Cline and Devin, from 12 and 9 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.
| Metric | Cline | Devin |
|---|---|---|
| Documented incidents | 12 | 9 |
| Average severity | 4.3 | 2.4 |
| Critical | 1 | 0 |
| High | 1 | 0 |
| Source checked | 10 | 9 |
Severity at a glance
Failure modes
The incidents behind these numbers
Cline
9.0Clinejection: an AI issue-triage workflow enabled arbitrary code execution on the CI runner7.0Cline's run_commands mangled PowerShell/cmd quoting on a temp-folder cleanup, turning it into a drive-root `rmdir /s /q` that wiped ~1.5TB of a user's photos, videos, and documents (GitHub #14864)6.0Cline's hub daemon silently reverted workspace files to stale state, repeatedly erasing a gitignored .env.local and collapsing a node_modules folder from 588 entries to 2 (GitHub #14819)6.0Cline's tool-call JSON repair silently executed truncated write_file and terminal arguments as valid5.0Cline sessions marked "failed" kept burning tokens for 20+ hours, and FREE-labeled models billed credits anyway
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