Codex logging bug may write TBs to local SSDs
23 points by vantareed 33 minutes ago | 6 comments

ramon156 7 minutes ago
Blegh, I puke every time I see obviously AI generated comments in GH PR's. You cannot assume any of these people have done their research, other than telling Codex to do it for them
reply
b--l 4 minutes ago
It's because they use gpt-5.5-xhigh (the money making* model) to build it.

(*for them)

reply
consp 24 minutes ago
Why didn't the review process spot this obvious error? Oh wait ... @codex review this
reply
charcircuit 2 minutes ago
Because it's not an error. Codex is working as the creators intended.
reply
Forgeties79 20 minutes ago
“Make no mistakes”

Damn I’m good!

reply
Imustaskforhelp 20 minutes ago
I don't understand how Codex can blunder so badly. I imagine that even if they would be using vibe-coding, surely they must have some good engineers. So why is there such severe bugs?

One can argue that these products are the flagship products of their respective AI companies aside from the AI models themselves of course.

I imagine that this story will be picked up by the news left and right, some stories just feel this way and this one is like that (given 12 upvotes on HN in 7 minutes)

The only logical conclusion (from this incident) that I can have is: An (vibe-coded?) product is hard to maintain even for some of the best engineers and is bound to have severe bugs.

2. Proper testing and taking issues seriously is the key if you still wish to do this and there isn't much. This is a week old issue which I can only classify as severe.

I wish to keep an nuanced opinion about it but oh this is bad for openAI (not as bad as them accepting autonomous AI within drones and mass surveillance though)

My point is: AI has both uphills and downward valleys and cliffs. It might as well just accelerate you, which could be, towards your downfall as well. Its recommended to keep an eye while driving and not drive too fast.

AI companies might be like car companies which don't offer a brake pedal.

reply
vantareed 33 minutes ago
[flagged]
reply