IdeaSift

VS Code debug and task configs make developers repeat values

Developers coordinating VS Code launch configurations with pre- or post-launch tasks may have to choose or enter the same values multiple times. They also duplicate variables across launch configurations, making shared settings harder to maintain. The signals point to a need for one source of truth across these configuration files, though they do not establish how common the problem is today.

For VS Code developers with multi-step debug and task workflows. Mentioned from Oct 2017 to Jun 2020 on GitHub.

4 different people described this problem in 3 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
5.0/10
Pain
5.5/10
Frequency
5.8/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. I'm also running into issues with this. I have a launch configuration that prompts for the IP address. It then has a preLaunchTask to do some preparation on the device but that task then has to prompt for the same IP address again
  2. The way I have it set up now means that I have to choose the option 3 separate times
Build brief

See what to build and who will buy it

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