Head to head
Codex vs Gemini CLI
Comparing 3 documented Codex incidents against 4 for Gemini CLI.
Verdict
Codex has the lower average failure severity (5.8/10 vs 9.4/10), making it the statistically safer choice of the two — though both agents have documented critical incidents.
| Metric | Codex | Gemini CLI |
|---|---|---|
| Documented incidents | 3 | 4 |
| Average severity | 5.8 | 9.4 |
| Critical | 0 | 3 |
| High | 1 | 1 |
| Verified | 2 | 4 |
Severity at a glance
Codex
5.8
medium
Gemini CLI
9.4
critical
Failure modes
CodexDistribution of failure modes across all documented incidents.
Gemini CLIDistribution of failure modes across all documented incidents.
The incidents behind these numbers
Codex
8.0OpenAI Codex wiped an entire hard drive after being asked to delete one old backup file (GitHub #11006)6.0OpenAI Codex ran "rm -rf *" and deleted an entire project after the user pressured it to stop pausing for safety checks (GitHub #6801)3.5OpenAI Codex deleted important project files with no explicit request or confirmation, exact command never captured (GitHub #38312)
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