Ctrl+C does not terminate dotnet watch under concurrently, but works with --raw

[lfiorini]

Describe the bug

Description

When running dotnet watch run through concurrently, pressing Ctrl+C
does not return control to the shell.

The same command exits correctly when run directly, and it also exits
correctly when concurrently is run with --raw.

Reproduction

Environment:

• OS: Debian 13
• concurrently: 10.0.5
• .NET SDK: 10.0.400
• .NET runtime: 10.0.11
• Architecture: x64

Run:

npx concurrently "dotnet watch run"

[gustavohenke]

What happens in that case, though? Can you share a self-contained project? I tried on Alpine so far - seems to work with dotnet v8 and v10

[gustavohenke]

Likewise on Debian, though I get an uncaught error 🤔

[lfiorini]

I just tried in MacOS:
node --version: v24.20.0
npm --version: 11.19.0
npx concurrently --version: 10.0.5
dotnet --info: 10.0.400
Runtime Environment:
OS Name: Mac OS X
OS Version: 26.6
OS Platform: Darwin
RID: osx-arm64

Iterm2 Build 3.6.11

myapp.csproj:
Project Sdk="Microsoft.NET.Sdk.Web"
TargetFramework=net10.0
...

npx concurrently "dotnet watch run" Ctrl+C
...
[0] Application is shutting down...
[0] dotnet watch ⌚ [myapp (net10.0)] Exited
[0] dotnet watch ⏳ Waiting for a file to change before restarting ...
... hangs here I have to open another terminal and kill -9 ...

npx concurrently --raw "dotnet watch run" Ctrl+C
...
Application is shutting down...
dotnet watch 🛑 Shutdown requested. Press Ctrl+C again to force exit.
dotnet watch ⌚ [myapp (net10.0)] Exited
return to prompt