Enhance multi-session run/debug and its corresponding integrated terminal to make life easier on developers

[jolsen-mitsu]

Let's say I have 3 debug configurations set up, and over time, I end up with all of them concurrently as additional run/debug sessions. As expected, each session gets its own integrated terminal for output and interaction.

So, I launch configuration A and a integrated terminal is opened.
I start launch configuration B as an additional session and an integrated terminal is opened.
I start launch configuration C as an additional session and an integrated terminal is opened.

In the debug toolbar, there is a dropdown list of the currently active run/debug sessions. If my itegrated terminal for configuration A is displayed, and I change the dropdown to session B, the integrated terminal stays on session A. if look at the integrated terminal names and their hover information, I only see a generic names and the hover provides a process ID.

I don't see a way to correlate which integrated terminal belongs to which active run/debug session.

It would be great if:

1. The launch configuration used to create the integrated terminal instance was optionally part name (first part?) and/or to the hover for the integrated terminal. If this was configurable, like the window titles where the user can define a custom text string with variables, that would be ideal. Right now it shows the process ID, but I have no way of knowing which process ID belongs to which debugging session I launched. This way there is an easy visual (or accessible) way to know which integrated terminal is related to which running run/debug session.

2. Add an option to enable auto-switching of the integrated terminal to correspond with the selected run/debug session selected in the debug toolbar. So if I choose session A in the toolbar, it would automatically switch to the integrated terminal corresponding to session A. If I then choose session C in the toolbar dropdown, it would then switch the integrated terminal that is associated with session C

Thank you for everything

[VSCodeTriageBot]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vs-code-engineering]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vs-code-engineering]

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!