It may be too extreme to call this a bug, but it is certainly "unexpected behavior"...
I have a command procedure that takes two directory names and runs winsin on them, by executing the simple command "winsin arg1 arg2". Just now when I ran it I was suprpised to see Winsin come up and start scanning something entirely different than the arguments I had supplied.
I had to scratch my head for a while before I figured out that the last time I had run it interactively I had left it on the Projects tab, and in this case the subsequent command "winsin arg1 arg2" ignored the arguments.
I think the command-line should force it to "Config" mode unless the /P switch is specified, regardless of how it was left last.