What changed

The first release rigseed can install for itself. If you are on 0.1.6, open Settings, then Updates, and it will be offered there.

The launch film

Fifty-one seconds on what rigseed is and why it exists, with real captures on both sides. Watch it on the site, or take the 4K master from the assets below (rigseed-launch-4k.mp4, 22 MB).

https://github.com/user-attachments/assets/27b267ad-15bd-4e87-b70e-099665380cad

Fixed

• The first frame no longer shows torrents that are not yours. Launching used to paint a list of sample downloads until the daemon answered, then replace them. It now starts empty.
• A splash while the daemon is being reached, so a cold start looks like the app starting rather than assembling itself. It appears on launch only, not when you bring the window back from the tray.
• The installer carries rigseed's icon instead of a generic one.
• The Updates panel no longer contradicts itself. It claimed rigseed never checks on its own; it does check once at startup, which is what puts the dot on the Settings icon. Nothing is downloaded or installed without being asked, and that part was always true.

Smaller releases

A release carried thirty-five files, sixteen of them licence texts. Those are now one rigseed-0.1.7-licences.zip, with THIRD-PARTY.md left out of it since it is the index that says which text applies where. The sidecar's source tarball stays separate, where the licence that requires it expects to find it.

Which file do I want

Platform	File
Windows	rigseed_0.1.7_x64-setup.exe
macOS (Apple silicon)	rigseed_0.1.7_aarch64.dmg
Linux, any distribution	rigseed_0.1.7_amd64.AppImage
Debian or Ubuntu	rigseed_0.1.7_amd64.deb
Fedora or RHEL	rigseed-0.1.7-1.x86_64.rpm

A .sha256 sits beside each one if you want to check your download.

If you are on Windows and installed rigseed before this release, you have to reinstall once by hand. Uninstall your existing copy first, then install the .exe below. An update cannot carry you across, which is the thing this release fixes.

One Windows installer

Earlier releases shipped both an .exe and an .msi. The update manifest can name only one file per platform, and it named the .exe, so anyone who had installed the MSI was being offered an installer that would not upgrade their copy. It would have installed a second one alongside it.

From this release there is one Windows installer and the mismatch cannot happen. There is no .msi any more, which is why the one-time reinstall is needed.

macOS and Linux are unaffected and update normally.

Which file do I want

Platform	File
Windows	rigseed_0.1.6_x64-setup.exe
macOS (Apple silicon)	rigseed_0.1.6_aarch64.dmg
Linux, any distribution	rigseed_0.1.6_amd64.AppImage
Debian or Ubuntu	rigseed_0.1.6_amd64.deb
Fedora or RHEL	rigseed-0.1.6-1.x86_64.rpm

A .sha256 sits beside each one if you want to check your download:

certutil -hashfile rigseed_0.1.6_x64-setup.exe SHA256

The .sig files and rigseed.app.tar.gz are what the in-app updater consumes. You do not need to download them by hand.

Release plumbing only. Nothing in this release changes anything you will notice while using rigseed.

It exists to exercise the update path. 0.1.4 was the first build with an updater in it, so no installed copy of rigseed has ever consumed an update manifest. This is the first one that will, and an otherwise empty release is the right thing to test that with, because nothing else competes for the signal.

Fixed

• The release draft now arrives with a changelog generated from the commits rather than a placeholder, so the page the update prompt points at says what changed. 0.1.4 shipped with a placeholder there.

If you are on 0.1.3 or earlier

Those builds have no updater and will not offer you anything. Install this one by hand from the assets below, once, and updates work from then on.

Which file do I want

Platform	File
Windows	rigseed_0.1.5_x64-setup.exe
macOS (Apple silicon)	rigseed_0.1.5_aarch64.dmg
Linux, any distribution	rigseed_0.1.5_amd64.AppImage
Debian or Ubuntu	rigseed_0.1.5_amd64.deb
Fedora or RHEL	rigseed-0.1.5-1.x86_64.rpm

A .sha256 sits beside each one if you want to check your download:

sha256sum -c rigseed_0.1.5_amd64.AppImage.sha256

The .sig files and rigseed.app.tar.gz are what the in-app updater consumes. You do not need to download them by hand.

In-app updates

rigseed can now check for its own updates. Settings has an Updates row that tells you what it found in a sentence, and the app looks once at launch and marks the Settings icon with a dot if something is waiting. Nothing is downloaded or installed without you asking.

This release is the one that adds the ability, so it cannot announce itself. If you are on 0.1.3 or earlier, that build has no updater in it and will not offer you 0.1.4, so install this one by hand from the assets below. From 0.1.4 onward updates are offered in the app.

Every update is signed, and a build will refuse an update that is not signed by the rigseed release key.

Third-party licence texts

Every release now carries the licence texts of everything rigseed ships, including the dependencies of the bundled qBittorrent sidecar, plus THIRD-PARTY.md listing them and the sidecar's own source tarball.

Fixed

• Adding a search hit no longer forces the add dialog open when your chosen layout says otherwise.

Which file do I want

Platform	File
Windows	rigseed_0.1.4_x64-setup.exe
macOS (Apple silicon)	rigseed_0.1.4_aarch64.dmg
Linux, any distribution	rigseed_0.1.4_amd64.AppImage
Debian or Ubuntu	rigseed_0.1.4_amd64.deb
Fedora or RHEL	rigseed-0.1.4-1.x86_64.rpm

A .sha256 sits beside each one if you want to check your download:

sha256sum -c rigseed_0.1.4_amd64.AppImage.sha256

The .sig files and rigseed.app.tar.gz are what the in-app updater consumes. You do not need to download them by hand.

The Files tab is a tree

Opening a torrent's Files tab used to print every file it contained, all at once, in whatever order the daemon returned them. A torrent with two hundred files across forty folders gave you two hundred rows, with the nesting suggested only by indentation. There were no folders to collapse, and loose files sat interleaved between directories.

It is a real tree now.

• Folders are rows. They sort above files, with names ordered the way you would count them, so Part 2 comes before Part 10.
• Deeper levels open from the arrow in front of a folder name. The folder a torrent is named after opens by itself, so the tab never greets you with a single row repeating the title above it.
• A folder shows what it is hiding: how many files it holds, their total size, and how far along they are, weighted by bytes rather than by file count.
• You can act on a folder without opening it. Its checkbox selects everything inside, and its priority applies to everything inside. When the files inside disagree, the priority reads Mixed rather than picking one of them and quietly flattening the rest.
• Files now carry a document icon instead of the folder icon every row used to wear.

Collapsed folders are not rendered at all, so a torrent with thousands of files no longer builds thousands of rows to show you ten.

---

Installing

Downloads are below. Every file has a .sha256 beside it, and checking one is worthwhile because these builds are not code signed:

• Windows shows SmartScreen. Choose More info, then Run anyway.
• macOS is refused by Gatekeeper on first open. Right-click the app, choose Open, then confirm. Apple Silicon only.
• Linux has no equivalent gate. Take the .deb, the .rpm, or the .AppImage.

There is no in-app updater yet, so upgrading means downloading again.

The qbittorrent-nox source archive is attached alongside the installers, which is what GPLv3 section 6(d) asks for: the source available from the same place as the binary.

Downloads landed in the wrong folder

The headline fix, and if you ran 0.1.0 or 0.1.1 it affected you.

Finished downloads went into the app's own profile directory instead of the folder rigseed named, and clicking a finished file did nothing. Both symptoms had one cause: rigseed wrote the save path under Downloads\SavePath, which is the qBittorrent 4 key. A configuration written fresh by qBittorrent 5 marks itself as already migrated, so the legacy key is never consulted and the daemon fell back to its default.

rigseed now writes the key the daemon actually reads, and repairs a configuration that only carries the old one, so an existing install corrects itself on next launch rather than needing to be set up again.

Search results were never sorted

The results header said "sorted by seeds" and nothing anywhere sorted anything. search/results answers per plugin and the daemon appends, so results arrived grouped by provider with each block ordered on its own.

Sorting now happens across the whole list, and the column headings do it. A column opens the way it should open, so seeds, size and peers start high while name and engine start at A, and clicking the same heading again reverses it. Ties are broken consistently, which matters while results are still arriving: without it, rows reshuffled on every update.

Move a torrent's files without re-downloading

New. Point a torrent at a different folder and the daemon relocates what is already on disk rather than fetching it again. Failures say what actually went wrong, whether the path was refused, unwritable, or already in use.

Also fixed

• The Description link on a search result did nothing. It was an anchor with target="_blank", which a Tauri window has no meaning for. It opens in your browser now.
• Adding a torrent from search has a toggle: skip straight to downloading, or open the add dialog first.

---

Installing

Every download has a .sha256 beside it, and checking one is worthwhile because these builds are not code signed:

• Windows shows SmartScreen. Choose More info, then Run anyway.
• macOS is refused by Gatekeeper on first open. Right-click the app, choose Open, then confirm. Apple Silicon only.
• Linux has no equivalent gate. Take the .deb, the .rpm, or the .AppImage.

There is no in-app updater, so upgrading means downloading again.

The qbittorrent-nox source archive is attached alongside the installers, which is what GPLv3 section 6(d) asks for: the source available from the same place as the binary.

Linux, for the first time

0.1.0 shipped Windows and macOS only. The bundled qbittorrent-nox inherited the build machine's glibc and would not start on Ubuntu 22.04, so Linux was held back rather than shipped broken.

The daemon is now built against an older base, and Linux joins the release in three formats: .deb, .rpm and .AppImage.

The AppImage had never built before. The reason turned out to be a chain: the sidecar was publishing an unpatched binary, which meant linuxdeploy could not resolve Qt for qbittorrent-nox, and two further faults in the Qt plugin collection sat behind that one. All three are fixed and the daemon has been rebuilt carrying them.

All three formats ship rather than one replacing the others. If you installed the .deb, keep updating through apt: an application rewriting a file dpkg believes it owns is worse than not updating at all.

Also fixed

• Only the SQLite driver is collected now, rather than every SQL driver Qt offers, and the Qt plugins are given the right rpath depth so they resolve from inside the bundle.

---

Installing

Every download has a .sha256 beside it, and checking one is worthwhile because these builds are not code signed:

• Windows shows SmartScreen. Choose More info, then Run anyway.
• macOS is refused by Gatekeeper on first open. Right-click the app, choose Open, then confirm. Apple Silicon only.
• Linux has no equivalent gate.

There is no in-app updater, so upgrading means downloading again.

The qbittorrent-nox source archive is attached alongside the installers, which is what GPLv3 section 6(d) asks for: the source available from the same place as the binary.

The first release of rigseed: a desktop client for qBittorrent that brings its own daemon.

There is nothing to install first and no server to configure. qbittorrent-nox ships inside the app, bound to loopback, and rigseed generates its own WebUI credentials on first launch, so there is no password to invent and no port to open. If you already run qBittorrent, rigseed reads and writes the same configuration: your categories, save paths, limits and trackers are the ones you already have, and the old interface is still there whenever you want it.

Every screen prints the endpoints it drives, because a client that hides its transport is a client you cannot debug.

Windows and macOS. Linux is not in this release: the bundled daemon inherited the build machine's glibc and would not start on Ubuntu 22.04. It arrives in 0.1.1.

---

Installing

Every download has a .sha256 beside it, and checking one is worthwhile because these builds are not code signed:

• Windows shows SmartScreen. Choose More info, then Run anyway.
• macOS is refused by Gatekeeper on first open. Right-click the app, choose Open, then confirm. Apple Silicon only.

There is no in-app updater, so upgrading means downloading again.

The qbittorrent-nox source archive is attached alongside the installers, which is what GPLv3 section 6(d) asks for: the source available from the same place as the binary.