NEWv0.2.0: errors explained, one-line install

Torrents, finally at home on Omarchy.

A native client for one server or many. Your theme, your keys, your seeding history. Powered by qBittorrent.

$ curl -fLO https://github.com/diogochaves/omaseed/releases/latest/download/omaseed-x86_64.pkg.tar.zst && sudo pacman -U omaseed-x86_64.pkg.tar.zst

Seed console

See what you give back. qBittorrent counts your uploads but keeps no history of them. omaseed keeps its own, so a year of seeding is one key away.

The tide

Upload over time, from the last hour to the last year.

The tide

The year

A cell for every day of the last year, and the streak you're on.

Keeping alive

The torrents few others still seed, rarest first.

Trackers

What you've given to each tracker, for the ones that count it.

Ratio ladder

Every torrent by its ratio, against the line where it has paid back what it took.

Everything above is demo data on this page. omaseed writes the real history to ~/.local/share/omaseed/ledger/ on your machine, so it stays when a server is replaced, and backs it up with the rest of its settings.

Adding torrents

It knows your library before you add. The add sheet looks at your Downloads folder, your disk and what you already seed, so nothing is downloaded twice.

Your newest downloads

The newest .torrent files in Downloads are waiting when you open it. Tick several to add them together.

Files already on disk

When another torrent already has the same files on disk, one click saves this one beside them, and it seeds without downloading.

Already in your library

A torrent you already have is caught before it's added. A public one's new trackers can be merged into it.

Room on the disk

What it needs and what's left on that drive: yellow when it leaves little, red when it won't fit.

Any server

This PC, a NAS, or all of them at once. omaseed is a window onto qBittorrent wherever it runs.

Finds the one on this PC

First run looks for a qBittorrent on this machine and signs in, or offers to install one.

Or any on the network

A NAS, a seedbox, the machine under the desk: qBittorrent 5.2 or newer with its Web UI on.

Several at once

Add as many servers as you run, and switch between them from the rail, the top of the window or the tray.

Signs in your way

An API key, a username and password, or nothing for a server that lets localhost in. Secrets go to the system keyring.

Self-signed HTTPS

omaseed shows the certificate's fingerprint and trusts that one certificate once you say so.

Opens what you click

Magnet links and .torrent files open in omaseed, from the browser, the clipboard, a drag or your Downloads folder.

Omarchy

It looks like the rest of your desktop. omaseed reads your Omarchy theme and repaints the moment it changes. Pick a theme under the window above and this page does the same.

In your bar

The mark in the bar is the readout: the down arrow lights while downloading, the up arrow while seeding, the square says how the server is. Click it for the popup.

Speaks up when it matters

A finished download, a server that went away and came back, a disk filling up.

Keyboard first

Every action has a key, and ? lists them all, with a filter. The mouse works everywhere too: right-click menus, drag and drop, double-click for details.

Every theme, live

All 22 bundled themes, the light ones too, with your font, base size, transparency and window rounding.

In the Omarchy menu

A Torrents row for the menu, and a window rule so its translucent window looks right.

Any Linux, too

Built for Omarchy, and runs on any Linux with a bundled theme when Omarchy isn't there.

Careful with your data

It asks before it costs you a seed. Deleting files another torrent still seeds, or the last copy anyone has, gets a question first.

Shared files

Two torrents seeding the same files: deleting one asks whether the other keeps them.

The last seed

If you are the only one still seeding it, omaseed says so, and offers to stop it instead.

Why it errorednew in 0.2.0

qBittorrent's API never says why a torrent stopped. omaseed reads qBittorrent's log and says it in plain words, with the keys that fix it.

Powered by qBittorrent

omaseed has no torrent engine of its own. qBittorrent does the transferring, on this machine or another, and omaseed is the window you see it through.

omabox

Built with omabox

No desktops were harmed in the making of omaseed. And no mouse was captured. Every window, scale and multi-monitor check ran inside omabox, an invisible Omarchy desktop, so the AI agent building omaseed never touched the desktop it was building for.

omabox.app

# the walks in omaseed's repo, each run in a box
scripts/dev/actions-walk.sh
scripts/dev/error-walk.sh
scripts/dev/magnet-walk.sh
scripts/dev/notify-walk.sh
scripts/dev/servers-walk.sh
scripts/dev/settings-walk.sh
scripts/dev/strict-walk.sh
scripts/dev/swarm-walk.sh

New in omaseed

Changelog. Every release, dated.

v0.2.013 Oct 2026

Errors explained, the mouse everywhere, one-line install

An errored torrent says why. qBittorrent's API never gives the reason, so omaseed reads qBittorrent's log: "Can't write to its save folder", "The disk is full", and the actions that fix it. The table reads the short cause, "no access" or "disk full".
A notice when a torrent stops with an error, with the reason; a click shows it.
Everything works with the mouse. One set of click rules for every list, right-click menus, clickable key hints, double-click for details, drop to add.
Installs with one line. Each release ships a prebuilt package: no build, pacman pulls the rest.

v0.1.010 Oct 2026

First release

The library. A dense, keyboard-first table with 29 columns to choose from, a rail of filters, palettes, and a details pane with files, trackers and peers.
Adding torrents. Magnets, .torrent files, the clipboard or a drag; it spots duplicates and files already on disk it can seed from.
The seed console. Upload over time, ratios, a year of seeding days, the torrents you keep alive.
Omarchy. Follows the theme live, a bar widget, the tray, notifications.
Servers. First run finds qBittorrent; several servers; secrets in the keyring; backups of its own.

The whole changelog

What's next

Open on GitHub. Work that's planned, as the issues name it. No dates.

Open source

MIT licensed, built in the open. Read the code, report a bug, ask for a feature or send a pull request. Contributions are welcome.

Codediogochaves/omaseedC++20 and Qt 6 Quick, a native Linux app IssuesReport a bug or ask for a featureWhat's planned is there too Pull requestsSend a changeFixes, features, a theme that looks off LicenseMITUse it, change it, share it

Install

Install omaseed.

On Arch and Omarchy: one line downloads the latest release, already built, and installs it. You need qBittorrent 5.2 or newer with its Web UI on, on this machine or another.

$ curl -fLO https://github.com/diogochaves/omaseed/releases/latest/download/omaseed-x86_64.pkg.tar.zst &&
  sudo pacman -U omaseed-x86_64.pkg.tar.zst

pacman pulls Qt and the rest of what omaseed needs from the Arch repos. omaseed isn't in a repo yet, so pacman -Syu doesn't update it: for a new release, run the same line again. First run finds your qBittorrent, or offers to install one.

Build from source instead

$ git clone https://github.com/diogochaves/omaseed.git
$ cd omaseed/packaging/arch
$ makepkg -si

makepkg -si asks for your password: pacman installs the build dependencies, then omaseed.

diogochaves/omaseed