> 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/overview.md).

# overview

This is the **Emby sync module** used by the orchestrator. It is not the setup/auth guide.

Start at: [Emby module](/blueprint-architecture/sync/_mod_emby.md).

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

### What it supports

This module can sync:

* [Watchlist](/blueprint-architecture/sync/_mod_emby/watchlist.md)
* [History](/blueprint-architecture/sync/_mod_emby/history.md)

Feature semantics live here:

* [Watchlist (engine-level)](/blueprint-architecture/sync/engine-level-features/watchlist.md)
* [History (engine-level)](/blueprint-architecture/sync/engine-level-features/history.md)

### Setup links

* [Auth: Emby](/crosswatch/providers/authentication/auth-media-servers/auth-emby.md)
* [Adapter: Emby](/crosswatch/providers/synchronization/adapter-emby.md)

### Matching notes

Emby often lacks strong external IDs.

That makes CrossWatch matching noisier.

Best practice:

* keep your Emby metadata agents set up
* ensure items have IMDb/TMDb/TVDb IDs where possible

### Common gotchas

* Watchlist is emulated (favorites/playlist/collections).
* Library scoping changes what “exists” to the module.
* Writes can be eventually consistent.
* If IDs are missing, two-way sync can get risky.
  {% endtab %}

{% tab title="Power users" %}

### Entry point

* `sync/_mod_EMBY.py`

### Feature modules

* watchlist → `providers/emby/_watchlist.py`
* history → `providers/emby/_history.py`

### Capability highlights

* `bidirectional: true`
* `index_semantics: "present"`
* `provides_ids: false`

<details>

<summary>Capabilities (raw)</summary>

```json
{
  "bidirectional": true,
  "index_semantics": "present",
  "provides_ids": false
}
```

</details>

### State files

* `emby_watchlist.unresolved.json`
* `emby_history.shadow.json`
* `emby_history.unresolved.json`
* `emby_history.emby.blackbox.json`

### Debug knobs

* `CW_DEBUG`, `CW_LOG_LEVEL`
* `CW_EMBY_DEBUG`, `CW_EMBY_LOG_LEVEL`
  {% 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/overview.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.