Customer complaint: restore conversation titles in Chat headers when the sidebar is hidden
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Customer complaint / usability regression
Please restore the active conversation name in the header of ordinary Chat conversations in the desktop application.
Observed behavior
On Windows, my Work/Codex conversation visibly displays its project icon and name (for example, “F10 Finish Line Manager”) in the top header row. In the ordinary, non-Work Chat conversation shown in my comparison, the equivalent header contains controls such as Share but no conversation name. With the sidebar hidden, I cannot readily identify which conversation I am using. I report this across my ordinary Chat windows; the supplied comparison establishes one example, not an independently verified universal rollout.
Reproduction
- Open an existing, named ordinary Chat conversation in the desktop app.
- Hide the sidebar to recover working space.
- Inspect the conversation header.
- Compare it with a Work/Codex task, where the task name remains visible.
Expected behavior and requested resolution
Keep the current conversation title visible in the header even when the sidebar is hidden. Use available header space and truncate long titles with a way to reveal the full name. Update the title correctly when switching conversations.
Customer impact
The missing title forces me to keep a space-consuming sidebar open or reopen it merely to determine where I am working. This is particularly disruptive with several conversations/windows open and increases the risk of entering instructions into the wrong conversation. Restoring persistent conversation identity is a basic usability requirement.
Environment / routing
Observed September 15, 2026, in the Windows desktop experience. Exact app version was not captured. This affects ordinary Chat within the desktop experience; Work/Codex is the working comparison. Filed here through the established customer issue channel. If another team owns this surface, please route it to that team and provide a trackable reference.
The customer supplied two comparison screenshots to the filing assistant; the observations above describe them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the desktop application's ordinary Chat header and the sidebar-visibility and conversation-switching entry points; no file or test is named in the report. Compare that header with the Work/Codex header, then verify that a title remains visible when the sidebar is hidden, truncates with a way to reveal the full name, and updates when switching conversations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100