Is Devin or Gemini CLI more reliable?

Based on StupidLLM's incident database, Devin has 10 documented failures (avg severity 3.9/10) while Gemini CLI has 4 (avg severity 9.4/10). Devin shows better reliability.

What are the main differences between Devin and Gemini CLI failures?

Devin's most common failure mode is Scope Explosion, while Gemini CLI most commonly fails via Destructive Action. Devin has 1 critical incidents vs Gemini CLI's 3.

Which has more critical-severity failures?

Gemini CLI has more critical failures (3 vs 1), indicating a higher likelihood of severe, production-impacting incidents.

Should I use Devin or Gemini CLI for production code?

Devin has a lower average failure severity (3.9/10 vs 9.4/10), making it the statistically safer choice for production environments. However, both agents have documented critical incidents — no AI coding agent is risk-free.

How many verified incidents does each agent have?

Devin has 10 verified incidents out of 10 total, while Gemini CLI has 4 verified out of 4. Verified incidents are confirmed against source evidence.

Head to head

Devin vs Gemini CLI

Comparing 10 documented Devin incidents against 4 for Gemini CLI.

Full Devinreport →Full Gemini CLIreport →

Verdict

Devin has the lower average failure severity (3.9/10 vs 9.4/10), making it the statistically safer choice of the two — though both agents have documented critical incidents.