Happy that I can now move the debug toolbar in the the 1.3 update! However, I think it is better suited for the sidebar, as it is often/constantly in the way.

Alternately, it could be attached to the debug console.

Yeah, sidebar would be an good option.
Especially after 1.3 (tab stacks feature) released, often find myself keep adjusting the debug toolbar position
Find it more convenient to put down the flaps open, keeping the standard for debug bar for all editors, eg Atom and Sublime
UX meeting notes
We could do a quick fix on this, but what we鈥檙e seeing is just one manifestation of a larger problem: our global commanding patterns need some work, as does our debugger UX. We will instead move to improve these overall experiences, which will in turn address this problem.
Anyone who wants a quick fix for your own productivity. Use command palette "Developer: Toggle Developer Tools" to use chrome developer tools. Then find the debug widget and change the top to 90px to shift it below the tabs and the find box. -5px is also nice :) ... I didn't like it covering the tabs.

I think this is a huge problem that makes me want to just avoid vscode for debugging. I'd recommend making the debug tools a part of a toolbar and persist across the different tab views. (if I am in explorer or plugins, I'd still be able to see the start debugging / stop etc.
Would be great if there was some progress on this. The UX of hiding other controls under a floating debug actionbar is a bit crazy.
So many other great aspects to VS Code, why has this languished for a year?
Any updates on this? Really hate constantly dragging the floating action bar around as I navigate a full screen of tabs. Can extensions modify VSCode's markup? If so I might look into writing an extension that simply moves the widget into the debug pane for now. It's definitely a pet peeve.
We will look into improving this experience this in the next couple of iterations, it is not on our plan for this milestone.
As I usually have quite a few tabs open when debugging, I was thinking more along the lines of:

If the side panel was closed, then it could fallback to the default behavior.
That's exactly what I was thinking. I'd really love it if it docked into the debug pane or debug console pane.
Alternatively we could make it float like the search widget, but perhaps anchored at the bottom, somewhat more consistent and out of the way, something like this:

Even moving the bar to the statusbar sounds like a saner idea to me:

If you want to check it out for yourself I've just published the extension.
I think that extension looks better than nothing.... But just kind of demonstrates the need for a proper toolbar... The status bar realestate is already limited... And with many of the extensions also pushing their ui to status bar (because that's all that's available) it's getting out of hand
I'm thinking what @mattacosta is thinking.
Also, when debugging multiple processes, I'd like multiple debug bars, instead of one debug bar with a dropdown to pick the process.
What @mattacosta proposed is great and that's what I'm hoping for. I think it can easily be allotted some vertical real estate at the top of the debug panel of the side bar while debugging.
Wherever it goes, it shouldn't be floating. Rather than cover other controls, it should displace them so it can be docked into place somewhere without covering up other tabs or toolbars. I'd even be fine if it sat to the left of the tab bar (outside the side bar) and displaced tabs to the right - sharing space currently allocated to the tabs. e.g.:

I've settled on placing it over the DEBUG start button:

How about just unanchored free floating option?
also this issue is apparently a dup of #2513
Yeah, closing as dupe of #2513
Hey @bgashler1 @isidorn
Any updates on this issue? Seems like it's been discussed for a while and the demand is there.
I hate this toolbar so much, finally ended up turning it off completelly by adding
"debug.hideActionBar": true to User Settings
Most helpful comment
Even moving the bar to the statusbar sounds like a saner idea to me:
If you want to check it out for yourself I've just published the extension.