Fliks 7.0 just shipped, so it felt like the right time to post here.
Holyarrs, posted here a while back, leaves playback to other apps. I went the other way: for Fliks the hard part was the playback itself, transcoding on the fly and native apps on every screen in the house.
What it is
Point Fliks at the folders holding your videos, music and books, and you get a streaming service for the household: profiles, Continue Watching, and an app on every screen. Start a film on your phone and the TV picks it up where you left off. When a device can't play the original file, Fliks transcodes on the fly (Intel, NVIDIA, AMD, Apple) and tone-maps HDR and Dolby Vision for screens that can't show them.
The whole *arr suite, in one app
Sonarr / Radarr: movie and series monitoring, an episode calendar, indexer search, download clients and the grab pipeline.
Lidarr: music organised by MusicBrainz release, with per-track requests. New in 7.0.
Readarr: books, audiobooks and comics, a built-in EPUB and PDF reader that works offline, and Kobo sync.
Bazarr: finds subtitles that match your exact copy, fixes the sync in one click by listening to the dialogue, translates a track with the engine you pick (Gemini, OpenAI-compatible, LibreTranslate), and turns image subtitles into text with OCR.
Overseerr: requests, with quotas per media type.
Tdarr: optimization profiles with a preview of what will change, a job queue, and remote workers on your other machines. The originals go to a trash you can restore from. New in 7.0.
Tautulli: a live dashboard of who's watching what and why a transcode was needed, plus a verdict for every session that stutters (network, weak device, transcode too slow).
Maintainerr: cleanup rules, a Leaving soon row, and reminders before anything is deleted.
On top of that: Live TV from your own IPTV (M3U or Xtream) with a guide and a rewind buffer, watch parties with synced playback and push-to-talk, shared playlists, commercials skipped from .edl files, and offline downloads that keep themselves current.
Plugins
A good part of it runs through plugins: downloading, and the metadata providers (TMDB, TVDB, MusicBrainz, OpenLibrary, lyrics). They are signed WebAssembly components, sandboxed, each with its own Postgres role, and the official Fliks source comes preconfigured. There is documentation for writing your own. Full disclosure: I've never read it.
Karaoke (new in 7.0)
Any song in your music library becomes karaoke. Fliks separates the vocals from the backing track, reads the melody from the audio and draws its notes, aligns the lyrics word by word, scores your pitch, and handles duets and key changes. Phones join as microphones and a singer queue keeps the evening going. UltraStar and CD+G files work too, on the TV, the Apple TV and the Chromecast.
Clients
Web, iOS, Android, Android TV, Apple TV (native SwiftUI), Samsung, LG, desktop (Windows, macOS, Linux), Chromecast, Android Auto, CarPlay, and a homebrew Nintendo Switch client in beta. Most of them are on the official stores (App Store, Play Store, LG Content Store, Snap Store).
The engine is its own project
I split the streaming engine out on purpose so other open-source projects can use it. It makes the playback decisions, runs the transcoding sessions and serves the segments, all behind a versioned HTTP API with an OpenAPI spec. It has no database and no user model: the host app decides who sees what, and the host can be written in any language. If you're building a media app and don't want to fight FFmpeg and per-device codec quirks yourself, take it: github.com/fliks-app/engine (AGPL, Docker image included).
The numbers: first POCs in March, repo created in May. 2,500+ merged PRs, around 470k lines of Rust, TypeScript, Swift and Kotlin.
How I work with Claude Code
It's not "one prompt, one app". What ended up working:
Opus thinks, Sonnet types. Design, plan reviews and code reviews go to Opus; implementation agents run on Sonnet.
Big features start as a written plan split into batches. Each batch gets its own session, its own git worktree and its own PR, and an Opus agent reviews every batch before it merges.
A CLAUDE.md of hard rules, each one written after a bad week: fix the root cause, never patch around it; delete a fix that turned out useless; two-line comments max; every piece of state lives in one place.
A memory folder of ~200 one-fact files: device quirks, past decisions, "this was removed on purpose, don't bring it back".
CI and release-please on every PR, plus a parity suite that checked the Rust rewrite of the backend (it started in NestJS).
What AI is still bad at
Real devices. A Samsung TV that ignores an audio-track switch, an LG that merges every audio track of the same language into one: no agent sees that. I test on real hardware (Android phone, Android TV, Samsung and LG TVs, Windows, a Mac mini and a MacBook), plus Apple TV and car screens in emulators. The LG and Android WebViews are driven over the Chrome debug protocol, so Claude reads their logs itself.
Silent guards. By far the most common bug: an if that quietly drops an error or an event instead of failing loudly. It's the first thing I look for in a review now.
Workarounds. Left alone, it patches the symptom where it shows up. Half my rules exist to stop that.
Parallel agents in one checkout. One git stash and another agent's work is gone. Worktrees fixed that.
Site: fliks.media · Code: github.com/fliks-app/fliks (AGPL)
See the documentation: docs.fliks.media
Happy to answer questions about the setup, the engine, or the TV ports.