You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It sits in the same slot as Transmission and SABnzbd, so it doesn't add any new tools. Your qBittorrent downloads just show up in the existing ones. Config is the same as Transmission, a URL plus username and password, no API key. Both credential fields are optional, so if you have "bypass authentication for clients on localhost" turned on it won't try to log in at all. You can also run it alongside Transmission if you happen to have both; the queues merge and every item says which client it came from.
Big caveat though: this has not been tested against a real qBittorrent yet. I wrote it against the documented WebUI API, and the test fixtures are hand written rather than captured from an actual instance, so there is a decent chance something is off in the details. The bits I'd expect to break first are the cookie login (especially if you're behind a reverse proxy or have CSRF/host header validation turned on), and the state mapping if you're on 4.x rather than 5.x, since they renamed the paused states.
So I'd really love feedback here. If you (or anyone else reading) can point it at your setup and tell me what happens, that would help a lot.
These are the five tools that should now know about qBittorrent, roughly in the order I'd poke at them:
the config UI service test, first thing. Does it connect at all, and what does it say if it doesn't
stack_health, should report a version and a free space row for your save path
get_queue, should list your torrents with sensible status, size and ETA. This is the one I most expect to have rough edges
diagnose, qBittorrent is now part of the chain it walks
remove_queue_item and clean_queue, only if you're feeling brave, since those actually delete things. Both preview first and need a confirm token, so nothing happens on the first call
Also useful to know: what version of qBittorrent you're on, and whether you reach it directly or through a reverse proxy.
Activity
bardesss commentedon Aug 18, 2026
Good news, qBittorrent support is up in #150.
It sits in the same slot as Transmission and SABnzbd, so it doesn't add any new tools. Your qBittorrent downloads just show up in the existing ones. Config is the same as Transmission, a URL plus username and password, no API key. Both credential fields are optional, so if you have "bypass authentication for clients on localhost" turned on it won't try to log in at all. You can also run it alongside Transmission if you happen to have both; the queues merge and every item says which client it came from.
Big caveat though: this has not been tested against a real qBittorrent yet. I wrote it against the documented WebUI API, and the test fixtures are hand written rather than captured from an actual instance, so there is a decent chance something is off in the details. The bits I'd expect to break first are the cookie login (especially if you're behind a reverse proxy or have CSRF/host header validation turned on), and the state mapping if you're on 4.x rather than 5.x, since they renamed the paused states.
So I'd really love feedback here. If you (or anyone else reading) can point it at your setup and tell me what happens, that would help a lot.
What to try
Docs on the branch, if you want the detail: README, tool reference, configuration.
These are the five tools that should now know about qBittorrent, roughly in the order I'd poke at them:
stack_health, should report a version and a free space row for your save pathget_queue, should list your torrents with sensible status, size and ETA. This is the one I most expect to have rough edgesdiagnose, qBittorrent is now part of the chain it walksremove_queue_itemandclean_queue, only if you're feeling brave, since those actually delete things. Both preview first and need a confirm token, so nothing happens on the first callAlso useful to know: what version of qBittorrent you're on, and whether you reach it directly or through a reverse proxy.
Happy to iterate on it. Thanks for the request!
feat: add qBittorrent as a download client (#150)
bardesss commentedon Sep 6, 2026
Closing this issue. More about qBittorrent in #195.
feat: add qBittorrent as a download client (#150)