It works on the real system
The agent has a shell and file access inside its container. It can look at a messy download and fix it, without anyone having written a tool for that case.
Self-hosted · Open source · MIT
An agent-native copilot for your film, TV and anime collection. It finds the title, picks a release, downloads it, files it into your library and fetches the subtitles, on your own NAS, with the tools you already run.
Works with qBittorrent, Jackett and Jellyfin. Runs on your own NAS.
Get me Sintel, the 2010 Blender film.
A young woman searches far and wide for a small dragon she once looked after.
Sintel.2010.1080p.BluRay.x264-GRP
1080pBluRayx2641.2 GB↑ 40Picked1080p BluRay, well seeded, subtitle inside.
Sintel.2010.2160p.WEB-DL.x265-OTHER
2160pWEB-DLx2654.0 GB↑ 12
Sintel.2010.1080p.CAM.x264-NOPE
1080pCAM668 MB↑ 300SkippedA camera recording.
Sintel is in your library, with a Chinese subtitle beside it. It keeps seeding from where it was downloaded. in library
The whole path from a name to a title you can play, done by one agent that can see every step.
From anything: a name, a TMDB or Douban link, a magnet, a photo of a poster.
Every indexer at once. Reelix looks inside a release before trusting its name.
With qBittorrent. Why this release was chosen is written down when it is added.
Hard links into a Jellyfin-standard library. Nothing is copied; seeding goes on.
Found, checked against the video, cleaned and placed. Or translated when none exists.
A standing instruction in your own words. New episodes arrive as they air.
Most tools in this space are rule systems with a chat box added. Reelix is the other way round.
The agent has a shell and file access inside its container. It can look at a messy download and fix it, without anyone having written a tool for that case.
Reading an odd release name or choosing between releases goes to the model, guided by a plain note of your taste. Exact code stays where a mistake costs something.
And remembers the answer. Questions, plans and notices wait in one Inbox, on the web, as a push notification or in Telegram.
Finding and filing is the core. These come with it.
On the web, in the terminal and in Telegram. The same agent, with the same note of your taste.
When none exists, Reelix translates one with your own models into a separate file. The video is never touched.
What is trending, the anime airing now, and picks based on what you watched in Jellyfin.
Questions and plans arrive as a notification on your phone or in Telegram. Answer from wherever you are.
Existing downloads are scanned and filed into the library, once you approve the plan.
Two themes and your own, four languages, and any model provider you like.
Real screens from a demo instance: fake services, a real agent.
Almost everything that talks to an outside service is a plugin. Switch them on and off in Settings, install new ones, or ask Reelix to write one for you.
Be the thing Reelix calls.
Change a decision as it is made.
Operations with a declared effect, a screen in the web UI, a pack of skills for the agent.
Want to build one? Read the plugin guide →
In conversation the agent does what you ask. A few things are fixed in code, because they are about correctness and cost, not permission.
Destructive actions need your approval. An approval is tied to the exact request and cannot be replayed.
Release names, web pages and subtitle contents are marked as outside text and never treated as instructions.
Every operation, whoever ran it, leaves one record in the ledger: what, by whom, with what result.
Removing a title removes a link. A last remaining copy goes to a trash that is kept for 14 days.
Keys and passwords are typed into a secret field. They never reach the model or a saved conversation.
Background work stops at a daily limit you set, and each plugin that uses your models has a budget of its own.
English · 简体中文 · Français · Русский
Reelix runs in one container beside your existing services. A pre-flight script checks your NAS first.
$ git clone https://github.com/4444zyf/Reelix.git && cd Reelix
$ sudo bash preflight/reelix-preflight.sh # finds your services, tests hard links, prints a .env
$ cp .env.example .env # then put in what the pre-flight printed
$ docker compose up -d # Reelix is at http://<nas>:7878
$ docker compose exec reelix pi # sign in to a model provider
$ npm install
$ npm run web:build # the web UI
$ export REELIX_DATA=$PWD/.dev-data
$ bin/reelix config set models.roles.chat provider/model-id
$ bin/reelix serve # the first visit sets the password
$ export REELIX_DATA=/tmp/reelix-try REELIX_PI_DIR=~/.pi/agent
$ export REELIX_DEMO_PASSWORD=choose-one REELIX_DEMO_MODEL=provider/model-id
$ node --no-warnings --disable-sigusr1 scripts/demo.ts # fake services, a real agent
Reelix is pre-release software. It has not yet had a long run on a NAS, and the plugin API is still version 0. Expect changes.