> For your average user I think this is confusing and not good UX.
I disagree, as the average vault user is likely someone familiar with Unix (though there is a Windows binary). Here is an example that I just ran on my machine.. very silent.
$ mkdir source
$ cd source
$ touch file
$ rm file
$ $ rm file
$ echo $?
$ 0
I picked this up at http://www.rsync.net/resources/howto/remote_commands.html for running commands over ssh and not seeing the console output.
Confirming success is only necessary when users do not trust the program (due to bugs, confusing UI/API, etc.). They will seek reassurance that their actions are successful. However, if users trust the program then no confirmation is needed.
We should be creating stable and predictable programs so that we can maintain users' trust. Otherwise we have to introduce hand-holding which degrades everyone's experience through extra cognitive overhead and user interaction.
Since a lot of people using this tool will be developers with MacBooks and not hardcore *nix users, it’s probably a good choice to ignore that convention.