[BUG] Claude leaves behind locked panels in VSCode

Resolved 💬 3 comments Opened Sep 17, 2025 by bottlerocketjonny Closed Sep 25, 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?

If I open Claude like in the following screenshot of an empty project:

<img width="2559" height="1410" alt="Image" src="https://github.com/user-attachments/assets/cc860349-ebe2-48d9-8df2-13612e5019f1" />

When I close VSCode and reopen again, I end up with a locked panel where Claude used to be open:

<img width="2559" height="1416" alt="Image" src="https://github.com/user-attachments/assets/c4509a35-ff7b-4006-b9b5-95c31a0bbc67" />

I've tried settings like this but it doesn't help.

"workbench.editor.autoLockGroups": {
    "workbench.editor.processExplorer": false,
    "workbench.editor.chatSession": false}

It's slightly annoying having to unlock/close the panel when I want to do something with that space - really I'd be fine if it just reopened Claude again.

What Should Happen?

Claude should either reopen again or not leave behind a locked panel.

Error Messages/Logs

Steps to Reproduce

  1. Open empty VSCode project
  2. Open Claude
  3. Close VSCode
  4. Reopen VSCode

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.0.117

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

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