The limitation is the debug adapter, not VSCodium itself. The FOSS C# adapter, netcoredbg, can't feed stdin through the integrated terminal. Only Microsoft's vsdbg does that, and its licence ties it to official VS Code and Visual Studio. The way round it that's worked for me is to skip launch mode and attach instead: start the program yourself in a normal terminal, then use an attach configuration to hook netcoredbg onto the running process. You get breakpoints and inspection, and since it's a real terminal the stdin behaves. Not as smooth as launch, but it stays fully FOSS.
this post was submitted on 08 Jun 2026
16 points (100.0% liked)
Programming
27223 readers
309 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
Thank you, I'll have to research how to do that!
Depending on your program you could mock out your terminal input.
I use jetbrains ide's, but I imagine you can set your run environment with parameters.
It seems JetBrains or the proprietary version of VSCode are the only convenient options, but they're so intrusive...
Yes that's how I set it to integratedTerminal
Edit: That probably is the solution on VSCode, but I found out the only debuggers available on VSCodium do not have anyway to connect to the terminal
That could be. I think c# in vscode proper has some proprietary secret sauce :(