[Bug] Chat title overlaps with underlying chat text when sidebar is collapsed
What version of the Codex App are you using (From “About Codex” dialog)?
26.709.11516 (Note: The "About Codex" dialog no longer exists; this version was retrieved from the Configuration tab.)
What subscription do you have?
Enterprise
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
Description
When utilizing the Codex Desktop app, collapsing the left sidebar causes a responsive layout failure where the top header fails to properly contain its elements. Specifically, a moderately long active chat title forcefully overlaps with the underlying chat text in the main conversation window, rendering the content visually cluttered and illegible.
Observed Behavior
The chat title does not respect its horizontal header boundaries when the viewport width changes. Instead of truncating or maintaining a spatial gap, it bleeds into the main chat container, overlapping directly with the actual conversation text.
Attachments
Please find attached screenshots demonstrating the UI before and after collapsing the sidebar.
<img width="3020" height="134" alt="Image" src="https://github.com/user-attachments/assets/9a7c6e86-8d40-43a8-b8e3-9eb346200547" />
<img width="3024" height="100" alt="Image" src="https://github.com/user-attachments/assets/c7f6b536-c361-4df5-bbe3-0537bfa50f17" />
What steps can reproduce the bug?
Steps to Reproduce
- Open the Codex Desktop application.
- Start or open a chat thread with a title that is long enough to span the majority of the top header.
- Ensure that the chat contains standard text outputs near the top of the main viewport.
- Click the interface icon to minimize or collapse the left sidebar.
- Observe the top header where the chat title drops down and merges with the main chat text.
What is the expected behavior?
Expected Behavior
The UI elements should maintain strict container boundaries. When horizontal space is reduced by collapsing the sidebar, the application should dynamically truncate the chat title with an ellipsis within its own header section to prevent a visual collision with the chat body below.
Additional information
_No response_