Before submitting
Area
Not sure
Steps to reproduce
Summary
If a prompt fails due to a provider error, the failed prompt becomes stuck in the conversation. It cannot be reverted to or deleted from the UI. I originally encountered this with an incompatible Codex provider version causing a provider error, but the same behavior can be reproduced by disconnecting the internet before sending a prompt.
Reproduction Steps
- Start a new thread.
- Send a message ("prompt 1")
- Confirm the assistant responds normally.
- Disconnect from the internet.
- Send another message ("prompt 2")
- Reconnect to the internet.
- Send additional messages and confirm the chat works again.
- Hover over prompt 2.
Expected behavior
The failed prompt should still support reverting to that message, or mark it as unsent and allow deleting it from the thread.
Actual behavior
The failed prompt has no usable actions other than copy. It cannot be reverted to or deleted, so it remains permanently stuck in the conversation.
Impact
Minor bug or occasional failure
Version or commit
0.0.23
Environment
Arch, installed through aur/t3code-bin
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
Before submitting
Area
Not sure
Steps to reproduce
Summary
If a prompt fails due to a provider error, the failed prompt becomes stuck in the conversation. It cannot be reverted to or deleted from the UI. I originally encountered this with an incompatible Codex provider version causing a provider error, but the same behavior can be reproduced by disconnecting the internet before sending a prompt.
Reproduction Steps
Expected behavior
The failed prompt should still support reverting to that message, or mark it as unsent and allow deleting it from the thread.
Actual behavior
The failed prompt has no usable actions other than copy. It cannot be reverted to or deleted, so it remains permanently stuck in the conversation.
Impact
Minor bug or occasional failure
Version or commit
0.0.23
Environment
Arch, installed through aur/t3code-bin
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response