Pressing ↑ Makes Draft Prompt Disappear

Resolved 💬 5 comments Opened Dec 18, 2025 by d-w-d Closed Dec 23, 2025

What version of the VS Code extension are you using?

Codex 0.4.52

What subscription do you have?

PRO

Which IDE are you using?

VS Code

What platform is your computer?

MacOS

What issue are you seeing?

I just spent ~5 minutes working on a VERY PRECISE prompt and then pressed ↑ which caused ALL of my prompt to dissappear and get replaced with a previous prompt. When I pressed ↓, I could NOT recover the prompt I had been building.

INCREDIBLY FRUSTRATING!

What steps can reproduce the bug?

I was building my prompt, then decided I needed a new file as a scratch pad. I pressed CMD+N to create a new file, but the focus was in the codex chat, so it created a new chat. When I went back to the chat I had been working in, I pressed up for some reason, and it started cycling through previous chats, and wiped out my lengthy draft prompt.

What is the expected behavior?

First, I would have expected pressing up when there is content in the prompt to NOT do anything!

But having moved to a previous prompt, I would at least expect pressing down to eventually stop at my draft prompt, but no, it just cycles through past prompts, and it appears that my draft is gone.

I also HATE the UX that pressing down seems to cycle you through god-knows what. I would prefer pressing down to bring you to an empty prompt. I.e. up/down needs to be linear with bookends, not cyclic! Once I was pressing up/down, I completely lost where in my prompt history I was!

Additional information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗