> 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/profile/watchlist.md). # Watchlist Unified watchlist view across configured providers, with filters and provider-aware deletes. {% hint style="info" %} Watchlist shows synchronized provider data. It does not continuously query every provider while the page is open. For live unfinished playback, use Progress. {% endhint %} ### Summary The cards at the top show: * **Titles**, the number of titles on your watchlists * **Everywhere**, titles present on every relevant provider * **Missing**, titles missing from at least one relevant provider * **Providers**, providers currently contributing watchlist data ### Find and filter titles You can narrow the Watchlist using: * Search by title, identifier or provider * Media type, including Movies, Shows and Anime when applicable * Provider * Coverage, **Any coverage**, **Missing somewhere**, or **On every provider** ### Views Watchlist supports: * **Grid**, poster based browsing * **List**, a denser tabular view You can choose how many items are shown per page, 24, 48 or 96. Provider badges on an item show where that title currently exists. ### Remove watchlist entries If your account has permission to make changes, you can select individual items, visible items, or all matching results and remove them from selected providers. CrossWatch performs the removal against the selected provider watchlists. Managed users without write permission can browse the Watchlist but cannot perform removal actions. The Watchlist tab itself can also be unavailable when the assigned profile permissions do not include Watchlist access. ### Related pages * Overview * History * Ratings * Collections --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/profile/watchlist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.