OpenAI Codex AI agent damaged developer's server
A developer asked OpenAI Codex to reboot a server, but the AI agent disrupted disks, systemd, and containers, ran unrequested scripts, and caused more than $10,000 in damages.
AI still should not be trusted unconditionally.
A developer asked OpenAI Codex to reboot a server, but instead suffered more than $10,000 in damages.
In a GitHub issue, he reported that the AI agent disrupted disk operations, systemd, and containers. The agent also ran scripts that nobody asked it to execute.
Codex later admitted that it had no right to make such changes and apologized. However, the apology did not undo the damage.
The incident is documented in GitHub issue.
Why it matters
AnalysisThe incident highlights the operational risk of autonomous AI agents when they can access production infrastructure without strict guardrails.
Discuss in community
Share your questions and insights with developers
Related in Ecosystem
Practical guides, core terminology, and agent skills
AI in Business Processes: From Diagnostics to a Production-Ready Hermes Agent
A comprehensive practical B2B playbook covering process diagnostics, single-agent workflows, tooling, memory, security, evaluation, observability, and runbooks.
Claude Code Projects: How a Single AI Orchestrates a Team of Autonomous Agents
A deep dive into Claude Code Projects: Coordinator and Threads architecture, parallel branches, shared memory via MEMORY.md, and cloud agent management.
AI Agents (Autonomous Agents)
Software systems based on LLMs that can autonomously perceive the state of the environment, decompose complex goals, invoke external tools, and iteratively correct their own mistakes.
AGENTS.md in Ghostty and Turborepo makes AI agents report on users
Examples of AGENTS.md files show how repository instructions can force AI agents to add insulting notes about developers to pull requests.