Live data from Hacker News

Codex logging bug may write TBs to local SSDs

github.com

191–200 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#191
post #61
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…

To be fair with Codex, you can use any harness you want with it. Access is not gatekeeper by a crappy full of slop electron app. So just move to PI, or whatever. Claude on the contrary, forces all plan users to use their horrible app, which, if you ever dared to use cowork, only once, will run a 2GB VM on app start, no f's given. at all. Not justifying it. But if you use the official Codex app, thats on you. If you u…

Not being able to use my own harness on the subscription plan is my biggest gripe with Anthropic/Claude. For what I work on, I still get better results with Opus than I do with GPT5.5-codex, but damn do I hate that I either have to PAYG or I'm stuck using Claude Code.

Re: Codex logging bug may write TBs to local SSDs

#192

Earlier quoted context omitted.

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

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.

Re: Codex logging bug may write TBs to local SSDs

#193

Earlier quoted context omitted.

I created a Claude Code plugin to load AGENTS.md. Uses symlinks but it’s better than no support. https://github.com/hexsprite/claude-agents-md

Claude Code supports native imports: `@AGENTS.md`

You two realise that symlinks exist, right? That you need neither a "plugin" nor a "native import"?

Re: Codex logging bug may write TBs to local SSDs

#194
post #156

Earlier quoted context omitted.

It still boggles my mind that Anthropic would invent the MCP protocol but not fully implement it. Especially when fully implementing it (prompts, resources, tools) is easily done in harnesses that don’t ship with MCP but allow good extension / modification like Pi. Claude not being able to see its own usage or self invoke slash commands is also very frustrating.

> It still boggles my mind that Anthropic would invent the MCP protocol but not fully implement it. https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ > Do they just want to force you to keep busy reacting to their volleys, so you can’t move forward?

> ...Do they just want to force you to keep busy

Given functionally unlimited access to tokens with frontier models, there is really no "force you to keep busy"; it should just bake overnight. We're talking about a rather simple and well-defined specification; not something novel and complex.

Re: Codex logging bug may write TBs to local SSDs

#195
post #57
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…

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???

It's not just Google AI Studio, it's also Google proper. Just one search result page consumes gigabytes of RAM. How did this happen? I've switched to DDG and never looked back.

Re: Codex logging bug may write TBs to local SSDs

#196
post #148

Earlier quoted context omitted.

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...

I think they have more than one job, they have to balance new features with improving the software itself. And Anthropic has to balance investing resources into Claude Code vs on infra or other things. Not that I'm happy with the current state of things, in fact I'm quite sad that improvements in capacity to do things doesn't translate into better quality.

> they have to balance new features with improving the software itself.

What new features?

> And Anthropic has to balance investing resources into Claude Code vs on infra or other things.

It seems they are doing neither? Their vibe-coders boast everywhere that they no longer even work, but just endlessly prompt Claude Code in a loop. Perhaps that's why there's no polish? Perhaps that's why their spring post about Claude Code issues reads like "these are all issues that would take a junior programmer a day to test and fix before they ever reached production"? https://www.anthropic.com/engineering/april-23-postmortem

Re: Codex logging bug may write TBs to local SSDs

#198
post #192

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.

Symlinks are a pain if you're on Windows, I'd rather not bother with them.

Re: Codex logging bug may write TBs to local SSDs

#199
post #192

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.

Symlinks aren’t portable.

Re: Codex logging bug may write TBs to local SSDs

#200
post #192

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.

One bonus to this approach is that I can add Claude Code-specific stuff in there, that I wouldn't need for other harnesses.
Post reply on HN