As you can see it takes more command input than the Chrome commands, but it works fine. I checked and the spots are uploading for MF and 40M. It is running in the background and a CTRL-C from the command line kills the process.
I wanted to spot New Zealand and Japan stations last night and had to resort to using all manual entries in the DX Cluster softwarre (VE7CC). Ten Tec used an ini file to transfer CAT data between softwares for the Ten Tec Pegasus, ORION, and other Ten Tec Radios. MixW, HDSDR, and other software were written to take advantage of this constantly updated ini file, sending and receiving, frequency and mode information.
Long story short; if the KiwiSDR wrote a file in the same ini format as Ten Tec used, software such as MixW would provide, logging, DX cluster spots and the ability to send spots to the cluster. Such software would automatically change frequency and mode according to how either connecting software was immediately set by the user. Change the KiwiSDR and MixW adjusts, change MixW and the KiwiSDR adjusts.
I've read that John has future plans for the dx.json format and use. I can imagine that file being redesigned to provide a data interface to other connecting software on the user's KiwiSDR instance.
In my case I mostly provide the service for the benefit of local hams that have problems with noise on their home receivers during HF nets. Of course most of the connections are from all over the place/world and it is difficult to tell what most are listening for or to. Now that VE3SUN has been providing connections to KiwiSDR receivers from current DX-spots, I've started paying more attention to listening on the KiwiSDR. I'm looking forward to a better interface from VE3SUN to the KiwiSDR.
Of course I do catch new stations on the waterfall and add a tag for them just to remember that I have heard them there before.