File tree labels are overly truncated even when there is enough horizontal space
What version of the Codex App are you using (From “About Codex” dialog)?
26.422.8496.0
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
File and folder names in the Codex App file tree are overly truncated with a middle ellipsis, even though the file tree panel has enough horizontal space.
Examples from the “All files” tree:
componentsis displayed ascompr.....entsnode_modulesis displayed asnode_.....dulespackage.jsonis displayed aspackag.....onREADME.mdis displayed asREADM.....dpostcss.config.mjsis displayed aspostcss.confi.....jstsconfig.tsbuildinfois displayed astsconfig.....uildinfo
This makes the file tree hard to use because many common file names become ambiguous.
What steps can reproduce the bug?
- Open Codex App on Windows.
- Open a local repository.
- Open the file tree / “All files” panel.
- Observe that file and folder names are truncated with a middle ellipsis even when there is enough horizontal space in the panel.
- Switch the app language to English and reset the UI font to the default.
- Reopen the file tree and observe that the issue still happens.
What is the expected behavior?
The file tree should use the available horizontal space before truncating labels.
Short file and folder names such as components, package.json, README.md, and middleware.ts should be displayed fully when the panel has enough room.
Additional information
I initially noticed this with the Japanese UI and a custom UI font, but the issue still reproduces after switching the app language to English and resetting the UI font to the default.
Environment:
- Codex App version:
26.422.8496.0 - OS: Windows
- UI language: English
- UI font: default
- Theme: Tokyo Night
Screenshots attached.
<img width="1920" height="1020" alt="Image" src="https://github.com/user-attachments/assets/31e30df9-ab2e-40ac-8e2d-196c169136c1" />
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗