Windows app crashes when opening a project folder that was renamed outside Codex

Open 💬 3 comments Opened Jun 14, 2026 by Mxmmsv

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

26.609.41114

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The Codex App for Windows crashes when trying to open a project folder in Explorer after that folder was renamed outside of the app.

In my case, I had a project/chat linked to a local folder. I renamed that folder directly in Windows File Explorer. After that, the Codex App still showed the old project/folder entry in the sidebar. When I opened the project menu and clicked "Open in Explorer", the app crashed.

Expected behavior would be to handle the missing/renamed folder gracefully instead of crashing.

What steps can reproduce the bug?

  1. Open Codex App on Windows.
  2. Add or open a local project folder.
  3. Rename that folder directly in Windows File Explorer, outside of Codex App.
  4. Go back to Codex App.
  5. Open the menu for the existing project/chat that still points to the old folder path.
  6. Click "Open in Explorer".
  7. The Codex App crashes.

What is the expected behavior?

The app should not crash.

It should handle the missing or renamed folder gracefully, for example by:

  • showing an error message that the folder no longer exists;
  • offering to locate the folder again;
  • updating/removing the stale project path;
  • disabling "Open in Explorer" for invalid paths.

Additional information

This seems related to Codex App keeping a stale local folder path after the folder is renamed externally.

Attached screenshots show:

  • the Codex App project/sidebar entry;
  • the project context menu with "Open in Explorer";
  • the GitHub issue form.

The folder was renamed in Windows File Explorer, not inside Codex App.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗