Jellyfin Infinity

Jellyfin plugin for federated media search across the local Jellyfin library, resolver-backed on-demand media, and configured remote providers.

The current implementation includes:

• Plugin scaffold with configuration and admin page registration.
• Custom API endpoints under /Infinity.
• Source adapter model with capability discovery.
• Search sources for the local library, resolver-backed music/video, AIOStreams, TMDb, MusicBrainz, and manual Torznab/Prowlarr candidates.
• Native Jellyfin /Search/Hints, /Items, /Artists, detail, children, playback, artwork, and subtitle augmentation for resolver-backed on-demand music and video.
• Ranking, deduplication, source health, partial failure reporting, and request privacy controls.
• Dockerized Chromium/CDP verification for the real Jellyfin Web interface.
• Documentation for API contracts, source adapter development, and testing.

The current native replacement path covers on-demand music and video search, details, playback handoff, resolver-backed artwork, and subtitle lookup. Resolver-backed media paths are accepted only under configured safe music/video roots. If a resolver item is queued, downloading, waiting for scan, unavailable, or mismatched, Infinity returns a structured status payload for the web overlay instead of allowing raw Jellyfin playback errors to surface.

Status

This is a local plugin build installed into the active Jellyfin 10.11.11 configuration. The repository includes smoke tooling for real Jellyfin Web verification.

Target

• Jellyfin server: 10.11.x first.
• Runtime: .NET 9.
• Client integration: custom API plus native Jellyfin search response augmentation for compatible clients.

Build

dotnet restore Jellyfin.Plugin.Infinity.sln
dotnet build Jellyfin.Plugin.Infinity.sln
dotnet test Jellyfin.Plugin.Infinity.sln

Nix

nix develop
nix flake check
nix build .#plugin
nix build .#release
nix run .#verify-infinity-status-patch

The flake fetches Jellyfin 10.11.11 reference assemblies from the official portable server archive, so the ignored local lib/ directory is not required for Nix builds. The dev shell also provides Python, Node.js, Chromium, and verification wrappers:

verify-infinity-status-patch
verify-jellyfin-web-ui-cdp --base-url http://10.1.11.21:8096 --db /jellyfin.db --out-dir /out --query Deadmau5
verify-on-demand-status-ui --base-url http://10.1.11.21:8096 --credentials /path/to/credentials.json --out-dir /out
verify-infinity-parity --base-url http://10.1.11.21:8096 --credentials /path/to/credentials.json --out-dir /out

The live Chromium/CDP wrappers pass the Nix-provided Chromium binary to the Python scripts. Set INFINITY_CHROME=/path/to/chrome when testing against a different browser binary.

Releases

Stable releases are generated by pushing a semantic version tag such as v1.0.0. The tag version is written into the plugin meta.json, release manifest, artifact name, and download URL.

Nightly releases are generated by pushing to the indev branch. The release workflow creates a prerelease tag using UTC month/day/year/hour/minute format, for example v61620261017. The Jellyfin plugin version and artifact name use the compatible dotted form, for example 6.16.2026.1017, and publish the same installable plugin zip, checksum, and manifest assets as a stable release.

Every indev push also refreshes the moving indev-latest prerelease. Use that channel on development or test Jellyfin servers when you want a fixed repository URL that always points at the newest indev build.

Install a Release

Use a release whose targetAbi is compatible with your Jellyfin server. This plugin currently targets Jellyfin 10.11.11 and publishes that three-part ABI string so servers reporting 10.11.11 do not reject the package as newer than the running server.

Install From the Jellyfin Catalog

1. Open the Jellyfin dashboard as an administrator.

2. Go to Plugins > Repositories.

3. Add a repository named Infinity with the release manifest URL:

   https://git.ds.reinitialized.net/reinitialized/infinity/releases/download/<release-tag>/manifest.json
   

   Replace <release-tag> with the stable or nightly release tag, for example v1.0.0 or v61620261017.

   To track the newest indev build instead, use the moving channel manifest:

   https://git.ds.reinitialized.net/reinitialized/infinity/releases/download/indev-latest/manifest.json
   

   Only use indev-latest on development or test servers. Indev builds use timestamp-based versions that may sort newer than stable releases.

4. Save the repository, then go to Plugins > Catalog.

5. Select Infinity, install the available version, and restart Jellyfin when prompted.

6. After Jellyfin restarts, confirm Infinity appears under Plugins > My Plugins.

If Jellyfin logs Plugin "installed": "Infinity" but Infinity disappears after restart, check the startup log for Registering whitelisted assemblies for plugin "Infinity" and Loaded plugin: "Infinity". If those lines are absent, Jellyfin did not discover a loadable Infinity_* folder under its program-data plugins path. Remove stale or partial Infinity_* directories from that path and reinstall. For the official container this path is usually /config/plugins; for package installs it is usually /var/lib/jellyfin/plugins.

Install Manually

1. Download these assets from the release page:

   • Jellyfin.Plugin.Infinity_<version>.zip
   • Jellyfin.Plugin.Infinity_<version>.zip.sha256

2. Set the plugin version from the release asset name:

   VERSION=1.0.0
   PLUGIN_DIR="/var/lib/jellyfin/plugins/Infinity_${VERSION}"
   

3. Verify the archive before installing it:

   sha256sum -c "Jellyfin.Plugin.Infinity_${VERSION}.zip.sha256"
   

4. Stop Jellyfin.

5. Create a plugin directory under the Jellyfin configuration directory:

   sudo mkdir -p "$PLUGIN_DIR"
   

   For Docker installs, use the host path that is mounted as the container's Jellyfin config directory. The plugin directory inside that config mount is usually plugins/Infinity_${VERSION}.

6. Extract the release archive into that directory:

   sudo unzip "Jellyfin.Plugin.Infinity_${VERSION}.zip" -d "$PLUGIN_DIR"
   

7. For package-based Linux installs, make sure Jellyfin owns the extracted files:

   sudo chown -R jellyfin:jellyfin "$PLUGIN_DIR"
   

8. Start Jellyfin, then confirm Infinity appears under Plugins > My Plugins.

Web Verification

With Nix:

nix run .#verify-jellyfin-web-ui-cdp -- \
  --base-url http://10.1.11.21:8096 \
  --db /jellyfin.db \
  --out-dir /out \
  --query Deadmau5

The same wrappers are available inside nix develop.

The Docker-based smoke command is still useful when you want to run inside the Playwright container:

docker run --rm --network host \
  -v /root/jellyfin-infinity/tools/verify_jellyfin_web_ui_cdp.py:/work/verify_jellyfin_web_ui_cdp.py:ro \
  -v /root/docker/jellyfin/config/data/jellyfin.db:/jellyfin.db:ro \
  -v /tmp/infinity-webtest:/out \
  mcr.microsoft.com/playwright:v1.53.0-noble \
  python3 /work/verify_jellyfin_web_ui_cdp.py \
    --base-url http://10.1.11.21:8096 \
    --db /jellyfin.db \
    --out-dir /out \
    --query Deadmau5

For broader live parity checks with credentials:

python3 tools/verify_infinity_parity.py \
  --base-url http://10.1.11.21:8096 \
  --credentials /path/to/credentials.json \
  --out-dir /out

Or with a read-only Jellyfin database, which creates and cleans up a temporary non-admin Jellyfin user for the run:

python3 tools/verify_infinity_parity.py \
  --base-url http://10.1.11.21:8096 \
  --db /path/to/jellyfin.db \
  --out-dir /out

That script covers the current manual smoke cases:

• Music: Deadmau5 search and album/detail rendering.
• Video: Skinamarink and Marie & Gali must either provide safe playback with preferred-language subtitles or a clear preparing/mismatch response.
• Search: Hostage Situation must not return duplicate One Piece episode cards, Marie & Gali must not show duplicate indistinguishable video cards, Beyond the Boundary must return video before music, and query transitions must not leave stale Marie cards visible.

API Endpoints

• GET /Infinity/Sources
• POST /Infinity/Search
• GET /Infinity/Search?q=alien&limit=20
• GET /Infinity/Results/{resultId}
• POST /Infinity/Actions/{action}

See docs/api.md for request and response examples.