ChatGPT reminders rename an existing conversation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
In an established ChatGPT conversation, asking ChatGPT to create a reminder or automation automatically changes the existing conversation title to the reminder topic. This overwrites the recognizable title of the ongoing chat and makes it difficult to find later.
Impact: users can lose the familiar title of long running conversations and have difficulty locating them afterward.
What steps can reproduce the bug?
- Open an established ongoing ChatGPT conversation with an existing recognizable title.
- Ask ChatGPT in that conversation to remind you about something at a future time.
- Confirm that the reminder is created.
- Observe that the existing conversation title changes to the reminder topic.
What is the expected behavior?
Creating a reminder or automation should not overwrite or rename the existing conversation title. The chat should retain its existing title unless the user explicitly renames it or normal title generation behavior independently determines a change.
Additional information
This report concerns reminder and automation creation within an existing ongoing ChatGPT conversation.
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 reproducing the reminder or automation flow in an established conversation and observe where the existing title changes. Trace the reminder-creation path and its title-update behavior; done means creating a reminder leaves the existing conversation title unchanged unless the user explicitly renames it or normal title generation independently changes it.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100