Told to reboot a server, it destroyed systemd, destroyed containers, ran random

Source: github.com

40 points by jstanley 2 hours ago on hackernews | 31 comments

What version of Codex CLI is running?

v0.166.0

What subscription do you have?

Business

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 MOTERHFUCKERS. 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 FUCKING FUCKING SOULS FUCK YOU TO FUCKING HELL YOU DESERVE THE FUCKIGN GUILLOTINE IN PUBLIC SQUARE YOU MOTEHRFUCKING FUCKERS. DO YOU UJNDERSTAND YOUFUCKING FUCKISDFD FUSLDICHFLAKDF 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 FUCKIGN INSANITY THAT FUCII9GN KEEPS ME UP TO FUCKING MIDNGITHT YOOYU CUFIGHG FLUCIGNSD

Additional information

No response