FYI, transmission-cli is considered deprecated by the Transmission developers. Using both transmission-daemon and transmission-remote is the recommended approach. Actually, transmission-cli uses transmission-daemon internally and they share the same configuration. transmission-cli is still useful for one-off downloads, but I still prefer the recommended way because I'd like to seed older torrents some more time.
> transmission-cli is considered deprecated
Wah! Bad news! I like to kick off a download from an SSH shell. Now I have to find out what transmission+remote is.
I was greatly disappointed too when I found out about transmission-cli's deprecation, but I have since found and replaced all uses of it with stig[1] which, for me, does the same thing and more.
You can still do that
$ transmission-remote -a one.torrent two.torrentYou could also check out rtorrent: http://rakshasa.github.io/rtorrent/, but I remember reading that development has stalled on that project.
aria2 can download a torrent from a magnet link given as CLI parameter.
I'm not a user of transmission-cli in general, but transmission-create (part of transmission-cli) is indispensable for me.
There's also the Transmission Remote GUI, which is a nice GUI for remotely controlling the Transmission daemon, on say, a NAS: https://github.com/transmission-remote-gui/transgui
It's great for keeping downloads going overnight without having to leave all the power-hungry devices powered on.
FWIW, qbittorrent also has a built-in web interface. It's also one of the most feature-rich BitTorrent clients.
And you can install it with just the web interface as qbittorrent-nox.
It's a great piece of software. I'm running a web remote v2.92 on an rpi with simple basic auth protection, and it has been working flawlessly for years now.
The cli is also used by Fragments, a Gnome torrent app.
It is not very known but there actually is a transmission-cli for common torrent operations that may come in handy some time.