> 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/blueprint-architecture/scrobble/services/auto-remove-watchlist.md).

# Auto remove watchlist

This service can remove items from watchlists when playback completes.

It uses a TTL dedupe file to avoid repeat deletes.

{% tabs %}
{% tab title="End users" %}

### What it does

On completion, it can remove the same item from watchlists.

It is optional and config-gated.

### Common gotchas

* A completion event is required.
* Filters can prevent completion from being seen.
* Dedupe may hide repeated tests.
  {% endtab %}

{% tab title="Power users" %}

### Entry point

* `providers/scrobble/_auto_remove_watchlist.py`

### Public surface

* `auto_remove_if_config_allows`
* `remove_across_providers_by_ids`
* `remove_by_ids`

### State file

* `/config/.cw_state/watchlist_wl_autoremove.json`

The TTL is 120 seconds.

### Config touchpoints

* `scrobble.*` (auto-remove flags and behavior)
  {% endtab %}
  {% endtabs %}


---

# 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/blueprint-architecture/scrobble/services/auto-remove-watchlist.md?ask=<question>&goal=<endgoal>
```

`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.