> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/watchlist.md). # Watchlist The **Watchlist** page shows one unified view of watchlist items across CrossWatch. It combines matching items from configured providers into one interface. Use it to review, filter, compare, hide, and remove watchlist items. {% hint style="info" %} This page shows data from the most recent CrossWatch sync. It does not continuously query every provider while open. {% endhint %} {% tabs %} {% tab title="End users" %} ### What it does The page merges matching entries from your configured providers. If the same item exists on Plex, Trakt, and SIMKL, it appears once. The page can show: * total and visible item counts * last synchronized time * poster, title, release, genre, and type * which providers currently have the item ### Coverage Pulse **Coverage Pulse** shows how well the **currently visible** watchlist is represented across active providers. It is not a sync-health check. Use it to see: * how complete the current view is * which provider has the best coverage * how filters change the coverage picture #### Sync density **Sync density** is the main percentage. Quick reading: * `100%` — every visible item exists on every active provider * `75%` — visible items exist on about three quarters of provider slots * `50%` — visible items exist on about half of provider slots Lower does not always mean sync failed. Provider differences and filters can reduce it. #### Provider cards Each active provider gets a card with: * provider name or logo * visible items found on that provider * provider coverage percentage * instance names, when available If you filter to one provider, that provider usually shows `100%`. The other cards then show how many of those same items exist elsewhere. ### Views and filters Use **List view** to compare metadata and provider presence. Use **Poster view** for a more visual scan. Main filters: * **Search** * **Type** * **Provider** Select **More** for: * release state * genre * hidden items Changing filters also recalculates **Coverage Pulse**. ### Delete vs Hide local Use **Delete** to remove selected items from one provider or all supported providers. Use **Hide local** to hide items only in the current browser. **Hide local** does not remove anything from external providers. ### Refresh **Refresh** reloads the stored CrossWatch watchlist. It does not always start a new provider sync. If you need newer provider data, run a sync from [Main dashboard](/crosswatch/main-dashboard.md). ### Limits Keep these in mind: * provider badges can be outdated until the next sync * missing TMDb setup means less artwork and metadata * local hidden items are browser-specific For pair behavior, see [Watchlist feature](/crosswatch/settings/configure-pairs/features/watchlist.md). {% endtab %} {% tab title="Power users" %} ### Data source The page reads unified watchlist items from `/api/watchlist/`. CrossWatch loads up to `5,000` items per response. Matching provider rows are normalized into one item with provider membership attached. Only active configured providers appear in the matrix and in **Coverage Pulse**. ### Sync density formula **Sync density** is calculated from the filtered visible result: ``` Provider memberships for all visible items ──────────────────────────────────────────── × 100 Visible items × Active providers ``` The result is rounded to the nearest whole percent. Example: ``` 100 visible items 3 active providers 240 memberships 240 / 300 × 100 = 80% ``` ### Provider coverage cards Each provider card uses: ``` Visible items present on provider ────────────────────────────────── × 100 Total visible items ``` Instance labels are collected from visible items only. The default instance is shown first. ### Filters and local state Coverage recalculates after changes to: * search * type * provider * release state * genre * hidden-item visibility Local UI preferences include: * list or poster view * poster size * advanced-filter visibility * release and genre filters * overlay preference * hidden-item visibility ### Metadata and limits TMDb can enrich visible items with artwork, dates, genres, overview, runtime, and trailers. Coverage Pulse does **not** prove: * provider connectivity * last sync success * correct matching * write support Use [Output panel](/crosswatch/main-dashboard/output-panel.md) and [Analyzer](/crosswatch/main-dashboard/tools/analyzer.md) for troubleshooting. {% endtab %} {% endtabs %} ### Related topics * [Navigation](/crosswatch/main-dashboard/navigation.md) * [Main dashboard](/crosswatch/main-dashboard.md) * [Dashboard widgets](/crosswatch/main-dashboard/dashboard-widgets.md) * [Watchlist feature](/crosswatch/settings/configure-pairs/features/watchlist.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/watchlist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.