Repository navigation
[FEATURE]: Better controls/UX for queued messages. #8685
Description
Activity
This issue might be a duplicate of existing issues. Please check:
- [FEATURE]: edit queued message prompts #6942: [FEATURE]: edit queued message prompts - Request to edit queued messages like in Claude Code
- [FEATURE]: Add ability to unqueue messages #4821: [FEATURE]: Add ability to unqueue messages - Request to cancel/remove queued messages
- Forgets queued messages #1476: Forgets queued messages - Reports that queued messages are lost after tasks finish
Feel free to ignore if none of these address your specific case.
- marked Add delete menu option for queue tasks #11729 as a duplicate of this issue
on Feb 2, 2026 I implemented the cancel side of this at b0a0769. Queued messages now show Cancel/Copy instead of Revert/Copy/Fork, and the undo keybind peels off the last queued message before falling back to abort+revert. Cancelled text goes back into the prompt input, which, if I remember correctly, is essentially how you "edit" queued messages in Claude Code.
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
Reacted by Benoit de Chezelles and williamtwomey
Feature hasn't been suggested before.
Describe the enhancement you want to request
At the moment, if you try to edit a queued message in the same way as in Claude Code, you only get a duplicate in the queue. When you edit and send the message, a new version is added to the queue instead of replacing the prior version. Ideally, it would be really nice and convenient to have a clear option for editing the queued message that is compatible with the Claude Code approach.
And, as a logical next step, could we please add an option to the menu of a queued message to edit or remove it completely from the queue? Currently, we only have the options to revert, fork or copy queued messages, as well as already sent messages. This is misleading because it doesn't make sense to revert or fork yet as the message hasn't been sent. However, we could add meaningful actions suitable for queued messages, such as 'edit' and 'cancel'.