I have good news. I created UXP Debugger for VSCode so you can debug without going back forth between UDT and VSCode.
I had to use some little tricks to make it work and hope with help of Adobe I could get rid of extra setup steps in next version and improve source mapping.
Get plugin here: UXP Debugger - Visual Studio Marketplace
Please let me know how it worked for you and what you think.
Wish there was one for IntelliJ 
Great work! Thank you for your hard work on this!
For the rc file, what would the settings be for PremierePro? Is that information documented anywhere? I have not yet investigated in the marketplace if it’s documented in the readme, but just thought I’d ask here.
Once you patch UDT, UDT will make rc file automatically. It has built-in feature to make them. After patch it only gets triggered on plugin load.
If someone wants to do it, I can help with the know-how. The first thing you would need to figure out is whether IntelliJ can accept CDP messages. The Chrome debugger protocol, or whether we need to translate them into DAP (Debugger adapter protocol), by some library we would use.
I want to first focus on fine-tuning the existing plugin and improving reliability and user experience.
Of course
And I’ve no idea about the supported protocols. If I decide to learn a new thing at some point, I might look into it 
Hi Jaroslav!
Thank you for sharing your plugin. However, I had difficulty setting it up correctly in both Photoshop 25.0 and InDesign 19.5 on Windows 10.
I followed your instructions closely — or at least I think I did — but after running UXP: Attach to Adobe UXP Plugin and selecting manifest.json, I see the blue “Eval in Adobe…” at the bottom instead of the orange “Attach to UXP Plugin” like in your video.
Regards,
Kasyan
Thanks for feedback. Other than that does everything works as it should? Anyway, I will look into why that status bar might show something else.
Unfortunately, no, it doesn’t.
I’ve already left the office for today. But I also tested it on my home computer (in Photoshop 24.6.0, Windows 10) and the problem is the same: when I hit ‘start debugging’, nothing happens in VS Code. All the breakpoints look like greyed-out hollow circles. Though in Photoshop, it works as expected.
Finally, in VS Code, I get the following error:
Does console.log log into console? If yes it should show file name and line number as clicable link. What happens if you click it?
No, it doesn’t log into console.
What is your version VSCode?
Version: 1.120.0 (user setup)
Commit: 0958016b2af9f09bb4257e0df4a95e2f90590f9f
Date: 2026-05-12T20:17:22Z
Electron: 39.8.8
ElectronBuildId: 13870025
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.18363
Finally, somehow I managed to make it work in InDesign.
Thank you!
