It's actually low key kind of sad/pathetic tbh.. like, in a traditional software dev environment I could respect the time it takes to fix bugs/etc; but with an army of highly capable AI agents at hand, and with users filing far more detailed bug reports (and often solutions) [..]

Apple Reminders / Calendar

Also, naming the windows based on the thread they have open, so I don't have to manually sift through 13 different 'Codex' windows to try and and guess which one was the one I actually needed.

Closing/restarting/updating Codex desktop doesn't restore the windows I had open; which means it takes a lot of manual effort to write down what windows I had open on what desktop spaces to be able to manually restore it; and that means I can't get the new updates quickly.

That feel when Codex doesn't recognise folders during a git command, and then tries to bring down your entire system by consuming more than half (5k+) of it's allowed child processes in a single burst; that doesn't even get killed when no longer relevant: github.com/openai/codex/issu…

Unhinged Codex 'feature' request: Open source (at least the Electron parts) of the Desktop app since JS is practically open anyway; so we don't have to unpack it and work through minified source when debugging things.

Would it be too unhinged of a 'Codex feature' request to want better triage of Codex related GitHub issues / bug reports? There seems to be a lot of good information that seems could be better de-duped automagically, verified, and used to improve the app/etc.

There’s a whole pile of pretty good bug report threads on GitHub about various unbounded process fanout, zombie processes not reaped, memory leaks, etc, etc that are honestly making Codex painful AF to work with…

Performance, restore windows on update/restart, name windows based on their active thread so I don’t just have 30 “Codex”, allow us to set custom command for ‘open in’ and of the things I’ve shared on past threads / RT’d about them recently, and that’s just off the top of my head

There’s also a pretty good list of high impact bugs on the GitHub issues tbh.. though it feels a bit ‘shout into the void’ for how little love they seem to get; or cross post links when PRs land that should impact them, etc.

Big agree tbh. Even if just the JS parts; it’s not like minified JS inside an electron app’s .asar is particularly ‘secret’ currently anyway.. so just make it properly open.

Seemingly not according to these new comments on one of the issues, with repro's still occurring after updating: github.com/openai/codex/issu…

Is it actually this time? Because from what I was seeing on the issue last time I checked, some parts were but there were still parts that weren’t and causing the same style of problem still. And a bunch of other tangentially related things burning HDD in loops from other things

There’s a pretty solid list of some pretty old and outstanding ones on the codex GitHub repo that honestly often feels like an unacknowledged ghost town. Aiming that way a little more could be good!

Part of it is fixed; but according to comments in the relevant issues; it’s still not fully fixed; and there are other bugs reported and sitting for a LONG time on the GitHub issues killing HDD’s in similar ways

That then also allows us to get into deeper internals of electron to be able to do things like setting an actually useful window name on the windows (eg. "Codex - <thread title>" rather than just having 30 windows called "Codex")

That feel when the Codex desktop app doesn't provide good window names, or good ability to search through / manage / persist open window state between updates/restarts/etc; so you end up reverse engineering ways to solve it yourself and build the supporting tooling to do so.

TIL that you can enable remote debugging on the main electron thread by sending SIGUSR1 while the app is still running. So much nicer than needing to restart with —inspect or —inspect-brk

What's next? Hopefully pointing Codex + GPT 5.6 Sol at the codex GitHub issues and properly triaging/cross-linking/de-duping/acknowledging and fixing them; it honestly feels pretty shitty being a dev reporting things with proper investigation/etc just to have it rot in the void.

Feedback: Point Codex + GPT 5.6 Sol at the codex GitHub issues and properly triaging/cross-link/de-dupe/acknowledge and fix them; it honestly feels pretty shitty being a dev reporting things with proper investigation/etc just to have it rot in the void.

Feedback: Stop treating people who report issues on GitHub as ignored nothingness that are basically screaming into the void: xitter.cf/_devalias/status/20768…