Aborting a command has strange behavior

I see 2 problems how aborting a command currently works.

• If the console is empty and you send Ctrl+C, then the text "[killed]" appears in the console. I guess nothing was actually killed. Then I try to for example create a new project and trigger: 'new-project --named testProject' and this command is swallowed or killed? Please see attached screenshot:

• Second, .. I tried several times to abort "an already in progress new-project" command but sometimes it succeeds and sometimes not. Like on my next screenshot. I figured out that it depends on the speed how fast I press the abort keys on the keyboard. It wasn't very hard for me to simulate the error.