> 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/sync/_mod_emby/watchlist.md).

# watchlist

Emby does not have a first-class “account watchlist”. CrossWatch emulates one.

Related:

* Engine semantics: [Watchlist (engine-level)](/blueprint-architecture/sync/engine-level-features/watchlist.md)
* Setup: [Adapter: Emby](/crosswatch/providers/synchronization/adapter-emby.md)

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

### What syncs

“Watchlist” is a plan-to-watch set.

In Emby it is implemented as one of:

* **favorites** (default)
* **playlist** (named playlist)
* **collections** (named collection)

### Supported media types

* Movies: ✅
* Shows: ✅
* Seasons: usually ❌ (depends on IDs and mode)
* Episodes: ❌

### Reads vs writes

* Reads: enumerate the chosen container (favorites / playlist / collection).
* Writes:
  * `add` adds items to that container.
  * `remove` removes items from that container.

### Key settings

These live under the Emby provider block.

* `emby.watchlist.mode`: `favorites` | `playlist` | `collections`
* `emby.watchlist.playlist_name`: used when `mode = playlist`
* `emby.watchlist.watchlist_write_delay_ms`: pacing between writes

Config reference: [Configuration (config.json)](/crosswatch/configuration-config-json.md).

### Known limitations

* Missing IMDb/TMDb/TVDb IDs makes matching noisy.
* Playlist mode can churn if duplicates exist.

### Troubleshooting

**Watchlist adds repeat every run**

* Emby item lacks external IDs.
* The destination write “sticks”, but the next read can’t match it.

Fix:

* improve metadata IDs
* add a small write delay
* keep watchlist one-way until matching is stable
  {% endtab %}

{% tab title="Power users" %}

### Code map

* `providers/emby/_watchlist.py`
* `providers/emby/_common.py`

### State files

* `emby_watchlist.unresolved.json`

Unresolved items are written when:

* an item can’t be matched to an Emby item id
* a write fails after retries

Related: [Unresolved](/blueprint-architecture/orchestrator/unresolved.md).

### Notes

Mode selection is part of your “data model”. Changing it changes what the index means.
{% 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/sync/_mod_emby/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.