IdeaSift

VS Code users struggle to access commands without a customizable toolbar

The signals describe VS Code users who want visible, configurable buttons for commands they use occasionally or often. They say relying on shortcuts and the command palette makes commands harder to remember or discover, and some report switching to another IDE. Most requests date from 2018, though a 2023 request raises a similar need for custom buttons in the Command Center, so current demand should be validated.

For VS Code developers who prefer clickable command controls. Mentioned from Jan 2018 to Jun 2023 on GitHub.

5 different people described this problem in 2 separate discussions.

Week of 2026-07-13: 0Week of 2026-07-20: 0Week of 2026-07-27: 0Week of 2026-08-03: 0Week of 2026-08-10: 0Week of 2026-08-17: 0Week of 2026-08-24: 0Week of 2026-08-31: 0Week of 2026-09-07: 0Week of 2026-09-14: 0Week of 2026-09-21: 0Week of 2026-09-28: 0
0 mentions in the last 12 weeks
Indie fit
3.0/10
Pain
5.3/10
Frequency
6.5/10
Willingness to pay
0.0/10
Momentum
5.0/10
Who pays
Professionals
Competition
Medium
Build difficulty
Medium

What people said

Quoted word for word. Follow a link to read the whole discussion.

  1. Add an optional configurable toolbar below the menu Whole my life I used ide where there was a customizable toolbar. I starded to use vscode and stopped to use it after one day. It is impossible to remember all shorcuts. In any other popular ide you can put any menu item on toolbar and use it from time to time.
    morozovsk on GitHub (microsoft/vscode)Jan 2018+412 upvotesAsked for a toolHas a workaround
  2. vs code has so much going for it however lack of feature discoverability, lack of easy navigation and forcing users into a land of Ctrl+Shift+P / the command palette bucket of everything does hold it back IMO
Build brief

See what to build and who will buy it

  • 1 product idea with the smallest useful version and pricing
  • 3 places to find your first customers
  • 4 more quotes from people who have this problem
  • Current workarounds, existing solutions and risks