Customer complaint: unsolicited renaming of established chats disrupts identification and continuity
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Customer complaint
During ordinary Chat use, an established conversation name sometimes changes without my requesting a rename. The replacement appears related to something I just asked for or completed. I then have to work out what the conversation used to be called and restore its identity. I do not want this behavior.
Observed behavior
This is intermittent customer-reported behavior. The exact trigger and responsible component have not been established. The complaint concerns changing an existing conversation title during continued use, rather than generating an initial title for a new conversation.
Customer impact
I rely on stable conversation names to recognize ongoing work and distinguish chats. An unsolicited rename disrupts that organization, makes a familiar conversation harder to find, and creates unnecessary recovery work. A title that describes the latest action may no longer describe the ongoing purpose of the conversation.
Requested resolution
Preserve established conversation names unless I explicitly request or perform a rename. Respect user-assigned names in particular. If automatic retitling is offered, make it an explicit opt-in rather than silently changing established names. Provide a straightforward way to recover the previous title when an automatic rename has occurred.
Investigation / acceptance
Please investigate which title-generation or agent behavior can rename existing chats after subsequent messages or completed tasks. Verify that continuing a named conversation, including changing topics or completing a task, leaves its title unchanged without explicit rename authorization.
Reported September 15, 2026. Exact app version, affected conversation IDs, and a deterministic reproduction are not captured in this report.
Related but distinct: #45784 requests persistent title visibility in the header. This complaint concerns the title itself being changed without permission.
Filed through the established OpenAI issue channel. If another team owns the ordinary Chat naming behavior, please route this complaint to that team and provide a trackable reference.
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
No files, tests, or entry points are identified, and the report lacks a deterministic reproduction or affected conversation details. First establish whether ordinary Chat title generation is implemented in this repository or belongs to another team. Done requires a reproducible case and verification that established or user-assigned titles remain unchanged without explicit rename authorization.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100