Chat Customization: last items in lists are clipped and not visible

Open
#321,322 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
electron, typescript
Domain
desktop, frontend

Research direction

Start by reproducing the issue in VS Code's Chat Customization, especially the MCP and Skills sections, and inspect the list layout and scrolling behavior. The fix is done when the final entries remain fully visible after scrolling to the bottom in all affected sections; verify against the provided screenshot and video.

Written by the indexing model from the issue text.

Description

Version: 1.124.2 (Universal)
Commit: 6928394f91b684055b873eecb8bc281365131f1c
Date: 2026-06-12T00:12:36Z
Electron: 42.2.0
ElectronBuildId: 14159160
Chromium: 148.0.7778.97
Node.js: 24.15.0
V8: 14.8.178.14-electron.0
OS: Darwin arm64 25.1.0

Summary

Last items in Chat Customization lists are cut off and not visible even when scrolled to the bottom

Description

When opening Chat Customization in VS Code, some items in the lists are not visible. Although the scrollbar reaches the bottom, the last entries in the list remain hidden/clipped and cannot be brought into view.

This affects multiple sections, including:

  • MCP (shown in the attached screenshot)
  • Skills
  • Other Chat Customization sections following the same pattern
Steps to Reproduce
  1. Open Chat Customization in VS Code.
  2. Navigate to a section with enough items to require scrolling (e.g., MCP, Skills).
  3. Scroll the list all the way down.

Video: https://github.com/user-attachments/assets/68678e10-2dd4-410b-95a3-6bf974b07815

Image
Dominant language
TypeScript
Stars
193k
Forks
42.9k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode

All issues in microsoft/vscode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.