Foreseerr is a personal fork of Seerr that folds SuggestArr-style discovery and media workflows into the app itself — Trakt browse, richer ratings, and more — without running a separate suggestion sidecar.
It keeps Seerr’s request pipeline, media-server integrations (Jellyfin / Plex / Emby), and Radarr/Sonarr support. Config paths stay Seerr-compatible (CONFIG_DIRECTORY, Docker /app/config).
Jellyfin-first. Foreseerr’s deeper features — Library / Watch Now, native Desktop playback, Jellyfin watched actions, and the Better Trakt bridge — are built and tested around Jellyfin. Plex and Emby remain supported for Seerr-style sign-in, library scans, requests, and availability. Cross-server features such as Direct Trakt, rating badges (e.g. MDBList), Discover, and the request pipeline work regardless of media server. Full Library and Desktop parity for Plex/Emby is not a current priority; please treat those as best-effort.
Docs: selmant.github.io/foreseerr
Foreseer Desktop is the optional native companion for Foreseerr. It loads the same hosted Foreseerr UI in a desktop window and, for supported Jellyfin playback, uses the maintained Jellium runtime fork to play in that window. It is not required for normal browser use, requests, library browsing, or any server-side feature.
The desktop binary never replaces this web application: browsers keep their normal Jellyfin links, while a compatible desktop runtime adds native playback only after the signed-in user's account is linked to Jellyfin. See the native desktop guide for the user-facing behavior and Foreseer Desktop for installation and release compatibility.
Note
Foreseerr v0.5.0 is the current stable release. Upgrades from v0.1.0, v0.2.0, v0.2.1, v0.3.0, and v0.4.x are supported. Alpha builds (0.1.0-alpha.x) are not a supported upgrade source — start from a fresh install or migrate from Seerr (see the migration guide). Back up your configuration before upgrading.
- Full Jellyfin/Emby/Plex integration including authentication with user import & management.
- Support for PostgreSQL and SQLite databases.
- Movies, shows, and mixed libraries.
- Sonarr and Radarr integration with a customizable request system.
- Library scans, granular permissions, notification agents, watchlist & blocklist.
- Mobile-friendly UI.
Near-term additions on top of Seerr (see the Foreseerr master plan):
- Trakt browse (recommendations, lists, watchlist) with manual requests
- Multi-source rating badges
- Trakt watched / unwatched / user score actions
- Further SuggestArr parity as Discover/settings — not auto-request jobs by default
AI / LLM recommendation features are explicitly out of scope unless reopened.
Foreseerr is currently distributed as a Docker image. Docker and Docker Compose must be installed on the host; see the Docker installation guide if needed.
Create a persistent directory for Foreseerr’s configuration. The container runs as UID/GID 1000, so make sure it can write to this directory:
mkdir -p ./foreseerr-config
sudo chown -R 1000:1000 ./foreseerr-configStart the released image:
docker run -d \
--name foreseerr \
--init \
--restart unless-stopped \
-p 5055:5055 \
-v "$(pwd)/foreseerr-config:/app/config" \
ghcr.io/selmant/foreseerr:v0.5.0Open http://localhost:5055 and complete the setup wizard. Keep the /app/config volume when updating or recreating the container; it contains your database and settings.
To update, replace the image tag with the version you want, then recreate the container with the same volume mount. Back up foreseerr-config before updating.
The equivalent production-style Compose service is:
services:
foreseerr:
image: ghcr.io/selmant/foreseerr:v0.5.0
container_name: foreseerr
init: true
restart: unless-stopped
ports:
- "5055:5055"
volumes:
- ./foreseerr-config:/app/configStart it with:
mkdir -p foreseerr-config
sudo chown -R 1000:1000 foreseerr-config
docker compose up -dThe image is published at ghcr.io/selmant/foreseerr. Prefer an explicit version tag (v0.5.0) or a stable alias (latest, v0, v0.5) rather than develop.
Older pulls used
ghcr.io/selmant/seerr. Point compose/CLI atghcr.io/selmant/foreseerrgoing forward.
Foreseerr uses Seerr-compatible config paths and database settings, so an existing Seerr configuration can be reused when replacing Seerr. Stop the existing instance first, back up its config/database, and do not run both instances against the same config directory or database.
See the migration guide for the evergreen replacement procedure (clone-test, then same /app/config volume), supported upgrade sources, and what to do if your Seerr is newer than Foreseerr’s last upstream sync.
With a running instance: http://localhost:5055/api-docs
Foreseerr tracks seerr-team/seerr. This fork’s remote is selmant/foreseerr.
MIT (same as Seerr).