claude-code - 💡(How to fix) Fix [FEATURE] VSCode Plugin Modification (Patch included)

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

This should be sent to the VSIX/VSCode plugin team. Idk how to contact them.

<img width="755" height="872" alt="Image" src="https://github.com/user-attachments/assets/d9ec6f56-9071-44f8-bca2-4c6dd95a914c" />

Proposed Solution

Requested improvements:

• Show the session list directly in the Claude Code sidebar instead of hiding it behind the small history popover.
• Use the available empty sidebar space more efficiently by splitting the main view into a chat pane and a session pane.
• Put the session pane on the right side of the sidebar.
• Add a draggable divider so users can resize the chat pane and session pane.
• Add Pin and Star actions to sessions.
• Keep the existing rename/edit and delete buttons working exactly as they do today.
• Show a running indicator on any session that is currently active.
• When a session finishes running, show a blue unread/done dot.
• Clear the blue dot when the user opens/clicks that session.
• Allow "Rewind code" to proceed when Claude can rewind the conversation context, even if the file diff is empty.
• Make modal dialogs/backdrops render above the resizable session pane so dialogs are not visually cut off or covered.

Updated

• Add a header toggle (next to the "Session history" clock icon) that hides/shows the right-side session pane and its resize handle, with the state persisted across reloads.
• Harden the split-pane flex layout so chat content with long messages or wide code blocks cannot push the divider, clip the session pane, or visually bleed into the other pane.

Alternative Solutions

I've included a markdown file with the suggested changes and basic instructions so your team can just have Codex implement them. Additionally, this pastebin contains the Python patch I'm currently using to apply changes to the VSIX, in case your dev team wants to reverse-engineer it to simplify their work.

I just made a repo. I was making too many changes https://github.com/LunarWerxs/vsclaudefix

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

No response

Additional Context

No response