However, this is far from trivial. For example, most statement download protocol requires some user interaction, at least for entering of a PIN number or a password. If you try to avoid all user interaction, you would need to pass these things in advance as command line options... which makes gnucash's command line option dependent on the kind of download technique. 

In aqbanking, we have a commandline program (aqbanking-tool) which uses the ncurses interface for PIN/password entering, which means we still need user interaction. In aqbanking it is additionally supported to read a password from a file -- but of course this is a no-no in terms of security, so we don't advertise this a lot. 

Anyway, I'm just saying that IMHO all useful bank download/importing will need some user interaction, and skipping this shouldn't be done because of security reasons. So you would need some really good idea on how to implement this.

Yeah, I don't think this is a UI-less scenario, so much as "run the import druid with this file after initialization is complete".  This would probably imply that the SX since-last-run dialog wouldn't run, as well.

*** Bug 104183 has been marked as a duplicate of this bug. ***

Additionally, if an instance of GnuCash is already open, it should run the import druid on the open instance instead of launching a new instance.

GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=345744. Please continue processing the bug there and please update any external references or bookmarks.