Autobrr vs autodl-irssi: Which Should You Use in 2026?

Both tools do the same job — sit on a private tracker’s IRC announce channel, match new releases against your filters, and push the ones you want into your client within a second or two of them being posted. autodl-irssi has been doing it since 2010. autobrr is the modern rewrite. Both are available on your Evoseedbox seedbox, so the question is which one to actually use.

The short answer

Use autobrr unless you have a working autodl-irssi setup you do not want to touch, or you use a tracker autobrr does not have a definition for yet. It is a single Go binary with a real web interface, it does not need irssi running behind it, and its filters are easier to get right.

Where they actually differ

What has to be running

autodl-irssi is an irssi script. That means an irssi process has to stay alive in a screen session for your account, and the ruTorrent plugin talks to it over a local socket. Two moving parts, and the failure mode is confusing: the ruTorrent panel says Connection refused, which looks like a network problem but nearly always means the irssi backend is not running for your account. Autobrr is one process with its own web UI and no client-side plugin at all.

Filters

autodl-irssi filters live in a text file with a long list of keys — match-releases, except-releases, resolutions, max-size, and so on — edited either by hand or through the ruTorrent dialog. Autobrr gives you a form per filter with the same concepts plus a few autodl never had: size ranges with units, per-filter download clients, smart episode handling, and a “duplicate” check so you do not grab a release you already have in another quality.

Seeing why something did not match

This is the real gap. Autobrr logs every announce it saw and shows, per filter, exactly which condition rejected it. With autodl-irssi you turn up the log level and read irssi output. If you have ever spent an evening wondering why a filter that looks right never fires, this alone decides it.

Tracker coverage

autodl-irssi’s tracker definitions have been maintained for well over a decade, and there are more of them, including some small trackers nobody has written an autobrr definition for. Autobrr covers the large private trackers well and adds new ones steadily, but if your tracker is obscure, check its definition exists before you migrate.

Cross-seeding and the rest of the stack

Autobrr talks to other tools directly — it can hand a release to a specific client with a specific label, and it fits naturally next to Sonarr and Radarr. autodl-irssi’s world ends at “put this torrent in the client”.

Migrating without losing your filters

There is no importer, and that is fine — filters do not translate cleanly anyway. The practical route:

1. Install autobrr from the Apps page in your client area and open it.
2. Add your trackers as Indexers, pasting the same IRC credentials and passkeys autodl-irssi already uses.
3. Add ruTorrent as a Download Client.
4. Rebuild your two or three most important filters by hand, and leave autodl-irssi running while you do.
5. Watch autobrr’s activity feed for a few days. When it is catching what autodl caught, turn autodl-irssi off.

Running both at once is safe — worst case they both grab the same release and the second one fails as a duplicate.

If you are staying on autodl-irssi

One thing worth knowing: if the ruTorrent autodl panel reports Connection refused, the plugin is fine and the irssi backend is not running for your account. Open a ticket and we will restart it — it is a one-line fix on our side, and it is not something you can trigger from the plugin.

Neither, if you only need RSS

If your tracker publishes an RSS feed and you are not racing, you do not need either tool. A Liteflow RSS flow with an include and an exclude pattern covers “grab every 1080p episode of this show” with nothing to keep running. IRC announce only matters when seconds do.