mpilot wrote:

Opening session using command-line parameter in scripting is deprecated.

Are you aware of what that warning exactly means?
It says that you should not do

But:

It does not limit you anyhow.
It just warns you that you are combining features that were never intended to be combined.

---

Also, we are definitely not intending to remove the ability to load stored sites in scripting (although we discourage it).
https://winscp.net/eng/docs/scripting#configuration

From the other posts in this forum I am getting the impression that WinSCP's command-line interface is focused on scripting for automation and not for interactive users. Although WinSCP has a nice GUI with choices, I still prefer using the command-line for multi-file development projects, because it avoids the time to load the screen from large directories and I already know the names of the files I am after.

We use WinSCP as a replacement for Windows' command-line ftp and were surprised to see the "deprecated" and "saved sites" messages when we upgraded from 5.1.5 to 5.15.3. Setting up saved sites to be used as command-line parameters is the most convenient way to access specific machines and directories for interactive command-line users.

Opening session using command-line parameter in scripting is deprecated.
In scripting you should not rely on saved sites, use this command instead:

I can understand not using parameters and saved sites for scripting, since this impacts portability. But both features are invaluable for interactive use and I am concerned that "deprecated" means that one or both of them may be removed in future releases.

Would you please consider retaining our ability to specify a saved site on the command line interactively?