[Windows] Cannot reply to an existing ChatGPT conversation unless I branch it
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 the ChatGPT app on Windows, I can open and read an existing conversation, but I cannot continue replying in that chat normally.
The only workaround I have found is to create/continue from a branch of the conversation. After branching, I can reply again, but the original chat remains effectively non-replyable.
This means I have to keep branching a conversation just to continue using it.
Steps to reproduce
- Open the ChatGPT desktop app on Windows.
- Open an existing conversation.
- Try to send another message in the same conversation.
- The normal reply flow is unavailable / does not let me continue the conversation.
- Branch the conversation from an earlier message.
- In the branched conversation, replying works again.
- Repeat: when the issue occurs, another branch is required to keep replying.
Expected behavior
I should be able to keep replying in the same conversation without creating a branch.
Actual behavior
I cannot continue replying in the existing chat and have to branch the conversation to regain the ability to reply.
Platform
- ChatGPT desktop app
- Windows
- App version: unknown
Additional information
A screenshot shows the affected conversation and that I had to use the branch/“Continued from …” flow to continue replying.
I can provide the screenshot and app version/logs if needed.
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
Reproduce this in the Windows desktop app by opening an existing conversation and testing normal reply versus the branch flow; record the app version and logs if available. Done means the original conversation accepts a new reply without requiring a branch, with the behavior verified against the listed steps.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100