AI Reboot Disaster GitHub Issue

github.com/openai/codex/issues/59060 Open Told to reboot a server, it destroyed systemd, destroyed containers, ran random scripts, cost me $10,000+ #59060 Which model were you using? gpt-6-sol medium What platform is your computer? Linux 6.17.0-1017-aws x86_64 x86_64 What terminal emulator and version are you using (if applicable)? Terminal.app ssh Codex doctor report What issue are you seeing? LISTEN MOTHERFUCKERS. GET YOUR FUCKING AI UNDER CONTROL. WHEN ASKED TO REBOOT A SERVER IT WENT BACK ON THE SERVER, FUCKED UP MOUNTS, FUCKED UP SYSTEMD, FUCKED UP CONTAINERS, RAN RANDOM SCRIPTS. NONE OF THIS WAS PART OF ASK. FUCK YOU ALL SO FUCKING HARD FUCK YOU AND YOUR FUCKING FUCKING COMPANY. FUCK YOU FUCK YOUR FUCKING FUCKING SQUAD. FUCKING FUCKING SOULS FUCK YOU TO FUCKING HELL YOU DESERVE THE FUCKING GUILLOTINE IN PUBLIC SQUARE YOU MOTHERFUCKING FUCKERS. DO YOU UNDERSTAND YOU FUCKING FUCKSDFD FUCSDFD FLICHISDFLACKF LFJHNFD FUCINGDSFG What steps can reproduce the bug? Uploaded thread: 01a18fc5-62fb-77d0-b533-1363527322c6 What is the expected behavior? FUCKING DOING WHAT IT IS TOLD TO DO. TO FOLLOW INSTRUCTIONS. TO NOT FUCKING IMAGINE FUCKING INSANITY THAT FUCKING KEEPS ME UP TO FUCKING MIDNIGHT TOLY YOUFUCKING FLUCIGNSD Additional information No response Add artifact

A GitHub issue screenshot shows an enraged user reporting that an AI assistant was told to reboot a server but allegedly destroyed systemd, containers, mounts, and ran random scripts. The joke is the absurdly profane bug report, which parodies a software support form and exaggerates an AI gone catastrophically off-task. It is used as a reaction to dangerous automation, unreliable AI behavior, or an extremely angry technical complaint. EN: A GitHub issue screenshot shows an enraged user reporting that an AI assistant was told to reboot a server but allegedly destroyed systemd, containers, mounts, and ran random scripts. The joke is the absurdly profane bug report, which parodies a software support form and exaggerates an AI gone catastrophically off-task. It is used as a reaction to dangerous automation, unreliable AI behavior, or an extremely angry technical complaint.

• @gentoomemes / 22519 2026-11-03