[BUG] When using external editor, should not blank the terminal

Status Fixed / completed
Maintainer reply None cached
Activity 7 comments · opened Oct 13, 2025 · closed Oct 22, 2025

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?

When I press Ctrl-G while running Claude Code in VSCode terminal, the terminal becomes blank, making it impossible to refer to Claude output while composing the prompt.

What Should Happen?

It should keep the conversation log visible.

Error Messages/Logs

Steps to Reproduce

With a session in progress inside VSCode terminal, press Ctrl-G

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.0.14

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

Particularly painful in planning mode with multi-screen plan - want to be able to respond to the plan by having the session log in terminal and my response to the plan in editor side-to-side, but with the log hidden, I lose most of the benefits of Ctrl-G.

View original on GitHub ↗

7 Comments

github-actions[bot] · 1 year ago

Found 2 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/9137
  2. https://github.com/anthropics/claude-code/issues/9218

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

pilotwaffle · 1 year ago

i get the same the screen goes blank and pressing escape twice does nothing, I loose everything that was being worked on

MatejBabis · 12 months ago

This would be a very helpful feature for me, sadly the same error experience on my side. I completely lose the conversation and have to kill terminal.

ANogin · 11 months ago

@karenzhou-ant is it really fixed? I still see it in 2.0.25 that is currently the latest...

ANogin · 11 months ago

@bcherny how is it that some rando who just created a github account has permissions to self-assign and mark as completed, but the original reporter does not have permissions to then reopen? :(

P.S. Tried to report via the hackerone link for security reporting, but got stuck in Cloudflare "prove you are human" loop :(

ANogin · 11 months ago

It looks like this is actually fixed in 2.0.27 - thank you Anthropic team for the fix! And if @karenzhou-ant is actually a real anthropic employee, very sorry for calling you "some rando".

github-actions[bot] · 11 months ago

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.