Live data from Hacker News

Codex logging bug may write TBs to local SSDs

github.com

101–110 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#101

I want to like codex, but the quality is just not very good, especially when compared to Claude. It used to work okay, but a while back they landed a major regression for an entire team of folks I work with. No response, no workaround. https://github.com/openai/codex/issues/23762

I don’t trust any agent to respect any boundaries. They might today. But tomorrow’s vibe coded slip update might break it in subtle ways.

My solution to this is to only run agents in a sandbox of my own making (a locked down Podman container).

Re: Codex logging bug may write TBs to local SSDs

#102
post #41
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…

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

Surprisingly Kiro is fine (I work at Amazon but not at all on the Kiro team). I prefer it to anything else I've tried (except Amazon Q Developer in IntelliJ, but it's now deprecated).

Re: Codex logging bug may write TBs to local SSDs

#104
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…

This software has been terrible for me. Burns tokens like crazy, and fails. Most times I try to use the browser plugin, it just says it can't use the plugin. When it does work, it takes minutes to click a button. Unusable workflow.

I ask to generate a png with an alpha channel. It can't. Instead, it outputs a chroma-keyed image, then generates a python script to remove chroma key (fails), then a js script (which also fails). Then my 5h allotment is up.

It's frustrating because if it worked as they advertise, it'd be an amazing tool.

Re: Codex logging bug may write TBs to local SSDs

#105
post #64
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"?

If the code churn is high the investment to refactoring etc is less beneficial than may be obvious. I don't remember the details but I heard in some podcast that the code base of Claude Code changes so fast that any piece of code won't be there for long..

Re: Codex logging bug may write TBs to local SSDs

#106
post #80

Same issue with Claude Code btw — it writes massive debug logs to ~/.claude/logs. Had to symlink it to a tmpfs to stop wearing out my SSD.

I don't see this. According to their docs, logs are no longer written: https://code.claude.com/docs/en/claude-directory

Re: Codex logging bug may write TBs to local SSDs

#107
post #44

Earlier quoted context omitted.

What are your thoughts on the SNR of the linked GitHub issue threads? Consider the volume of comments posted and the substance of each comment.

I read the first page and they were excellent. Each was clearly written by an experienced dev who knows how to substantiate their claims and propose an acceptable fix that could just be merged. Your comment, on the other hand, would be improved by including your own opinion on the matter.

> Each was clearly written by an experienced dev

/s?

They're clearly AI generated

Re: Codex logging bug may write TBs to local SSDs

#108
post #36

Earlier quoted context omitted.

Yeah. Here I am sitting on a major incident at our company because someone’s vibe coded shit went seriously wrong.

Can you talk more in detail if possible and are allowed to do so? I do know one instance of someone literally losing a job because they vibe-coded their way to prod. Their response/justification was: "The code wasn't written by me. It was written by Claude/Chatgpt" They hadn't done anything to the database itself but you betcha that there are some horror stories involving database, lack of proper backups and Vibe-cod…

> "The code wasn't written by me. It was written by Claude/Chatgpt"

That seems like a good way to justify your own job away.

Re: Codex logging bug may write TBs to local SSDs

#109
post #57

Earlier quoted context omitted.

Not only Codex, but I can't leave ChatGPT app in macOS open for few hours, because it will consume 60 gigabytes of RAM over time and crashes all the apps. Mindboggling. Or can't use Google's AI Studio in browser because it takes 100% CPU. Need to write own app for everything???

the damn chat.openai.com webapp lags a lot as well on long chats, typing takes so long.

In my experience the input field lags on short chats too, sometimes in the middle of writing the second or third prompt. Are they running some kind of prospective evaluation or something?

Re: Codex logging bug may write TBs to local SSDs

#110
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…

Claude code (desktop) and Codex (desktop) are both absolutely dogshit pieces of software. I can't pick which one is worse. I'd be sort of ashamed to say I actively worked on them, regardless of how they can empower people. Cursor's new UI is similarly terrible. They're all slowly getting better, but too slow for my taste.

They are incredibly slow in unpredictable ways, eat up memory at an insane rate, and just feel like they were built with no regards for UX. Like they crammed together all the engineers with no idea of how to build a coherent and predictable UI and let them loose on the product without proper designers.

The other day Codex (desktop) was eating up 70GB of RAM on my machine. What had I done? Literally nothing. I opened it and let it update once.

Another one with Codex was when I had a specific conversation where no activity was happening and which would make the app spin up all of my CPU cores, rendering it barely usable. It would take seconds to react to anything or update the UI. The conversation wasn't even in focus!!! Restarting the app wouldn't help. After I archived it, it suddenly got better

Claude Code Desktop used to be so, soo, soo slow and eat up so much RAM. It was unusable for anything other than playing around when I first tried it. It also didn't communicate any of what it would do. Using it was like living in a world with no affordances, constantly afraid of interacting with them and being faced with some sort of destructive action. Still, it has definitely been improving in terms of the UI experience.

Cursor's new agents mode suffers from similar issues. Obscenely slow, hogging CPU without anything going on, breaking with existing UX patterns (some of them already well implemented in their other, more polished, previous version), confusing buttons and labels which don't explain what to do and that sometimes do destructive operations on your code.

My favorite cursor absurdity is that if you use their workflow to create a worktree and the worktree setup script fails, the following happens:

1. The agent has no idea that it failed, let alone have any logs of the failure

2. Often you yourself don't get access to the logs of what failed in that script. Don't ask me, half the time it just says it failed with no further logs.

3. When you do get the logs, you cannot copy them in ANY way. You can't even select them. I have had to resort to taking a screenshot to do OCR on it

I've also had cursor repeatedly have concurrency/race condition bugs when creating multiple worktrees in parallel. I have 5 tasks, I spin them up all together so they can create 5 worktrees and they crash with random internal cursor errors. Wasn't the point of this abhorrent new UI you've stuffed me with to enable parallelism?

It's like people aren't even testing the shit they ship. Which I guess they aren't.

I'm a big believer in AI and think it is changing the world and will continue to do so, but I almost get offended at how bad these products for which I am paying (sometimes quite a lot!) are. There's "move fast and break stuff" and then there's "build crap to call stuff".

Post reply on HN