When pressing ESC ESC ESC up up enter you can't get back to the last turn - and this rollback sometimes crashes

[dagelf]

What issue are you seeing?

It's too easy to lose a 15+ minute run context and turn by accident and there is no way to redo it deterministically

What steps can reproduce the bug?

After a few turns, press ESC left arrow left arrow enter. Then try to go back to the turn you were on before you did this. Not possible.

What is the expected behavior?

You should be able to revert back to where you were. The visual cue says "Enter to edit message" but it doesn't say "Enter to trash all subsequent messages from transcript and logs" which is what it actually does.

Additional information

No response

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• CLI/TUI: support editing an already-sent user message and regenerating downstream turns #17243
• Allow edit on any message, not just the last one #18708

Powered by Codex Action

[etraut-openai]

This is working as intended, so I don't think we'd consider this a bug.

Do you have a better suggestion for this UX? If so, I could change this to a feature request.

[dagelf]

You should be able to go back to where you started by purely pressing DOWN/FORWARD arrow again, Ie, if you press Esc again and go forward, it should be able to go to the messages that were there before you accidentally pressed Enter.

The real underlying problem is that there is a 1-5 second lag sometimes when pressing Esc, sometimes you press Esc to abort but Esc has mutlple functions depending on state. If you press Esc while generating, it stops generation.

In situations where people want things to stop they generally are used to lag or are unsure if they pressed it or if it worked, and they might press it 2 or more times in a row (eg ^C) - what happens if you press Esc 3 times is that you do not end up in a state where you can not use UP and DOWN arrow keys to copy previous messages, but you end up in a state where you can delete the whole tail end of your conversation before you realize that the UX is in a different state.

There's also a deeper bug here, I just ended up in a state where this happened, on the current version, by just going into this Esc Esc mode 3 times in a row:

› test

■ Conversation interrupted - tell the model what to do differently. Something went wrong? Hit /feedback to report
the issue.
Error: thread/rollback failed in TUI

$

So there's also still a real bug here, in addition to the bad UX which seems to be by design. I'm sure you can fuzz it in 5 minutes by just using Esc and the arrow keys. My PRs that took me days, got rejected, but maybe if you invite me to contribute you can get some more public service from me.