As documented by multisession-reconnect.txt: No connected No disconnected 1. C/X(1) 2. C/X(1) That is: If you don't have any sessions at all, matching the specified command, and you are not allowed to create any new sessions, you should get an error message. Currently, this is done for policy 1. In the Ask policy, however, you are reconnected automatically, even though the command does not match. Also, perhaps you should get an Ask dialog instead. I do not believe that this is 2.0.0 critical.
When we are implementing this bug, we might want to clean up the tlclient implementation as well.
