For example, during a deploy that takes time, a user types Ctrl-C, this does unlock the prompt and the command "seems" to have been interrupted. Actually the command thread has been interrupted but not the remoting task that is in progress. So although the user can think its command has been aborted, it is silently processing in background.

When interruption occurs in a command thread, current remoting task should be canceled. This is what we are doing today when a timeout is set on a command.