Engineering case study / Electron + qBittorrent Web API

A qBittorrent remote with operational context.

Qubit starts with qBittorrent's Web API and adds the server, path, content, and media context needed to operate it from one keyboard-friendly desktop workspace.

Version
v1.0.0
Platform
Windows x64
License
MIT licensed
QUBIT / TORRENTS connected

Connected servers

home-lab seedbox media-box
All torrents4 items

Illustrated torrent list

Dune.Part.Two.202418.2 GB72%
The.Bear.S034.8 GBdone
Linux.ISO.collection9.1 GB31%
Archive.2026.062.4 GBpaused

selected / transfer

4.6 MB/s ↓

media match

preview
Illustrated Qubit application surface showing a server switcher, torrent list, detail panel, and preview area.

From API surface to working tool.

This project sits at the other end of my consultancy spectrum: a focused desktop application built around an existing service boundary. The engineering work is making server state, transfer operations, content structure, and media context explicit in one workflow.

01 / CONNECTIONS

Make the server boundary visible.

Keep per-server credentials, default save paths, categories, and local path mappings together. Move between a home machine, remote host, or media box while retaining the operational settings that shape each connection.

home-lab192.168.1.20● online
seedboxremote / mapped● online
media-boxlocal library● online
Illustration of three Qubit server cards.
02 / OPERATE

Turn API records into operations.

Manage start, stop, force start, recheck, reannounce, and removal from the live list. The detail panel adds general information, trackers, peers, and a navigable content tree with per-file priorities and download toggles.

content tree

▾ Dune.Part.Two▾ videoscene-01.mkvscene-02.mkv

detail

generaltrackerspeersfiles 12 / 18
Illustration of Qubit detail and content panels.
03 / INTAKE + MEDIA

Connect intake to media-aware controls.

Add a torrent from a file or magnet, catch duplicates by infohash, and optionally merge trackers. When content lands in a tagged Stash or Plex folder, Qubit can match it against the library and expose the relevant preview or playback controls.

Drop a .torrentor paste a magnet linkadd paused · tracker merge

matched media

Scene player readyexact oshash match
STASH / MOVIE
Illustration of adding a torrent and matching media.

Built around the desktop

A remote with enough context to be useful.

qBittorrent's Web API remains the centre of the system. Qubit adds the operational context around it: connection settings, transfer state, content structure, path mappings, and media-aware controls in one desktop surface.

↳ 01

API-backed transfer control

Delta-polled torrent data, sortable and resizable columns, folder grouping, and explicit per-row actions.

↳ 02

Media-aware controls

Sidecar screenshots, direct image previews, and in-app playback for content matched to Stash or Plex libraries.

↳ 03

Windows-native handoff

Package Qubit for Windows with .torrent and magnet associations through the Default-Apps picker flow.

Current source release

Qubit 1.0.0

This is a focused consultancy artefact: a small Windows desktop client that turns an existing qBittorrent service boundary into a more complete operator workflow. The repository package manifest identifies the current version as 1.0.0, with an x64 NSIS installer and an x64 ZIP archive configured through electron-builder.

Build targets

NSIS / x64ZIP / x64Electron