claude-code
claude-code copied to clipboard
anthropics
[Feature Request] Enhance VS Code Extension UX: Relocate to Secondary Panel & Add Chat Resumption Options
Hi Team,
I have two suggestions to improve the VS Code extension's usability:
Move to Secondary Panel: Please allow the Claude panel to be moved to the secondary side panel. This is standard for most AI assistants and allows users to keep the file explorer open while chatting, which is much more convenient.
Add Chat Resumption Options: Instead of always starting a new chat, please add options to resume the previous session or continue from a recent chat, similar to the --resume and --continue CLI flags. This would make continuing previous work much faster.
Thanks for considering these improvements!
yes, the editor group approach is awkward, +1 for secondary panel and option to resume
VS Code now allows extensions to contribute views to the secondary sidebar https://github.com/microsoft/vscode/issues/151681
Keep in mind that this API is still in proposed state, and we aim to finalize it start of October. So it would be great if you try out the API - let us know if it works for you, and once it is final you should be able to use it.
@isidorn I came here looking for a feature request asking to not lock the new editor group when Claude starts in the VS Code extension.
As I searched, I noticed the extension had an update. After I updated it, I have observed this confusing behavior (which may have been present before my recent update but I never noticed it until now):
- If I already have a secondary editor group, when I start Claude Code it goes into that group, unlocked.
- If I have no secondary editor group, when I start Claude Code it goes into a new group that is locked.
It would be nice to just have an option somewhere that says "Whatever group we end up in, don't lock it please".
Not sure if this warrants a new issue. I can't find one that exactly matches it. At least now that I know the pattern of how it works, I'll try to remember that. But I know I'll forget and end up with a locked panel which will mess up my flow.
I would like to have the option for claude to be in bottom panel. I currently open terminal window and type claude in order to have it work for me in the bottom. Hope that could be an option for when I click the Claude button in vscode to save those manual steps.
currently I use both copilot and codex in vscode on the left sidebar, so I can toggle between file explorer and the chat UIs without having to change the layout
with claude I currently have to hide whatever pane it is in so I have space to see the file explorer and the code at the same time, and vice-versa, meaning switching between claude and file explorer/codex/copilot is a 2 step process.
with copilot or codex, this is a one step process, as these occupy the same pane as the file explorer.
I believe supporting claude being part of the left panel would be a great addition
pictured are codex and copilot at the bottom of the panel icons
+1 for this feature. Very nice update today, but the ability to actually use this in the sidebars (primary or secondary panel) would make alot of sense for viewability!
Thanks for everyone's feedback! 👍 We're look into adding the ability to launch into the secondary sidebar, once the VSCode API is finalized/generally available! We decided not to default launch in the primary sidebar and stick with with editor tabs for the time being.
I'd suggest that Claude Code should open by default at the same panel where it was open during previous session?
@hackyon-anthropic why is this even an either/or choice? The button to open Claude Code as an Editor Tab works great, keep it! In addition to it, there can be a pinnable Primary Sidebar extension tab that works just like Codex. There is no contradiction between two approaches.
How long ago were you last working with Claude on laptop without an external monitor?
I was somehow able to get this to work, but then today it's not working? Can we get a way to toggle this on for those of us that want to use CC in the pane.
On Mac you can do Cmd + Shift + P, then search Claude: Open in Side Bar! Guessing its Ctrl + Shift + P on Win/Linux. Thanks guys!
@kristruman thanks! it is clearly moving in the right direction. But this sidebar view is not pinnable, and once you switched to an Explorer or Source Control, it is gone. A keybinding helps though.
On Mac you can do Cmd + Shift + P, then search Claude: Open in Side Bar! Guessing its Ctrl + Shift + P on Win/Linux. Thanks guys!
Thank you very much! That's what we want!
Yes, that works, but there's no visible button for that action, like the one for opening in a new tab. Also you can't change the font or size, that's a limitation of vscode even though there are many who asked for it to be customizable.
@hackyon-anthropic why is this even an either/or choice? The button to open Claude Code as an Editor Tab works great, keep it! In addition to it, there can be a pinnable Primary Sidebar extension tab that works just like Codex. There is no contradiction between two approaches.
How long ago were you last working with Claude on laptop without an external monitor?
The (OK, A) problem with the editor tab is that every time it wants to edit something, it shows a diff in a new tab on the same panel, which means having to switch back to the Claude Code tab in order to approve the edit. It's extremely inconvenient.
Thanks for everyone's feedback! 👍 We're look into adding the ability to launch into the secondary sidebar, once the VSCode API is finalized/generally available! We decided not to default launch in the primary sidebar and stick with with editor tabs for the time being.
Github Copilot has been supporting the secondary sidebar for months.
How long ago were you last working with Claude on laptop without an external monitor? Last night. :-)
@dxkaufman do you mind showing a screen recording of your issue? Claude code should be opening up in a new column, whereas the diffs should show up in the main editor column
Unfortunately, I believe the GitHub copilot extension was using private internal APIs so they can load directly in the sidebar by default without the user dragging it there. This was possible as GitHub copilot was bundled in VSCode (and both owned by the same parent company).
I don't want Claude in the side panel, I would prefer it to behave as just another document and for it to not appear in it's own locked group so I can move it around easily.
@dxkaufman do you mind showing a screen recording of your issue? Claude code should be opening up in a new column, whereas the diffs should show up in the main editor column
Unfortunately, I believe the GitHub copilot extension was using private internal APIs so they can load directly in the sidebar by default without the user dragging it there. This was possible as GitHub copilot was bundled in VSCode (and both owned by the same parent company).
@hackyon-anthropic - OK, here's what it looks like with Claude Code in one tab and an open file in the other, with the sidebar on the left (just the file explorer at the moment):
(actually, I switched the tabs so CC is on the right)
Here's what it looks like after I gave it the instruction:
It brought the 'Claude's edit' tab up on top of Claude, so now I have to click on the Claude tab to tell it that I want it to complete those edits.
@dxkaufman do you mind showing a screen recording of your issue? Claude code should be opening up in a new column, whereas the diffs should show up in the main editor column
Unfortunately, I believe the GitHub copilot extension was using private internal APIs so they can load directly in the sidebar by default without the user dragging it there. This was possible as GitHub copilot was bundled in VSCode (and both owned by the same parent company).
I believe that they have opened up the Secondary Side Bar to any app now using Views, would love for the Claude extension to use this versus a doc view, so it can use the full height on the right side. https://github.com/microsoft/vscode/issues/263786
@dxkaufman do you mind showing a screen recording of your issue? Claude code should be opening up in a new column, whereas the diffs should show up in the main editor column Unfortunately, I believe the GitHub copilot extension was using private internal APIs so they can load directly in the sidebar by default without the user dragging it there. This was possible as GitHub copilot was bundled in VSCode (and both owned by the same parent company).
I believe that they have opened up the Secondary Side Bar to any app now using Views, would love for the Claude extension to use this versus a doc view, so it can use the full height on the right side. microsoft/vscode#263786
In code now after I use CMD + Shift + P and choose Claude Code: Open in Side Bar it uses the full sidebar like Codex/Roo Code and stays in there through reboots/project swaps etc.
Yes, we do already provide a launch in sidebar VSCode command for power users. Note that you still need to drag it to the right hand side panel (unless you want to keep it at the left hand side).
The button should respect the last launched mode as well (editor tabs vs sidebar)
@
Yes, we do already provide a launch in sidebar VSCode command for power users.
You do, but this primary sidebar view is not pinnable as a sidebar tab (like Codex is). Once you switched to Explorer or Source Control tab, it disappears. Assigning a hotkey helps, but this is NOT an expected user experience from a mature product.
@
Yes, we do already provide a launch in sidebar VSCode command for power users.
You do, but this primary sidebar view is not pinnable as a sidebar tab (like Codex is). Once you switched to Explorer or Source Control tab, it disappears. Assigning a hotkey helps, but this is NOT an expected user experience from a mature product.
I might be setup differently to you, but my experience does not mimic this. Regardless of what I select (Explorer, Extensions, Source Control) Claude remains pinned in my right hand sidebar. Are you using yours in the right hand secondary side bar?