Based on what the author says in his explanations, I expected to be able to type in the path to a command and see the results displayed. Exactly what I could achieve in the terminal, excep that there I have the benefit of a PATH environment variable, and lots else besides.
It is absolutely beyond me what the utility of this program could be to anyone other than its author. Only he really knows why he wanted an interface like this to perform shell interaction with programs, and the brief description at the website is completely inadequate to explain the rationale.
After struggling for ten or fifteen minutes to even get the SAME functionality as the shell via terminal, I was able to recover the stdout of a simple unix command in his interface. The application needs at least a short account of how the various input fields and output views are intended to work. Such labels as "Start" "Stop" "Set" and "Execute" are barely intelligible in their context and seem to have little or no relation to one another.