Well, they do not really advertise that fact and the codebase is not exactly the same, it seems.

The mentioned vs code connection - and it seems, I cannot just edit edge dev tools with edge, something I can do in chrome.

I am curious why you can edit Edge dev tools with Edge. There is literally a part of the article where I show that this is possible with a screenshot showing it on my Mac.

"I cannot just edit edge dev tools with edge,"

I could not "just" edit it like I am used to from chrome - but apparently had to activate a experimental setting. Which you did explain in a video. Not text. I read text.

I still want to understand the issue. The Sources tool is the same in Chrome and in Edge. And if you undock the devtools and you press CMD+Shift+I (or CTRL+I) on either Chrome or Edge you get a second DevTools instance to debug the first one. If you use a workspace, you edit files externally in either Edge or Chrome as they are the same thing. There is no difference in either of these use cases. What use case are you finding where it is different? I'm really confused.

"And if you undock the devtools and you press CMD+Shift+I (or CTRL+I) on either Chrome or Edge you get a second DevTools instance to debug the first one. "

Not for me on a vanilla edge instance. Pressing Ctrl + Shift + I closes the dev tools completly, no matter where the focus is. (on Win 10, german localisation, Edge 95.0.1020.40)

But it works like you describe (and how I know it) on a vanilla chrome dev instance.

So is there maybe some hidden setting, one needs to activate first?