v0.1.3 · Windows, macOS and Linux
rigseed puts a modern interface on the daemon you already trust.
The reliability of qBittorrent, with the interface it never had.
sync/maindata · torrents/info · app/preferences
Stock qBittorrent on the left, rigseed on the right, the same Ubuntu, Debian and Arch images downloading in both. Drag the handle, or use the arrow keys.
qbittorrent-nox ships inside the app and starts with it, bound to loopback. On first launch rigseed generates its own WebUI credentials and writes them into the config, so there is no password to invent and no port to open.
rigseed reads and writes the same qBittorrent configuration the stock client uses. Categories, save paths, limits and trackers are the ones you already have. Go back to the old interface whenever you like and nothing has moved.
Every screen prints the endpoints it drives, because a client that hides its transport is a client you cannot debug. What you see on screen is one call away from what you could make yourself with curl.
Transfers
Your torrents already work. The client is the part that never did.
rigseed writes no torrent code. It starts the daemon, talks to it over the same Web API the built-in interface uses, and draws what comes back. If rigseed crashes, your transfers do not even notice.
Tauri 2 · Rust host
The window, and nothing else. No torrent code of its own.
upstream, unpatched
Started with the app, bound to loopback, on a profile of its own.
libtorrent
Your existing session, trackers and configuration. Untouched.
The daemon is the upstream release, compiled and bundled unmodified. That is why nothing about how your torrents behave changes, and it is why every release carries the source that built the exact copy inside it.
Picking one does not recolour a few buttons. Every neutral surface is a mix of its base tone and the accent, so the page you are reading retints with it. These are the app's eight accents and the app's own two-stage mix, running here on a colder ground than the app uses, so this is the mechanism itself rather than a picture of it.
Free and open source, under Apache 2.0. Every file is published with its SHA-256 so you can check what you got before you run it.
Builds are not code signed yet, so Windows and macOS will both warn you on first open.What that looks like and why.