25 ms·

Codex logging bug may write TBs to local SSDs

510 points by vantareed 3mo ago

joka88xj 3mo ago
[flagged]
bravetraveler 3mo ago
Somebody please donate some tokens to this plucky startup, they need our help.
neuralkoi 3mo ago
Vibe coding takes "move fast and break things" to a whole nother level.
- cryo32 3mo ago
  Yeah. Here I am sitting on a major incident at our company because someone’s vibe coded shit went seriously wrong.
  - Imustaskforhelp 3mo ago
    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-coding gone insanely wrong.
    - cryo32 3mo ago
      I can say very little in detail but basically Claude doesn’t have any conceptual idea of order of operations and transactional guarantees which resulted in producing something that failed under normal load. There is an evidence chain to suggest it was asked to do this but did not and that wasn’t verified. Our engineers are accountable for what they produce regardless of how so they are cleaning up the extensive mess this made. This will result in a very heated post-mortem meeting between the two factions in the company.
    - latexr 3mo ago
      > Their response/justification was: "The code wasn't written by me. It was written by Claude/Chatgpt" It boggles the mind someone could think that is a valid justification, because ultimately what they’re saying is “I’m useless, what you get from me is the same thing as prompting the model” which still means they would lose their job.
    - flir 3mo ago
      > "The code wasn't written by me. It was written by Claude/Chatgpt" Culturally (across all LLM use, not just programming) we need to nip that in the bud. If we don't it's going to be the new "someone hacked my social media password" get out of jail free card for avoiding responsibility. I don't care what tools you used, but if your name is on it, you're the author and the responsibility is yours. No "it wasn't me it was my typewriter" bullshit.
      - Imustaskforhelp 3mo ago
        (Although I was a bit para-phrasing as I don't remember the exact story but something similar was definitely said. I agree and I feel that that company in particular's response to that statement was also the same in terms of: you are responsible for your code no matter what and prompted to fire the engineer. but there was also this dual level of hypocrisy from the company as well, in terms of asking the engineers to be 10x'd and putting pressures on it and internal lying by teams on how much productive they really are with AI and many other things in general. I feel like engineers are within pressure of being asked to replace themselves within some (IMO) toxic workplaces by having the expectations of being 10x'd, something which previously was just an hyperbole but is now being expected as reality. As much as I'd like to place the fault on that engineer isolated itself which in some sense you can consider that. I also think of it as a probability of a person like that existing. Within the hyperfocused hyper-growth mentality without much safe-guards AI 10x agentic intent focused engineers (I have exhausted my AI vocabulary), the chances of a person like that existing simply rises magnitudes more which could probably be why I heard of a story like that in first place. This might be one of the reasons I am worried about the hyper-focus on using AI as an everything tool or the investor/company focus on using AI for everything. I have said it elsewhere and I might say it again but if we treat AI as a hammer, then we need to stop treating everything as a screw and forcing/dog-feeding AI inside it, we need to treat a screw as a screw otherwise we will probably end up with some very messy foundations. I would agree on you to have a cultural annotation on this being bad but unless we also add a cultural annotation on the last thing that I mentioned, I find it very hard to be achievable but I suppose that the last thing is what the AI companies and everyone is betting trillions of dollars on, on AI being used for everything and anything and I find it hard for the culture to be expected to change from top-down manner especially when its inverted and managers expect you to build things with AI given the investment. There should be a balance and push-back from engineers alike, but as mitchell has said, even some really smart engineers who should know better are completely within AI psychosis and the philosophy of using AI as a hammer and hammering everything. As such I would find it hard to create a cultural disturbance. Would you like to know the disturbing part? When someone who worked at that company was honest and told higher-ups that they weren't being 10x'd by AI while all other engineers said that they were (they were in fact lying and working till 1 AM to finish the work as AI was ineffective). The management just treats this honest employee as the one ineffective and it has created a bit semi-toxic workplace for them. Imagine asking for cultural disturbance if everyone involved from top to bottom is involved in covering up for AI, because investors want to jump in on AI, and companies want that sweet investor money and management wants to satisfy the company and engineers want to keep their job and keep management happy and honest people get punished for being honest. This got a bit long but this is everything wrong with AI. Not really the tech but rather everything around it. I hope the culture around things get better but its an uphill battle. on the other hand of things, I am optimistic because it seems that honesty would matter more when the bubble pops and everyone would become hopefully more selective on complete AI consumption or more intentional around it. (I am happy with developers building tools and prototypes that they previously couldn't have and even monetizing it somewhat, but just being honest and also more than capable of switching from slopware sunk costs. TLDR: being authentic/transparent.)
    - smoe 3mo ago
      > "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.
    - ValentineC 3mo ago
      > 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" People like that and their managers should all be put on PIP right away. It's not like there is a lack of talent on the market.
      - LtWorf 3mo ago
        Say in an interview that you are sceptical of ai and you won't get the job.
  - al_borland 3mo ago
    I hope that ends up in the RCA, to show these tools as a real risk, and not swept under the rug, where all blame is shifted elsewhere.
    - cryo32 3mo ago
      It'll go under the rug as it always does because no one wants to explain that our AI first strategy was a stupid one that caused a net negative ROI impact and reputational damage.
- comboy 3mo ago
  We are running out of things to break.
  - stavros 3mo ago
    Make more things to break.
- GL26 3mo ago
  as long as you don't have technical debt, vibe coding is mostly useful for prototyping. For a real product, true SWE will never be replaced
  - Otek 3mo ago
    Already got replaced at world top tier tech jobs. „True SWE” will be niche / luxury soon, just like real woodworking vs IKEA
    - inigyou 3mo ago
      Software is freely duplicable unlike wood. IKEA could be mass producing copies of the most beautiful chair in the world just as easily as it produces copies of something a 5-year-old drew in freecad.
      - wafflemaker 3mo ago
        >something a 5-year-old drew in freecad Ikea series of plush toys based on children drawings were actually very cool. Not drawn in frecad though, just plain old crayons on paper. https://digitalsynopsis.com/advertising/ikea-childrens-drawings-soft-toys-education/ https://digitalsynopsis.com/advertising/ikea-childrens-drawi...
    - slopinthebag 3mo ago
      Source that a big tech company replaced all their SWEs with vibe coders?
  - throwatdem12311 3mo ago
    all code is technical debt
vantareed 3mo ago
[flagged]
consp 3mo ago
Why didn't the review process spot this obvious error? Oh wait ... @codex review this
- deleted 3mo ago
  [deleted]
- charcircuit 3mo ago
  Because it's not an error. The software is working as the creators intended. The diagnostic data (trace logs) are intentionally being saved for debug purposes.
  - anematode 3mo ago
    What?
    - charcircuit 3mo ago
      Someone choosing different tradeoffs is not them making an error.
      - anematode 3mo ago
        It's obviously an error, but I'm going to assume you are larping and move on
        charcircuit 3mo ago
        What is the error? I explained how it is not an error and your are giving vague responses.
- cedws 3mo ago
  Moreover why isn't the bug fixed already? I thought programmers were obsolete now. Surely one of the leading AI labs has figured out full automation of software development end-to-end by now if that's so.
Imustaskforhelp 3mo ago
I don't understand how Codex can blunder so badly. I imagine that even if they would be using vibe-coding, surely they must have some good engineers. So why is there such severe bugs? One can argue that these products are the flagship products of their respective AI companies aside from the AI models themselves of course. I imagine that this story will be picked up by the news left and right, some stories just feel this way and this one is like that (given 12 upvotes on HN in 7 minutes) The only logical conclusion (from this incident) that I can have is: An (vibe-coded?) product is hard to maintain even for some of the best engineers and is bound to have severe bugs. 2. Proper testing and taking issues seriously is the key if you still wish to do this and there isn't much. This is a week old issue which I can only classify as severe. I wish to keep an nuanced opinion about it but oh this is bad for openAI (not as bad as them accepting autonomous AI within drones and mass surveillance though) My point is: AI has both uphills and downward valleys and cliffs. It might as well just accelerate you, which could be, towards your downfall as well. Its recommended to keep an eye while driving and not drive too fast. AI companies might be like car companies which don't offer a brake pedal.
- PunchyHamster 3mo ago
  > I don't understand how Codex can blunder so badly. I imagine that even if they would be using vibe-coding, surely they must have some good engineers. So why is there such severe bugs? Because it was deemed not Hard Enough task for real engineer to look at, so AI was sent to do it with no supervision, just checking the effects. Also overly excessive logging is probably useful to them in chasing some of the edge cases, the cost to users doesn't matter in the slightest to them
- supriyo-biswas 3mo ago
  The truth of the matter is that any time that has been saved in writing the code must be spent on ensuring proper system design, reviewing the code, and most importantly of all, QA, which is an uncomfortable discussion for AI techbros who are peddling complete automation of the software profession.
- dathinab 3mo ago
  > I don't understand how Codex can blunder so badly. because they trust the AI too much (and seem to be fin with acting knowingly negligent) the problem is - AI tends to produces very convincing looking code, even if fully wrong - AI does mistakes of kinds no human would do, at least no human who is also able to write convincing looking code - code reviews are hard, a lot of devs, including senior devs, put a lot of implicit trust into the co-worker behaving "sane and non malicious". But AIs behave sometimes not so sane and in a way (wrt. trying to be convincing). In the worst case in ways which if it where a human you might consider to be them trying malicious sabotage the product Like a "dump" example from work: - AI randomly removes a HTML element id while doing other changes in jsx/react - the PR has a lot of changes, the id removal line looks innocent, like some on the fly cleanup - human reviewers have the bad tendency to often not look too much at deleted lines, only if they need reference to how a new line was before (but it's only a deleted line and no new line) - you don't expect humans to randomly without reason delete important properties of components when changing other things - you maybe would still have found it, but it's a emergency fix for a production issue - it happens to miss integration tests, but happens to still matter a lot for one specific important for complicated reasons not properly tested flow (similar people tend to not test logging too much, at best the presence of needed info but hardly ever the absence of noise)
ramon156 3mo ago
Blegh, I puke every time I see obviously AI generated comments in GH PR's. You cannot assume any of these people have done their research, other than telling Codex to do it for them
- b--l 3mo ago
  It's because they use gpt-5.5-xhigh (the money making* model) to build it. (*for them)
- deleted 3mo ago
  [deleted]
b--l 3mo ago
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 the release of vibe coded junk. I would literally fix it myself but it's closed source for whatever reason. There are many discussions about which model is better, or if vibe coding is even possible. I point you to the extent of what one of the most well funded, money flush, well staffed model making companies can do with vibe coding. To me a screwup this bad (where the CEO has already made it clear they're now "focussing on coding") indicates that there's something truly broken in the company. No one on polymarket expects them to have a leading model any time soon for example. It's a tragedy. The world needs competition to anthropic.
- l33tman 3mo ago
  This was fixed long ago, if I'm thinking of the same bug. It was stuck in an inf loop all the time the codex window was open.
  - cncjvu7 3mo ago
    Nah it's still doing weird shit. Uninstalled that crapware last week.
- jofzar 3mo ago
  > Codex is one of the most infamous examples of slopware Woah, let's not forget Claude code is right there
  - mvATM99 3mo ago
    Yeah exactly. I'm not exactly building TUI's every day, but even i felt pain when i read that "small game engine" post
    - 3mo ago
dundercoder 3mo ago
If something like this is helpful or necessary, that’s what ram backed tmpfs is for.
- mrweasel 3mo ago
  Using a RAM backed tmpfs would be a work-around as to not trash your SSD. It's doesn't fix underlying problem. It's incredibly poor design on OpenAIs part.
ares623 3mo ago
i hope they find the smoking gun, the key insight, the kicker.
- 59nadir 3mo ago
  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.
  - jofzar 3mo ago
    Ugh this one's gets me so bad, same with "wire" and "wired" everything is wired to something.
    - never_inline 3mo ago
      that's a real gap
      - anematode 3mo ago
        The honest answer:
- wrxd 3mo ago
  At least they could call someone who’s is absolutely right so that the tool can see its mistakes now
indiv0 3mo ago
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 software than we do? To which the answer is obvious IMO -- even emergent properties can't elevate AI intelligence too far above the training dataset. So how do we get to superintelligent (or at least "not-wreck-your-NVMe-endurance-telligent") AI, if we, as a whole, are not smart enough ourselves? Judge not the slop-bot, lest ye be judged yourself, engineer.
- applfanboysbgon 3mo ago
  1. I bet that developer only made that mistake one time in their life. Humans learn from their mistakes, LLMs don't. If you rely on LLMs to generate all of your code, you can expect to run into the same issues again and again. 2. "One developer somewhere in the world made a bad mistake one time, so this represents the quality of all software devs everywhere". Maybe they were just a bad developer? Bad developers exist. I have never written a bug that has destroyed my users' hardware, and I think that writing such a bug is completely inexcusable in an enterprise environment with software that will be shipped to millions of users, as Codex is.
  - lifthrasiir 3mo ago
    > I have never written a bug that has destroyed my users' hardware, ... Probably whoever (human or agent) originally decided to put TRACE logs into SQLite also thought---or reasoned---so. Maybe the decision was right at that time but the amount of TRACE logs have increased enormously. You will never know.
    - applfanboysbgon 3mo ago
      I love that we've moved the goalposts from "LLMs are better than artisanal software engineers" to "actually, shipping hardware-destroying bugs in production is literally unavoidable, nobody could possibly avoid doing it".
woadwarrior01 3mo ago
Someone 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 https://xcancel.com/bdsqlsz/status/2067964486615810369 [2]: https://xcancel.com/jeethu/status/2068087449469780434 https://xcancel.com/jeethu/status/2068087449469780434
- NamlchakKhandro 3mo ago
  The real solution is to stop using it and switch to Pi
  - woadwarrior01 3mo ago
    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.
  - deleted 3mo ago
    [deleted]
- sgarland 3mo ago
  DB-level rules saving the day once again.
rvz 3mo ago
The first of many bugs that are beyond the complexity of its authors, thanks to comprehension debt. Even with tests, the more complex the code base is, the more risky it is to vibe-code on it without introducing more bugs [0] and increasing the debt. Does not matter if the CI is green or if all the tests pass. It gets even worse if you can't explain the change / pull request or what the implications are after applying that "suggested" fix. [0] https://sketch.dev/blog/our-first-outage-from-llm-written-code https://sketch.dev/blog/our-first-outage-from-llm-written-co...
- HPsquared 3mo ago
  There are going to be sooooo many consulting opportunities after this wave.
  - deleted 3mo ago
    [deleted]
deleted 3mo ago
[deleted]
bob1029 3mo ago
I'm struggling with how this much logging information could be generated at any level of verbosity. Is codex writing log entries while it's sitting idle? Why would someone want to look at these logs?
hun3 3mo ago
The operating system has historically trusted the applications not to do dumb things too much. Only now we're witnessing the consequences much more frequently thanks to accelerated slop.
- skydhash 3mo ago
  > The operating system has historically trusted the applications not to do dumb things too much. The OS is a thin layer providing an abstract and consistent interface regardless of the hardware configuration. Policing applications is mostly related to security and resources utilization, not moronic errors.
  - hun3 3mo ago
    > The OS is a thin layer providing an abstract and consistent interface regardless of the hardware configuration. This is called a hardware abstraction layer, not OS. https://en.wikipedia.org/wiki/Hardware_abstraction https://en.wikipedia.org/wiki/Hardware_abstraction
i2km 3mo ago
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...
- drakythe 3mo ago
  They're pretty bad about fixing issues it seems. My favorite is #2472 which they demonstrated "fixing" on stage on the release of GPT 5, but the ticket is still open and the "fix" hasn't been merged. The original blog that flagged this fact https://blog.tymscar.com/posts/openaiunmergeddemo/ https://blog.tymscar.com/posts/openaiunmergeddemo/ and the issue: https://github.com/openai/openai-python/issues/2472 https://github.com/openai/openai-python/issues/2472
  - lelandfe 3mo ago
    Claude meanwhile just auto closes all issues because they simply don’t triage ~anything. There’s been countless instances of this horrifying issue created for over a year now: https://github.com/anthropics/claude-code/issues/16180 https://github.com/anthropics/claude-code/issues/16180 > Permission bypass when commands are chained with && At one point they fixed their auto stale bot closing bugs but, hey, guess that wasn’t long lived.
- cl3misch 3mo ago
  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.
taosu_la 3mo ago
Can someone tell me if the current sub-agent of codex is available now? There used to always be a spinning issue.
jofzar 3mo ago
This is actually such a classic blunder (shipping trace/debug logging on for everything), but funnily the impact is not in a normal way. It's crazy we have hit a point where memory, CPU speed and disk speed isn't getting clapped because a Dev shipped logging at trace level instead of what used to the application being catastrophically slow so its immediately fixed in the next update.
- kuekacang 3mo ago
  It helps too that agent work is done server side so you can hog all the local resources for your thin client.
abihordun 3mo ago
[flagged]
purpleidea 3mo ago
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 https://github.com/openai/codex/issues/23762
- christophilus 3mo ago
  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).
  - matheusmoreira 3mo ago
    I went the full virtual machine route. Just finished hardening the setup and firewalling it off my local network. Not perfect but it does make me feel much safer.
  - drakythe 3mo ago
    They can't respect boundaries as long as those boundaries exist only in the LLM instruction set. A human being who follows rules long enough the rules will become second nature (usually), almost to the point where long running companies are known for having rules no one understands (Chesterton's Fence is alive and well). But an LLM have a limited "memory" and while the instructions might land in there and be of sufficient priority to be "respected" a single instance of that memory getting too full or the LLM autocompleting the work around because that was the statistical "best" solution and any barriers that exist only in LLM instructions and not in hardcoded guards will evaporate like so much morning fog.
- newtwilly 3mo ago
  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 https://github.com/carderne/pi-sandbox/issues/50
taspeotis 3mo ago
OpenAI really snatched defeat from the jaws of victory late last year when Claude Code was a laggy mess. Nowadays Codex has typing latency out of the gate, whereas Claude Code has the odd pause but generally displays my key presses as … you know … I press them.
- kasey_junk 3mo ago
  Fwiw I have the exact opposite experience.
- christophilus 3mo ago
  I find Claude Code nearly unusable. I always have to type in neovim if I’m typing anything more than a few words.
  - aquariusDue 3mo ago
    It runs fine for me on an old ThinkPad X220 loaded with 8 GB, an i5 and a barely working SATA SSD. This is on Fedora and Claude Code is installed from Anthropic's dnf repo (the latest channel). Granted I'm on the Pro Plan and I'm not running lots of sub agents but the default terminal app from KDE (Konsole) renders and keeps Claude Code responsive enough. I must be honestly missing some key piece of workflow otherwise I don't know why it would run so slow for other people on better hardware? Granted I'm taking care to tell Claude to not exhaust CPU cores and make sure to not trigger OOM errors, akin to "make no mistakes pls".
- Lionga 3mo ago
  [dead]
deleted 3mo ago
[deleted]
xfgong 3mo ago
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.
- eddyfromtheblok 3mo ago
  I don't see this. According to their docs, logs are no longer written: https://code.claude.com/docs/en/claude-directory https://code.claude.com/docs/en/claude-directory
sigbottle 3mo ago
I have noticed absurd lag from the browser usage and sometimes complete bricking of my network too on my computer. I thought it was just my computer getting old, but possibly it's ChatGPT.
deleted 3mo ago
[deleted]
christophilus 3mo ago
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 https://github.com/openai/codex It's fairly easy to patch.
- Lionga 3mo ago
  [dead]
- redox99 3mo ago
  That's the CLI, not the codex app which is proprietary.
  - milkshakes 3mo ago
    the issue is in the cli and app-server
altcognito 3mo ago
I 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?
- theowaway213456 3mo ago
  Every time you write a test that handles some data, you write an assertion about how much data is handled? Come on, this is such an easy thing to forget to test. Don't act like there is some magical testing strategy that would have caught this
  - altcognito 3mo ago
    I'll acknowledge that this is probably not likely to get caught. Integration testing could/should catch this, especially for a client side app. A simple constraints is a good thing. "Our app shouldn't use more than 50mb of ram, or use 3gb of disk space."
    - cute_boi 3mo ago
      load testing definitely should have caught this issue.
  - tomjakubowski 3mo ago
    The most likely way I think you'd catch this in a test would be by accident, running some kind of long-running integration test for other purposes, and then finding the disk gets filled up in CI (or on a developer machine).
- java-man 3mo ago
  what QA?
  - cute_boi 3mo ago
    Quality assurance testing....
whalesalad 3mo ago
Yikes. 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.
akitowerns 3mo ago
[flagged]
joelthelion 3mo ago
A good moment to switch to an open solution like opencode or pi.
ewsbr 3mo ago
Looks like this was fixed[0], so it should land in the next release. [0] https://github.com/openai/codex/commit/e98d43ac372ddf7f513c0e30c56dd8dc35ea5404 https://github.com/openai/codex/commit/e98d43ac372ddf7f513c0...
tgtweak 3mo ago
Slightly better than the claude code "feature" that deletes all your session context and transcripts older than 30 days old.
- qup 3mo ago
  At least that's a decision vs a bug.
  - tgtweak 3mo ago
    Not a decision that users are aware of though. Nor is there a setting to disable/change it. It just showed up one day and erased your previous sessions.
    - pdantix 3mo ago
      > Nor is there a setting to disable/change it. https://code.claude.com/docs/en/settings#available-settings https://code.claude.com/docs/en/settings#available-settings `cleanupPeriodDays` has always existed.
- Mistredo 3mo ago
  Codex has a similiar bug and makes chats disappear randomly.
collabs 3mo ago
I feel vindicated in my admittedly seemingly masochistic ritual of copy pasting code from the web browser to visual studio code even though I don't always pore over every line.
collabs 3mo ago
This is a little off topic but These guys really need to stop polluting the root folder of repo with Claude dot MD and copilot dot MD. Get in a room together and decide on a well known folder structure like docs/llm/*
g42gregory 3mo ago
I wonder if this falls into a "coding is solved" category? I start getting good results with Oh-My-Pi and Pi Coding Agents.
jackbucks 3mo ago
HAHAHAHAHAHAHA
linzhangrun 3mo ago
Considering the current storage prices and the SSDs whose lifespan you would thus exhaust...
fc-oai 3mo ago
Hey everyone, I'm an engineer at OpenAI. Thanks for the discussion here. Just wanted to report that a fix for this issue has been published in an update to the CLI and Codex App.
- tdehnke 3mo ago
  Looks like the fix doesn't work for all users from the comments on Github, please verify.
robeym 3mo ago
I'm on 0.139.0 on Linux and my visible ~/.codex/logs are only about 129 MB. This makes me even more conservative on upgrading these tools every time they prompt me to. Better to let them get a few miles on them and see how the community responds. In this case it sounds like 0.142.0 reduced the issue but didn't fully settle it. I'll wait for 0.143.0+ and see if that version is more acceptable.
MajorLettuce 3mo ago
Ironically now it seems that the companies that make these companies are the only ones to profit from slop software. There is no other reason for this to happen other than that the people responsible didn’t take care to check the code they are pushing. Which should be a signal in itself but I suppose it doesn’t matter if it is “good enough.”

510 points by vantareed 3mo ago

joka88xj 3mo ago

[flagged]

bravetraveler 3mo ago

Somebody please donate some tokens to this plucky startup, they need our help.

neuralkoi 3mo ago

Vibe coding takes "move fast and break things" to a whole nother level.

cryo32 3mo ago
Yeah. Here I am sitting on a major incident at our company because someone’s vibe coded shit went seriously wrong.
- Imustaskforhelp 3mo ago
  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-coding gone insanely wrong.
  - cryo32 3mo ago
    I can say very little in detail but basically Claude doesn’t have any conceptual idea of order of operations and transactional guarantees which resulted in producing something that failed under normal load. There is an evidence chain to suggest it was asked to do this but did not and that wasn’t verified. Our engineers are accountable for what they produce regardless of how so they are cleaning up the extensive mess this made. This will result in a very heated post-mortem meeting between the two factions in the company.
  - latexr 3mo ago
    > Their response/justification was: "The code wasn't written by me. It was written by Claude/Chatgpt" It boggles the mind someone could think that is a valid justification, because ultimately what they’re saying is “I’m useless, what you get from me is the same thing as prompting the model” which still means they would lose their job.
  - flir 3mo ago
    > "The code wasn't written by me. It was written by Claude/Chatgpt" Culturally (across all LLM use, not just programming) we need to nip that in the bud. If we don't it's going to be the new "someone hacked my social media password" get out of jail free card for avoiding responsibility. I don't care what tools you used, but if your name is on it, you're the author and the responsibility is yours. No "it wasn't me it was my typewriter" bullshit.
    - Imustaskforhelp 3mo ago
      (Although I was a bit para-phrasing as I don't remember the exact story but something similar was definitely said. I agree and I feel that that company in particular's response to that statement was also the same in terms of: you are responsible for your code no matter what and prompted to fire the engineer. but there was also this dual level of hypocrisy from the company as well, in terms of asking the engineers to be 10x'd and putting pressures on it and internal lying by teams on how much productive they really are with AI and many other things in general. I feel like engineers are within pressure of being asked to replace themselves within some (IMO) toxic workplaces by having the expectations of being 10x'd, something which previously was just an hyperbole but is now being expected as reality. As much as I'd like to place the fault on that engineer isolated itself which in some sense you can consider that. I also think of it as a probability of a person like that existing. Within the hyperfocused hyper-growth mentality without much safe-guards AI 10x agentic intent focused engineers (I have exhausted my AI vocabulary), the chances of a person like that existing simply rises magnitudes more which could probably be why I heard of a story like that in first place. This might be one of the reasons I am worried about the hyper-focus on using AI as an everything tool or the investor/company focus on using AI for everything. I have said it elsewhere and I might say it again but if we treat AI as a hammer, then we need to stop treating everything as a screw and forcing/dog-feeding AI inside it, we need to treat a screw as a screw otherwise we will probably end up with some very messy foundations. I would agree on you to have a cultural annotation on this being bad but unless we also add a cultural annotation on the last thing that I mentioned, I find it very hard to be achievable but I suppose that the last thing is what the AI companies and everyone is betting trillions of dollars on, on AI being used for everything and anything and I find it hard for the culture to be expected to change from top-down manner especially when its inverted and managers expect you to build things with AI given the investment. There should be a balance and push-back from engineers alike, but as mitchell has said, even some really smart engineers who should know better are completely within AI psychosis and the philosophy of using AI as a hammer and hammering everything. As such I would find it hard to create a cultural disturbance. Would you like to know the disturbing part? When someone who worked at that company was honest and told higher-ups that they weren't being 10x'd by AI while all other engineers said that they were (they were in fact lying and working till 1 AM to finish the work as AI was ineffective). The management just treats this honest employee as the one ineffective and it has created a bit semi-toxic workplace for them. Imagine asking for cultural disturbance if everyone involved from top to bottom is involved in covering up for AI, because investors want to jump in on AI, and companies want that sweet investor money and management wants to satisfy the company and engineers want to keep their job and keep management happy and honest people get punished for being honest. This got a bit long but this is everything wrong with AI. Not really the tech but rather everything around it. I hope the culture around things get better but its an uphill battle. on the other hand of things, I am optimistic because it seems that honesty would matter more when the bubble pops and everyone would become hopefully more selective on complete AI consumption or more intentional around it. (I am happy with developers building tools and prototypes that they previously couldn't have and even monetizing it somewhat, but just being honest and also more than capable of switching from slopware sunk costs. TLDR: being authentic/transparent.)
  - smoe 3mo ago
    > "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.
  - ValentineC 3mo ago
    > 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" People like that and their managers should all be put on PIP right away. It's not like there is a lack of talent on the market.
    - LtWorf 3mo ago
      Say in an interview that you are sceptical of ai and you won't get the job.
- al_borland 3mo ago
  I hope that ends up in the RCA, to show these tools as a real risk, and not swept under the rug, where all blame is shifted elsewhere.
  - cryo32 3mo ago
    It'll go under the rug as it always does because no one wants to explain that our AI first strategy was a stupid one that caused a net negative ROI impact and reputational damage.
comboy 3mo ago
We are running out of things to break.
- stavros 3mo ago
  Make more things to break.
GL26 3mo ago
as long as you don't have technical debt, vibe coding is mostly useful for prototyping. For a real product, true SWE will never be replaced
- Otek 3mo ago
  Already got replaced at world top tier tech jobs. „True SWE” will be niche / luxury soon, just like real woodworking vs IKEA
  - inigyou 3mo ago
    Software is freely duplicable unlike wood. IKEA could be mass producing copies of the most beautiful chair in the world just as easily as it produces copies of something a 5-year-old drew in freecad.
    - wafflemaker 3mo ago
      >something a 5-year-old drew in freecad Ikea series of plush toys based on children drawings were actually very cool. Not drawn in frecad though, just plain old crayons on paper. https://digitalsynopsis.com/advertising/ikea-childrens-drawings-soft-toys-education/ https://digitalsynopsis.com/advertising/ikea-childrens-drawi...
  - slopinthebag 3mo ago
    Source that a big tech company replaced all their SWEs with vibe coders?
- throwatdem12311 3mo ago
  all code is technical debt

vantareed 3mo ago

[flagged]

consp 3mo ago

Why didn't the review process spot this obvious error? Oh wait ... @codex review this

deleted 3mo ago
[deleted]
charcircuit 3mo ago
Because it's not an error. The software is working as the creators intended. The diagnostic data (trace logs) are intentionally being saved for debug purposes.
- anematode 3mo ago
  What?
  - charcircuit 3mo ago
    Someone choosing different tradeoffs is not them making an error.
    - anematode 3mo ago
      It's obviously an error, but I'm going to assume you are larping and move on
      - charcircuit 3mo ago
        What is the error? I explained how it is not an error and your are giving vague responses.
cedws 3mo ago
Moreover why isn't the bug fixed already? I thought programmers were obsolete now. Surely one of the leading AI labs has figured out full automation of software development end-to-end by now if that's so.

Imustaskforhelp 3mo ago

I don't understand how Codex can blunder so badly. I imagine that even if they would be using vibe-coding, surely they must have some good engineers. So why is there such severe bugs? One can argue that these products are the flagship products of their respective AI companies aside from the AI models themselves of course. I imagine that this story will be picked up by the news left and right, some stories just feel this way and this one is like that (given 12 upvotes on HN in 7 minutes) The only logical conclusion (from this incident) that I can have is: An (vibe-coded?) product is hard to maintain even for some of the best engineers and is bound to have severe bugs. 2. Proper testing and taking issues seriously is the key if you still wish to do this and there isn't much. This is a week old issue which I can only classify as severe. I wish to keep an nuanced opinion about it but oh this is bad for openAI (not as bad as them accepting autonomous AI within drones and mass surveillance though) My point is: AI has both uphills and downward valleys and cliffs. It might as well just accelerate you, which could be, towards your downfall as well. Its recommended to keep an eye while driving and not drive too fast. AI companies might be like car companies which don't offer a brake pedal.

PunchyHamster 3mo ago
> I don't understand how Codex can blunder so badly. I imagine that even if they would be using vibe-coding, surely they must have some good engineers. So why is there such severe bugs? Because it was deemed not Hard Enough task for real engineer to look at, so AI was sent to do it with no supervision, just checking the effects. Also overly excessive logging is probably useful to them in chasing some of the edge cases, the cost to users doesn't matter in the slightest to them
supriyo-biswas 3mo ago
The truth of the matter is that any time that has been saved in writing the code must be spent on ensuring proper system design, reviewing the code, and most importantly of all, QA, which is an uncomfortable discussion for AI techbros who are peddling complete automation of the software profession.
dathinab 3mo ago
> I don't understand how Codex can blunder so badly. because they trust the AI too much (and seem to be fin with acting knowingly negligent) the problem is - AI tends to produces very convincing looking code, even if fully wrong - AI does mistakes of kinds no human would do, at least no human who is also able to write convincing looking code - code reviews are hard, a lot of devs, including senior devs, put a lot of implicit trust into the co-worker behaving "sane and non malicious". But AIs behave sometimes not so sane and in a way (wrt. trying to be convincing). In the worst case in ways which if it where a human you might consider to be them trying malicious sabotage the product Like a "dump" example from work: - AI randomly removes a HTML element id while doing other changes in jsx/react - the PR has a lot of changes, the id removal line looks innocent, like some on the fly cleanup - human reviewers have the bad tendency to often not look too much at deleted lines, only if they need reference to how a new line was before (but it's only a deleted line and no new line) - you don't expect humans to randomly without reason delete important properties of components when changing other things - you maybe would still have found it, but it's a emergency fix for a production issue - it happens to miss integration tests, but happens to still matter a lot for one specific important for complicated reasons not properly tested flow (similar people tend to not test logging too much, at best the presence of needed info but hardly ever the absence of noise)

ramon156 3mo ago

Blegh, I puke every time I see obviously AI generated comments in GH PR's. You cannot assume any of these people have done their research, other than telling Codex to do it for them

b--l 3mo ago
It's because they use gpt-5.5-xhigh (the money making* model) to build it. (*for them)
deleted 3mo ago
[deleted]

b--l 3mo ago

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 the release of vibe coded junk. I would literally fix it myself but it's closed source for whatever reason. There are many discussions about which model is better, or if vibe coding is even possible. I point you to the extent of what one of the most well funded, money flush, well staffed model making companies can do with vibe coding. To me a screwup this bad (where the CEO has already made it clear they're now "focussing on coding") indicates that there's something truly broken in the company. No one on polymarket expects them to have a leading model any time soon for example. It's a tragedy. The world needs competition to anthropic.

l33tman 3mo ago
This was fixed long ago, if I'm thinking of the same bug. It was stuck in an inf loop all the time the codex window was open.
- cncjvu7 3mo ago
  Nah it's still doing weird shit. Uninstalled that crapware last week.
jofzar 3mo ago
> Codex is one of the most infamous examples of slopware Woah, let's not forget Claude code is right there
- mvATM99 3mo ago
  Yeah exactly. I'm not exactly building TUI's every day, but even i felt pain when i read that "small game engine" post
  - 3mo ago

dundercoder 3mo ago

If something like this is helpful or necessary, that’s what ram backed tmpfs is for.

mrweasel 3mo ago
Using a RAM backed tmpfs would be a work-around as to not trash your SSD. It's doesn't fix underlying problem. It's incredibly poor design on OpenAIs part.

ares623 3mo ago

i hope they find the smoking gun, the key insight, the kicker.

59nadir 3mo ago
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.
- jofzar 3mo ago
  Ugh this one's gets me so bad, same with "wire" and "wired" everything is wired to something.
  - never_inline 3mo ago
    that's a real gap
    - anematode 3mo ago
      The honest answer:
wrxd 3mo ago
At least they could call someone who’s is absolutely right so that the tool can see its mistakes now

indiv0 3mo ago

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 software than we do? To which the answer is obvious IMO -- even emergent properties can't elevate AI intelligence too far above the training dataset. So how do we get to superintelligent (or at least "not-wreck-your-NVMe-endurance-telligent") AI, if we, as a whole, are not smart enough ourselves? Judge not the slop-bot, lest ye be judged yourself, engineer.

applfanboysbgon 3mo ago
1. I bet that developer only made that mistake one time in their life. Humans learn from their mistakes, LLMs don't. If you rely on LLMs to generate all of your code, you can expect to run into the same issues again and again. 2. "One developer somewhere in the world made a bad mistake one time, so this represents the quality of all software devs everywhere". Maybe they were just a bad developer? Bad developers exist. I have never written a bug that has destroyed my users' hardware, and I think that writing such a bug is completely inexcusable in an enterprise environment with software that will be shipped to millions of users, as Codex is.
- lifthrasiir 3mo ago
  > I have never written a bug that has destroyed my users' hardware, ... Probably whoever (human or agent) originally decided to put TRACE logs into SQLite also thought---or reasoned---so. Maybe the decision was right at that time but the amount of TRACE logs have increased enormously. You will never know.
  - applfanboysbgon 3mo ago
    I love that we've moved the goalposts from "LLMs are better than artisanal software engineers" to "actually, shipping hardware-destroying bugs in production is literally unavoidable, nobody could possibly avoid doing it".

woadwarrior01 3mo ago

Someone 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 https://xcancel.com/bdsqlsz/status/2067964486615810369 [2]: https://xcancel.com/jeethu/status/2068087449469780434 https://xcancel.com/jeethu/status/2068087449469780434

NamlchakKhandro 3mo ago
The real solution is to stop using it and switch to Pi
- woadwarrior01 3mo ago
  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.
- deleted 3mo ago
  [deleted]
sgarland 3mo ago
DB-level rules saving the day once again.

rvz 3mo ago

The first of many bugs that are beyond the complexity of its authors, thanks to comprehension debt. Even with tests, the more complex the code base is, the more risky it is to vibe-code on it without introducing more bugs [0] and increasing the debt. Does not matter if the CI is green or if all the tests pass. It gets even worse if you can't explain the change / pull request or what the implications are after applying that "suggested" fix. [0] https://sketch.dev/blog/our-first-outage-from-llm-written-code https://sketch.dev/blog/our-first-outage-from-llm-written-co...

HPsquared 3mo ago
There are going to be sooooo many consulting opportunities after this wave.
- deleted 3mo ago
  [deleted]

deleted 3mo ago

[deleted]

bob1029 3mo ago

I'm struggling with how this much logging information could be generated at any level of verbosity. Is codex writing log entries while it's sitting idle? Why would someone want to look at these logs?

hun3 3mo ago

The operating system has historically trusted the applications not to do dumb things too much. Only now we're witnessing the consequences much more frequently thanks to accelerated slop.

skydhash 3mo ago
> The operating system has historically trusted the applications not to do dumb things too much. The OS is a thin layer providing an abstract and consistent interface regardless of the hardware configuration. Policing applications is mostly related to security and resources utilization, not moronic errors.
- hun3 3mo ago
  > The OS is a thin layer providing an abstract and consistent interface regardless of the hardware configuration. This is called a hardware abstraction layer, not OS. https://en.wikipedia.org/wiki/Hardware_abstraction https://en.wikipedia.org/wiki/Hardware_abstraction

i2km 3mo ago

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

drakythe 3mo ago
They're pretty bad about fixing issues it seems. My favorite is #2472 which they demonstrated "fixing" on stage on the release of GPT 5, but the ticket is still open and the "fix" hasn't been merged. The original blog that flagged this fact https://blog.tymscar.com/posts/openaiunmergeddemo/ https://blog.tymscar.com/posts/openaiunmergeddemo/ and the issue: https://github.com/openai/openai-python/issues/2472 https://github.com/openai/openai-python/issues/2472
- lelandfe 3mo ago
  Claude meanwhile just auto closes all issues because they simply don’t triage ~anything. There’s been countless instances of this horrifying issue created for over a year now: https://github.com/anthropics/claude-code/issues/16180 https://github.com/anthropics/claude-code/issues/16180 > Permission bypass when commands are chained with && At one point they fixed their auto stale bot closing bugs but, hey, guess that wasn’t long lived.
cl3misch 3mo ago
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.

taosu_la 3mo ago

Can someone tell me if the current sub-agent of codex is available now? There used to always be a spinning issue.

jofzar 3mo ago

This is actually such a classic blunder (shipping trace/debug logging on for everything), but funnily the impact is not in a normal way. It's crazy we have hit a point where memory, CPU speed and disk speed isn't getting clapped because a Dev shipped logging at trace level instead of what used to the application being catastrophically slow so its immediately fixed in the next update.

kuekacang 3mo ago
It helps too that agent work is done server side so you can hog all the local resources for your thin client.

abihordun 3mo ago

[flagged]

purpleidea 3mo ago

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 https://github.com/openai/codex/issues/23762

christophilus 3mo ago
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).
- matheusmoreira 3mo ago
  I went the full virtual machine route. Just finished hardening the setup and firewalling it off my local network. Not perfect but it does make me feel much safer.
- drakythe 3mo ago
  They can't respect boundaries as long as those boundaries exist only in the LLM instruction set. A human being who follows rules long enough the rules will become second nature (usually), almost to the point where long running companies are known for having rules no one understands (Chesterton's Fence is alive and well). But an LLM have a limited "memory" and while the instructions might land in there and be of sufficient priority to be "respected" a single instance of that memory getting too full or the LLM autocompleting the work around because that was the statistical "best" solution and any barriers that exist only in LLM instructions and not in hardcoded guards will evaporate like so much morning fog.
newtwilly 3mo ago
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 https://github.com/carderne/pi-sandbox/issues/50

taspeotis 3mo ago

OpenAI really snatched defeat from the jaws of victory late last year when Claude Code was a laggy mess. Nowadays Codex has typing latency out of the gate, whereas Claude Code has the odd pause but generally displays my key presses as … you know … I press them.

kasey_junk 3mo ago
Fwiw I have the exact opposite experience.
christophilus 3mo ago
I find Claude Code nearly unusable. I always have to type in neovim if I’m typing anything more than a few words.
- aquariusDue 3mo ago
  It runs fine for me on an old ThinkPad X220 loaded with 8 GB, an i5 and a barely working SATA SSD. This is on Fedora and Claude Code is installed from Anthropic's dnf repo (the latest channel). Granted I'm on the Pro Plan and I'm not running lots of sub agents but the default terminal app from KDE (Konsole) renders and keeps Claude Code responsive enough. I must be honestly missing some key piece of workflow otherwise I don't know why it would run so slow for other people on better hardware? Granted I'm taking care to tell Claude to not exhaust CPU cores and make sure to not trigger OOM errors, akin to "make no mistakes pls".
Lionga 3mo ago
[dead]

deleted 3mo ago

[deleted]

xfgong 3mo ago

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.

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

sigbottle 3mo ago

I have noticed absurd lag from the browser usage and sometimes complete bricking of my network too on my computer. I thought it was just my computer getting old, but possibly it's ChatGPT.

deleted 3mo ago

[deleted]

christophilus 3mo ago

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 https://github.com/openai/codex It's fairly easy to patch.

Lionga 3mo ago
[dead]
redox99 3mo ago
That's the CLI, not the codex app which is proprietary.
- milkshakes 3mo ago
  the issue is in the cli and app-server

altcognito 3mo ago

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

theowaway213456 3mo ago
Every time you write a test that handles some data, you write an assertion about how much data is handled? Come on, this is such an easy thing to forget to test. Don't act like there is some magical testing strategy that would have caught this
- altcognito 3mo ago
  I'll acknowledge that this is probably not likely to get caught. Integration testing could/should catch this, especially for a client side app. A simple constraints is a good thing. "Our app shouldn't use more than 50mb of ram, or use 3gb of disk space."
  - cute_boi 3mo ago
    load testing definitely should have caught this issue.
- tomjakubowski 3mo ago
  The most likely way I think you'd catch this in a test would be by accident, running some kind of long-running integration test for other purposes, and then finding the disk gets filled up in CI (or on a developer machine).
java-man 3mo ago
what QA?
- cute_boi 3mo ago
  Quality assurance testing....

whalesalad 3mo ago

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

akitowerns 3mo ago

[flagged]

joelthelion 3mo ago

A good moment to switch to an open solution like opencode or pi.

ewsbr 3mo ago

Looks like this was fixed[0], so it should land in the next release. [0] https://github.com/openai/codex/commit/e98d43ac372ddf7f513c0e30c56dd8dc35ea5404 https://github.com/openai/codex/commit/e98d43ac372ddf7f513c0...

tgtweak 3mo ago

Slightly better than the claude code "feature" that deletes all your session context and transcripts older than 30 days old.

qup 3mo ago
At least that's a decision vs a bug.
- tgtweak 3mo ago
  Not a decision that users are aware of though. Nor is there a setting to disable/change it. It just showed up one day and erased your previous sessions.
  - pdantix 3mo ago
    > Nor is there a setting to disable/change it. https://code.claude.com/docs/en/settings#available-settings https://code.claude.com/docs/en/settings#available-settings `cleanupPeriodDays` has always existed.
Mistredo 3mo ago
Codex has a similiar bug and makes chats disappear randomly.

collabs 3mo ago

I feel vindicated in my admittedly seemingly masochistic ritual of copy pasting code from the web browser to visual studio code even though I don't always pore over every line.

collabs 3mo ago

This is a little off topic but These guys really need to stop polluting the root folder of repo with Claude dot MD and copilot dot MD. Get in a room together and decide on a well known folder structure like docs/llm/*

g42gregory 3mo ago

I wonder if this falls into a "coding is solved" category? I start getting good results with Oh-My-Pi and Pi Coding Agents.

jackbucks 3mo ago

HAHAHAHAHAHAHA

linzhangrun 3mo ago

Considering the current storage prices and the SSDs whose lifespan you would thus exhaust...

fc-oai 3mo ago

Hey everyone, I'm an engineer at OpenAI. Thanks for the discussion here. Just wanted to report that a fix for this issue has been published in an update to the CLI and Codex App.

tdehnke 3mo ago
Looks like the fix doesn't work for all users from the comments on Github, please verify.

robeym 3mo ago

I'm on 0.139.0 on Linux and my visible ~/.codex/logs are only about 129 MB. This makes me even more conservative on upgrading these tools every time they prompt me to. Better to let them get a few miles on them and see how the community responds. In this case it sounds like 0.142.0 reduced the issue but didn't fully settle it. I'll wait for 0.143.0+ and see if that version is more acceptable.

MajorLettuce 3mo ago

Ironically now it seems that the companies that make these companies are the only ones to profit from slop software. There is no other reason for this to happen other than that the people responsible didn’t take care to check the code they are pushing. Which should be a signal in itself but I suppose it doesn’t matter if it is “good enough.”