Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Codex logging bug may write TBs to local SSDs

github.com

Post reply on HN
Print view View original

201–210 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#201

Post by cl3misch »

i2km wrote: post #39

Shocking. Been open a week and AFAICT just silence from OpenAI. I just find it baffling. You'd think that these vendors would be very sensitive to this sort of issue. I mean, surely they have multiple agents hooked up to github monitoring potential issues and proposing fixes, right? ...right? Surely it should be trivial for them to have their own tools spinning away trying to fix all the github issues in real time...

There have been Issues on Github about the same problem since April. I'm using Codex a lot and I'm very happy with its performance (UX and output), but it's baffling they haven't fixed this problem.

Re: Codex logging bug may write TBs to local SSDs

#202

Post by layer8 »

r_lee wrote: post #64
b--l wrote: post #10

Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…

if we are at 10x with AI and near AGI or ASI, then how is it possible that these products (Codex, Claude Code CLI) are still such garbage? shouldn't this "agentic AI revolution" have long solved this already? no way they're over there saying "we are on it plz wait" or that "it's too much effort"?

The issue is that apparently AI coding means that developers stop caring about software quality. Which puts the whole purpose into question.

Re: Codex logging bug may write TBs to local SSDs

#203

Post by geodel »

thewebguyd wrote: post #186
geodel wrote: post #179

Earlier quoted context omitted.

> Maybe if Anthropic claimed that you could write an unsupervised loop that writes perfect software, the critics would make more sense. Or to be upstanding, ethical companies that they are. Just put disclaimer after every prompt response and on their website "AI generated code has no absolutely no guarantee of quality or correctness. Human prompter must be held accountable for any mistake or inaccuracies." Hope it wo…

See, but that would counter act all of their marketing and hurt the feelings of all the execs that desperately want to believe that software development is "solved" and in the near future they won't have to hire those expensive, pesky developers ever again.

Two trends I see at work:

1) No more human written code in projects, all code must be AI generated.

2) Developers are responsible for all code AI generated.

Combine that with fear of losing job and you have no one calling out management bullshit on their face.

Re: Codex logging bug may write TBs to local SSDs

#204

Post by never_inline »

jofzar wrote: post #42
59nadir wrote: post #18

Earlier quoted context omitted.

Then they can apply a clean solve , the cleanest solution . It's fascinating how offensive some of this verbiage becomes to you when you see it attached to LLM output too much.

Ugh this one's gets me so bad, same with "wire" and "wired" everything is wired to something.

that's a real gap

Re: Codex logging bug may write TBs to local SSDs

#205

Post by datsci_est_2015 »

me551ah wrote: post #122
jofzar wrote: post #41

Earlier quoted context omitted.

> Codex is one of the most infamous examples of slopware Woah, let's not forget Claude code is right there

Claude is also weird for being the only coding assistant that for some reason doesn't support AGENTS.md. Codex, Amp, Cursor all of them support it and read from it, but not claude which forces it's users to use CLAUDE.md instead. The issue is the higest voted issue on their gitlab repo: https://github.com/anthropics/claude-code/issues/6235

Literally trying to use file naming to build a moat. “We can’t switch to Cursor, we’d have to rename all of our files from CLAUDE.md to AGENTS.md!”

Re: Codex logging bug may write TBs to local SSDs

#206

Post by [deleted] »

troupo wrote: post #192
ValentineC wrote: post #133

Earlier quoted context omitted.

My CLAUDE.md is just: @AGENTS.md And Claude processes it just fine. (I see that it's a common workaround, and there's a comment in the above link saying just this: https://github.com/anthropics/claude-code/issues/6235#issuec... ) It's a hassle having to add it to every repo that I use Claude with though, and I often use other models and harnesses too for the more trivial tasks.

I beg people to learn what symlinks are. The fact that "put @AGENTS.md in there" is a "common workaround" shows why programmers (good ones at least) are not going anywhere soon.

[deleted]

Re: Codex logging bug may write TBs to local SSDs

#207

Post by milkshakes »

redox99 wrote: post #173
christophilus wrote: post #112

Well, everyone's bashing on OpenAI as well they should, but just a reminder, unlike Claude Code, Codex is officially available to customize here: https://github.com/openai/codex It's fairly easy to patch.

That's the CLI, not the codex app which is proprietary.

the issue is in the cli and app-server

Re: Codex logging bug may write TBs to local SSDs

#208

Post by fortuitous-frog »

troupo wrote: post #192
ValentineC wrote: post #133

Earlier quoted context omitted.

My CLAUDE.md is just: @AGENTS.md And Claude processes it just fine. (I see that it's a common workaround, and there's a comment in the above link saying just this: https://github.com/anthropics/claude-code/issues/6235#issuec... ) It's a hassle having to add it to every repo that I use Claude with though, and I often use other models and harnesses too for the more trivial tasks.

I beg people to learn what symlinks are. The fact that "put @AGENTS.md in there" is a "common workaround" shows why programmers (good ones at least) are not going anywhere soon.

I used to use a symlink but was concerned that Claude might see the presence of an "AGENTS.md" file (in e.g, a "List Files" tool call output or from a direct `ls`), be curious and attempt to read it directly (not knowing that it's the same as the "CLAUDE.md" file auto-injected by the harness), and essentially double the token impact / context bloat. Indeed, I did some local experimentation and noticed this was the case, which is why I switched to the explicit "@AGENTS.md" approach.

So perhaps there's no need to be rude about it :)

Re: Codex logging bug may write TBs to local SSDs

#209

Post by dpkirchner »

troupo wrote: post #192
ValentineC wrote: post #133

Earlier quoted context omitted.

My CLAUDE.md is just: @AGENTS.md And Claude processes it just fine. (I see that it's a common workaround, and there's a comment in the above link saying just this: https://github.com/anthropics/claude-code/issues/6235#issuec... ) It's a hassle having to add it to every repo that I use Claude with though, and I often use other models and harnesses too for the more trivial tasks.

I beg people to learn what symlinks are. The fact that "put @AGENTS.md in there" is a "common workaround" shows why programmers (good ones at least) are not going anywhere soon.

I'm pretty sure some agent harnesses read both files when present, so this @ "aliasing" is more token efficient.

Re: Codex logging bug may write TBs to local SSDs

#210

Post by datsci_est_2015 »

thewebguyd wrote: post #183
igleria wrote: post #67

Earlier quoted context omitted.

This is the biggest elephant in the room I have seen in my decade+ career. At the same time, look how bad Apple is in software compared to its hardware... It's not an AI only problem, it's almost like software in general gets a free pass on being very unsafe or low quality because no one wants to face the same "profit reducing red tape" that civil engineers or similar face.

> same "profit reducing red tape" that civil engineers or similar face. I don't think we should ever head toward licensing/a credential body for software development, but I do think now is a good time to have discussions around liability for defective products. A good start would be to stop allowing companies to disclaim all warranties of fitness for a particular purpose in their EULAs. The joke of Microsoft Copilot…

> I don't think we should ever head toward licensing/a credential body for software development, but I do think now is a good time to have discussions around liability for defective products.

Liability is how a credential body would organically grow. It already exists in the security, compliance, and enterprise parts of the software world.

Post reply on HN