> 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/engine-level-features/history.md).

# History

{% tabs %}
{% tab title="End users" %}
History means: **“I watched this.”**

History is timestamp-sensitive.

Most providers store a `watched_at` or “played” state.

{% hint style="warning" %}
History can be noisy on big libraries.

Start one-way + add-only.
{% endhint %}

Related:

* Pair toggles: [Configure Pairs](/crosswatch/configure-pairs.md)
* Filtering by library: [Library Whitelisting](/crosswatch/library-whitelisting.md)
  {% endtab %}

{% tab title="Power users" %}
**Feature:** `history`

### Contract

* read: `build_index(...) -> dict[canonical_key -> item]`
* write: `add(items)` / `remove(items)`

Most items should include:

* `watched_at` (ISO8601 preferred)

### Index semantics across providers

* `JELLYFIN`: `present`
* `MDBLIST`: `present`
* `PLEX`: `present`
* `PUBLICMETADB`: `present`
* `SIMKL`: `delta`
* `TAUTULLI`: `present` (read-only importer)
* `TRAKT`: `present`

### Providers that implement History

* `JELLYFIN`
* `MDBLIST`
* `PLEX`
* `PUBLICMETADB`
* `SIMKL`
* `TAUTULLI`
* `TRAKT`
  {% 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:

```
GET https://wiki.crosswatch.app/blueprint-architecture/sync/engine-level-features/history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.