autobrr/qui

A fast, single-binary qBittorrent web UI: manage multiple instances, automate torrent workflows, and cross-seed across trackers.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 20 minutes ago
Added to GitGenius on September 15th, 2026
Created on August 4th, 2025
Open Issues & Pull Requests: 81 (-3)
GitHub issues: Enabled
Number of forks: 154
Total Stargazers: 4,526 (+0)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.7 hours
Mean response time: 6.6 days
90th percentile: 16.9 days
Tracked items: 413

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 67% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "refactor" is answered fastest, typically in under an hour, while "config" waits about 2 days. Almost all tracked open issues have seen activity in the last three months. 88% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 61
New in 7 days: 28
Closed in 7 days: 11
Avg open age: 28 days
Stale 30+ days: 6
Stale 90+ days: 1

Recent activity

Opened in 7 days: 27
Closed in 7 days: 9
Comments in 7 days: 1
Events in 7 days: 25

Top labels

  • web (271)
  • enhancement (241)
  • bug (141)
  • backend (118)
  • ready-for-agent (93)
  • cross-seed (45)
  • config (43)
  • refactor (23)

Detailed Description

Qui is a web UI for qBittorrent that runs as a single compiled binary and enables management of multiple qBittorrent instances alongside torrent workflow automation and cross-seeding across trackers.

The tool addresses the limitations of qBittorrent's default web interface by providing a faster, more capable alternative built in Go. It allows users to connect to and control multiple qBittorrent instances from one dashboard, automate torrent-related workflows, and coordinate cross-seeding activities across different torrent trackers. The single-binary distribution model simplifies deployment without requiring separate dependencies or complex setup procedures.

Qui suits users who run multiple qBittorrent instances or need to orchestrate torrent operations across several trackers. It works well in self-hosted environments and integrates with the broader *arr ecosystem (Radarr, Sonarr) and autobrr for enhanced automation. The project is particularly valuable for those managing cross-seeding strategies where torrents need to be distributed and managed across multiple tracker communities simultaneously. Developers and power users who want programmatic control over qBittorrent workflows rather than manual web interface interaction will find the automation capabilities most useful.

The project shows consistent development activity with regular commits addressing bug fixes, feature additions, and performance improvements. Pull requests receive timely review and integration. The maintainers actively respond to issues and incorporate user feedback into the roadmap. Documentation is maintained alongside code changes to reflect current functionality. The project demonstrates sustained engagement with its user base through issue resolution and feature development rather than periods of inactivity.