Who fired the quality control department? This combined app update is embarassing.

Open 💬 3 comments Opened Aug 26, 2026 by myriahmaek
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.818.41509

What subscription do you have?

Pro $200

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Whoever decided to mix ChatGPT Projects and local Codex projects into the same sidebar without clearly distinguishing them created an unnecessarily confusing mess and utilized zero quality control before releasing the combined design.

I can click a normal ChatGPT project and a local Codex repository from the same list. They use identical folder icons. There is no obvious badge telling me which is ChatGPT and which is Codex. Why would they not be separated based off which function you're currently using? Can someone explain the reasoning, or the lack of common sense with this design?

Then I click into an actual Codex repository, where I am looking at code changes, tests, commits, and local file paths, and what does the upper-left corner still say?

“ChatGPT.”

Seriously?

If you are going to combine two applications/workflows into one interface, the absolute minimum requirement should be making it obvious which environment the user is currently using.

I should not have to reverse-engineer your interface.

I should not have to remember that one project has spaces and another has dashes.

I should not have to open settings and look for “source folders” to determine whether something is a ChatGPT project or a Codex project.

This is basic UX and basic quality control.

Give Codex repositories a Codex icon. Label them “Codex” or “Local.” Change the header when I enter one. Put them in their own section. Literally any of these solutions would be better than making two fundamentally different project types look almost identical.

It amazes me that a company with access to some of the most intelligent AI models on planet earth could create and not catch such a ridiculous and frustrating UI flaw. I have slowly been converting my work flows from Claude to Codex because of the frustration with Claude and Anthropic, as have many others and to see such an easily catchable and fixable design flaw be pushed out to users is frankly ludacris. Lets get it together, design just a little smarter and try to keep the converted users you're getting. Its really not that hard you guys.

Please forward this to the Codex/ChatGPT desktop product and UX teams. This is not some obscure edge case. It is an immediately visible design flaw created by merging the products without adequately redesigning the navigation around that merger. There is quite literally zero excuse for how this got pushed out to the public with such an obvious design flaw, who in the world is getting paid however many hundreds of thousands of dollars to run whatever department is responsible for this blatant quality defect? As a high school drop out with zero college education I could do a much better job and would be happy with half their salary. Just sayin.. Or at least let your top users review updates and provide feedback before you embarrassingly release flawed designs to your public facing interfaces.

no-active-thread-01a03c64-62f3-7aa0-91a9-5668b573e168

What steps can reproduce the bug?

Basic app navigation.

What is the expected behavior?

To be able to distinguish ChatGPT projects from Codex projects?

Additional information

I would consider a job offer to help prevent embarrassing future app releases.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #40581
  • #40536

Powered by Codex Action

R-Bower · 2 days ago

Tibo is busy resetting limits, he doesn't have time for silly things like usability and quality control!

myriahmaek · 2 days ago
Tibo is busy resetting limits, he doesn't have time for silly things like usability and quality control!

There's no excuses for @tibo-openai unless I see some usage resets sitting on my account, Im down to 1.