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

211–220 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#211

Post by newtwilly »

purpleidea wrote: post #63

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

Decent sandbox + sandbox override experience with pi coding agent... pi-sandbox uses the same sandbox tech that claude code uses, although it uses a fork that's a little behind, and I'm not sure exactly why it uses a fork.

You can install pi, then install pi-sandbox locked to the current version. Here it is described how pi-sandbox plus an additional extension allow you to have the experience where a sandbox is used, but you can fall back to unsandboxed with approval required. https://github.com/carderne/pi-sandbox/issues/50

Re: Codex logging bug may write TBs to local SSDs

#213

Post by Zenul_Abidin »

indiv0 wrote: post #14

This thread will become a typical "haha slop company made slop" but I've been bitten by a bug exactly like this before in a (pre-AI, artisan) OSS project. The maintainer there didn't properly account for DST when calculating last backup time, so the app started and never stopped writing/re-writing backups continuously. Perhaps the framing shouldn't be "haha slop" but rather why doesn't the AI write better quality sof…

I've been bitten by this bug for several days, to the point where I had had to write a script to delete the WAL so that my server would stop getting locked up from a lack of disk space from codex logging.

You can find it here: https://github.com/openai/codex/issues/28224#issuecomment-47...

I have been making noise about this bug for a week, so I'm glad to see this is blowing up on HN.

Re: Codex logging bug may write TBs to local SSDs

#214

Post by sethaurus »

anon373839 wrote: post #135
me551ah wrote: post #122

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

[flagged]

> Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.

https://news.ycombinator.com/newsguidelines.html

Re: Codex logging bug may write TBs to local SSDs

#215

Post by reducesuffering »

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

Claude Code has been out for just 1 year and has millions of users already, being a major contribution to roughly $40 billion in revenue. By any stretch it is one of the most extremely fast developed products driving the most important workflow for millions of people already.

"Why isn't literally everything about a product that came out a year ago with an extremely fast scaling userbase solved?" is what I hear.

The goalposts will keep moving until AGI is undeniable.

Re: Codex logging bug may write TBs to local SSDs

#216

Post by Zenul_Abidin »

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…

I have been wondering why my battery dies quickly when I have codex open, even in my tray

I only noticed the CPU spike with Process Explorer also in my tray.

Re: Codex logging bug may write TBs to local SSDs

#217

Post by Supermancho »

epistasis wrote: post #181
Supermancho wrote: post #168

Earlier quoted context omitted.

If Pi can't use my MCPs, it's too big a step backward. Is the common tooling: https://github.com/nicobailon/pi-mcp-adapter ?

I imagine the answer varies greatly but what use cases do people find for MCP over standard command line calls? The only time I use MCP is when I'm supposed to test that an MCP is working. Everything else is just incredibly clunky and ugly. For example, connecting to Linear to grab a ticket is far easier and cleaner to copy and paste the text rather than to have the agent call the MCP and look it up by ticket name. I…

I use a Godot MCP in addition to my Godot IDE and the Figma MCP

The Godot Engine API (100s of calls) is not worth memorizing and Figma is visual based, along with a complicated engine-specific serialization.

Much easier to ask an LLM to find out why one thing affects another or how to optimally generate a specific change by exploring those APIs. When the LLM eventually fails, to explain the available functions and triage a solution.

Re: Codex logging bug may write TBs to local SSDs

#218

Post by mannanj »

thewebguyd wrote: post #180
r_lee wrote: post #64

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

> shouldn't this "agentic AI revolution" have long solved this already? Daily reminder that Anthropic took over a year to fix the Claude Code terminal flickering issue despite proclaiming all over the internet that software development as a "solved problem." Apple forked over $250 Million in a class action over false advertising for Apple Intelligence. When do we start seeing the same for the misleading and outright…

As long as a majority of the people of the living class are gullible and naive and sick, entrained behavior from the institutions and media they are made to consume, they stop seeing the misleading and false claims. Or at least they myopically see it short enough to complain about it in an ineffective way, then continue to consume the next big lie or slop. Until something happens that channels that accumulated rage finally into a cause they feel makes things right (assuming they have not already died and the next generation has been groomed to fall for the rich man's trap) and those who's family and next generation is to continue the extraction and trickery hides behind an anonymous personality or system.

Re: Codex logging bug may write TBs to local SSDs

#219

Post by lijok »

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.

Good programmers know symlinks are not portable
Post reply on HN