Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • 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
    by ramon156
  • It's because they use gpt-5.5-xhigh (the money making* model) to build it.

    (*for them)

    by b--l
  • 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/*

    by collabs
  • Somebody please donate some tokens to this plucky startup, they need our help.
    by bravetraveler
  • 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-co...

    by rvz
  • There are going to be sooooo many consulting opportunities after this wave.
    by HPsquared
  • Looks like this was fixed[0], so it should land in the next release.

    [0] https://github.com/openai/codex/commit/e98d43ac372ddf7f513c0...

    by ewsbr
  • 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.

    by jofzar
  • It helps too that agent work is done server side so you can hog all the local resources for your thin client.
    by kuekacang
  • 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.

    by taspeotis
  • I find Claude Code nearly unusable. I always have to type in neovim if I’m typing anything more than a few words.
    by christophilus
  • Fwiw I have the exact opposite experience.
    by kasey_junk
  • Vibe coding takes "move fast and break things" to a whole nother level.
    by neuralkoi
  • 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
    by GL26
  • We are running out of things to break.
    by comboy
  • Yeah. Here I am sitting on a major incident at our company because someone’s vibe coded shit went seriously wrong.
    by cryo32
  • 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...

    by i2km
  • 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.
    by cl3misch
  • 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/ and the issue: https://github.com/openai/openai-python/issues/2472
    by drakythe
  • 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

    It's fairly easy to patch.

    by christophilus
  • That's the CLI, not the codex app which is proprietary.
    by redox99
  • 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

    [2]: https://xcancel.com/jeethu/status/2068087449469780434

    by woadwarrior01
  • The real solution is to stop using it and switch to Pi
    by NamlchakKhandro
  • DB-level rules saving the day once again.
    by sgarland
  • 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.

    by b--l
  • 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.

    by markdog12
  • > THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!!

    This seems to be a common Chromium problem across tons of software. GitHub has the same issue with its spinners, VSCode as well.

    by CryZe
  • > It's a tragedy. The world needs competition to anthropic.

    I agree, though Sam Altman's company is the last option I'd want to replace Claude with. I would sooner exhaust every open model.

    by giancarlostoro
  • Well thank you for your service. I thought about trying out Codex after the disaster that is Claude Code. I'll be fine without either one on my machine
    by xpct
  • Excel would use 100% CPU if you left a cell selected and your screen saver turned on because you were idle.

    That bug caused untold grief for multi-user session hosts / terminal servers / Citrix XenApp for a better part of a decade. Way before slopware!

    People forget that software written by people is… even worse.

    It’s like the self driving car debate: sure, the robot taxis will kill people on occasion, but people kill people regularly.

    by jiggawatts