[BUG] Prompt revision draft is lost once Arrow Up is pressed on Claude Extension for Visual Studio Code and Claude Code
Status Fixed / completed
Reported on v2.1.145
Maintainer reply None cached
Activity 8 comments · opened May 20, 2026 · closed May 22, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Sequence Arrow Up followed by Arrow Down does preserve drafts of reedited prompts, in some cases. Check provided steps.
Going deeper, this also affects v2.1.139 Claude Code
Very important! Altough this seems a duplicate of #6275, #37074 and #9492xxxx, this VERY ANNOYING behaviour that HAS NOT BEEN addressed yet.
What Should Happen?
Whenever navigation to previous prompts thru cursor up key occurs, current draft should never be lost, unless user explicitly allows/requests draft discard.
Error Messages/Logs
Steps to Reproduce
Open Claude Extension for Visual Studio Code
- Start new chat
- Type "_Prompt1_"
- Press Enter key
- Type "_Prompt2_"
- Press Enter key
- Press Arrow Up key. This recover "_Prompt2_" from history
- Type "_Fixed_ ". This will adjust prompt to "_Fixed Prompt2_" and cursor will be at 7th position)
- Press Arrow Up key. Tthis will move text cursor to 1th position)
- Press Arrow Up key. This will recover "_Prompt1_" from history
- Press Arrow Down key and you will get "_Prompt2_" instead of "_Fixed Prompt2_"
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.145
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
8 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I have managed to reproduce this odd behaviour and added steps to reproduce it. This IS NOT a duplicate of none of the referred issues on previous comment
It is similar to the other tickets but this focuses on VS Code extension. I had the same issue.
This on focuses on VS Code extension and Claude Code. Can you point an issue that provides the exact steps do reproduce this odd behaviour ? If not, please reopen the issue so it gets due attention.
Bear in mind that I have found several pretty close issues, some with PRs, which did not address this remainng case.
Oh I'm not a mod here, I just submitted my own bug for the same issue. I was just making a statement there are other cases that report the same issue and it looks like it dates back to last year from what I have seen.
Can you share your submission so I can assess whether it has enough details ?
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.