Earlier quoted context omitted.
> I'm not exactly building TUI's every day, but even i felt pain when i read that "small game engine" post The bigger issue is they where somehow thinking it was "cool" and "advanced" while it's just a kludgy rube-goldbergy monstrous hack. Which is of course only semi-working: to me the model thinking what you see is what it outputs in the TUI is the deal-breaker for me. It's of course not working like that for they'…
Whats the small game engine post?
Codex logging bug may write TBs to local SSDs
121–130 of 296 posts
Re: Codex logging bug may write TBs to local SSDs
#122Codex 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
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
Re: Codex logging bug may write TBs to local SSDs
#123I think part of the question should be, why is there no QA or test that catches this? It's one thing to be slopware, but why didn't anything run a test that catches this?
Re: Codex logging bug may write TBs to local SSDs
#124Yikes. I have a habit of leaving sessions open for a long time. I just ran `sudo iotop` to watch live disk activity and sure enough all my idle codex sessions were spinning away writing god knows what constantly to disk.
Re: Codex logging bug may write TBs to local SSDs
#125Earlier quoted context omitted.
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"?
Like anything, you have to decide between polish vs switch to any other task in the queue. If you choose too much from the latter, then polish suffers, yet that's a human thing. Also, Codex and Claude Code aren't as bad as people say. I think most of the noise is embellished by the "hah see? AI sucks" angle. It's kind of like how HNers would claim to your face that you can't actually build anything with Javascript an…
>Like anything, you have to decide between polish vs switch to any other task in the queue
Why do you "have to decide"? Let some agents go at both of those, isn't that what they claim people can just do?
>Also, Codex and Claude Code aren't as bad as people say. I think most of the noise is embellished by the "hah see? AI sucks" angle.
Why shouldn't it? They're not the ones making the extraordinary claims.
Re: Codex logging bug may write TBs to local SSDs
#126Someone posted a temporary workaround for this on X[1]. sqlite3 ~/.codex/logs_2.sqlite "CREATE TRIGGER IF NOT EXISTS block_log_inserts BEFORE INSERT ON logs BEGIN SELECT RAISE(IGNORE); END;" Also, I found that running VACUUM FULL on the sqlite file on my laptop shrunk it from 27GB to a mere 73MB[2]. [1]: https://xcancel.com/bdsqlsz/status/2067964486615810369 [2]: https://xcancel.com/jeethu/status/2068087449469780434
The real solution is to stop using it and switch to Pi
I’ve been using oh-my-pi with GLM-5.2 xhigh as the main model and GPT-5.5 medium as its advisor model. IMO, the combo works better than either of those models alone.
Re: Codex logging bug may write TBs to local SSDs
#127Earlier quoted context omitted.
We've gone from "you're holding it wrong" to "the training data was bad because humans suck too". Difference is, humans learn from their mistakes.
> Difference is, humans learn from their mistakes. Great! So next time the human will prompt the agent to watch out for and avoid this bug.
> Great! So next time the human will prompt the agent to watch out for and avoid this bug.
I actually created a system for something like this. The basic idea is, once you have identified what the issue was and fixed it, you can create lessons that lives inside the repository. Lessons are designed to be mapped to one or more files so if the LLM changes the files again, they can see what the issue was.
The main challenge is being able to summarize and create proper tags so the AI after any code change can easily find the lesson.
Re: Codex logging bug may write TBs to local SSDs
#128Earlier quoted context omitted.
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?
When you are writing completely new prompt - it sends every character to server when writing and tries to make suggestions based on that. And keeps doing it in intervals in /prepare endpoint, during each prompt. So if you are working with something sensitive - don't write it to browser directly and edit it there.
But then why does it become dog slow when the chat becomes bigger?
Re: Codex logging bug may write TBs to local SSDs
#129Earlier quoted context omitted.
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..
In other words it's an ever moving vibe fest, with random bugs and misbehaviors each time they roll the dice...
Re: Codex logging bug may write TBs to local SSDs
#130Earlier quoted context omitted.
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"?
A simple explanation is that they are "good enough" for most people and they have better things to do. Even if tomorrow I was 100 times as productive, I still wouldn't have time to do literally everything and I would have to prioritize.
You might not.
But the Claude Code team has ONE job.
And they have full access to a platform that they advertise as "humanity-threat" level good, and claim that it can automate everything code related...