Documentation menu

Connect / AniList

AniList connection, status, scores, planning, and recommendations

Connect AniList with OAuth, write watched status safely, and keep recommendation feedback distinct from playback tracking.

What Omakase reads

Omakase can read a public AniList or MyAnimeList history for recommendation evidence. A written taste profile adds the context that a score alone cannot carry.

AniList writes require an explicit OAuth connection. The current release can:

  • add a chosen title to Planning;
  • mark a recommendation as Completed;
  • save an optional 1–10 score;
  • exclude an “Already watched” recommendation from future menus immediately;
  • keep a durable retry when AniList is disconnected or temporarily unavailable.

MyAnimeList writes are not enabled in this release.

Register the OAuth application

In AniList developer settings, create an application with this callback shape:

text
https://your-private-omakase.example/plus/integrations/anilist/callback

The path must remain exact. Configure the same HTTPS base URL in Omakase. Store the AniList client ID and client secret in the secret environment file, not in public configuration.

The OAuth flow uses PKCE, an owner-scoped single-use state value, a ten-minute expiry, and durable server-side flow state. The resulting access token is encrypted at rest.

Connect in Settings

  1. Sign in to the private Omakase Plus interface.
  2. Open Settings.
  3. Choose Connect AniList.
  4. Review AniList’s authorization screen.
  5. Return to Omakase and confirm the connected state.

Do not use a callback host that is reachable over plain HTTP beyond loopback.

“Already watched” is a real list action

The Discover action coordinates two outcomes:

  1. local recommendation feedback is recorded immediately;
  2. AniList is created or updated as Completed with the optional score.

If the remote write fails, Activity shows a retryable list action. Omakase does not present a local hide as a successful AniList update.

Recommendations and playback tracking

Recommendation feedback and playback progress are separate sources of truth:

  • Omakase owns recommendation disposition and request history;
  • AniList owns list status and score;
  • Plex owns playback position;
  • an optional tracking bridge owns playback-to-list synchronization.

If you connect a Plex-to-AniList bridge, scope it to the Anime and Anime Movies libraries, use stable identity mapping, choose a completion threshold, and prevent it from silently overwriting an intentional Omakase score.

Conflicts should be visible and reviewable rather than resolved by guessing.