> 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/settings/synchronization/media-servers/silo.md).

# Silo

Silo adapter notes for syncing watchlist, history, ratings, progress, and playlists with stable external IDs.

{% hint style="info" %}
Connect Silo first. See [Silo](https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers/silo.md).
{% endhint %}

{% hint style="warning" %}
Silo support is **experimental**. Silo remains pre-release. Its API can change before version 1.0.
{% endhint %}

### What CrossWatch can sync

| Feature    | Read | Write | Notes                                                                                     |
| ---------- | ---- | ----- | ----------------------------------------------------------------------------------------- |
| Watchlist  | Yes  | Yes   | Movies and shows. Titles outside the library require Silo Requests.                       |
| History    | Yes  | Yes   | Library movies and episodes; no separate rewatch events.                                  |
| Ratings    | Yes  | Yes   | Movies and shows; whole-number scores from 1 to 10.                                       |
| Progress   | Yes  | Yes   | Resume positions for library movies and episodes.                                         |
| Playlists  | Yes  | Yes   | Silo collections and Favorites. Smart and shared collections are read-only.               |
| Collection | Yes  | No    | Read-only library inventory: movies, shows and episodes. Named collections use Playlists. |

**Read** brings data into CrossWatch; **Write** sends changes to this provider. Enable only features supported by both sides. Collection pairs are one-way only.

Data belongs to the selected household profile or the identities linked in the pair.

Connect the provider first: [Silo setup](https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers/silo.md).

### How matching works

CrossWatch matches by provider IDs only.

* CrossWatch reads your Silo library once per run. It indexes movies, shows, and episodes.
* Movies match on TMDb, IMDb, or TVDB IDs.
* Keep episode IDs and show metadata accurate on both sides. Missing or ambiguous matches remain unresolved.
* Missing show IDs trigger one lookup. CrossWatch caches the result.

{% hint style="warning" %}
Strict ID matching is the default.

Items must exist in your Silo library. Local files without a TMDb, IMDb, or TVDB match cannot sync.

When IDs are missing, CrossWatch prefers a missing peer over a wrong match.
{% endhint %}

### Watchlist behavior

* **Read:** the connected profile's Silo watchlist.
* **Write:** add or remove titles in your library.
* Titles outside your library can be added when Silo **Requests** is enabled. Otherwise, they remain unresolved.
* CrossWatch does not use fuzzy title matching.

{% hint style="info" %}
Silo hides fully watched shows from its watchlist. CrossWatch remembers them, so it does not treat them as removed.
{% endhint %}

### History behavior

* **Read:** the Silo watch ledger, including completed items and watch dates.
* **Write:**
  * Add with a date marks an item watched using that date.
  * Explicitly unknown watch dates are skipped during pair sync; Silo is not a destination for preserving undated watches.
  * Remove unwatches an item and hides it from the Silo history feed.
* CrossWatch verifies every write.

{% hint style="warning" %}
After you unwatch an item in Silo, Silo ignores earlier watches for that title.

CrossWatch marks these records as **ignored by server** and stops retrying them.
{% endhint %}

Rewatches are unsupported. Silo stores one watch per item.

### Ratings behavior

* **Read:** movie and show ratings.
* **Write:**
  * Add sets a whole-number rating from 1 to 10.
  * Remove clears the rating.
* Episode ratings are unsupported.

Use a Silo server with the 1–10 rating scale. A score of 7 stays 7/10. Pair sync rounds fractional scores to the nearest whole number, with halves rounded up: 7.5 becomes 8/10.

### Progress behavior

* **Read:** resume positions for movies and in-progress episodes.
* **Write:** sets the resume position.
* **Clear:** supported.
* Optional [Continue Watching removal sync](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/progress.md#sync-continue-watching-removals) hides the movie or show card, including its next-up card, while keeping progress. Both sides must be Emby, Plex, Tofa or Silo.
* CrossWatch verifies resume-position writes. If Silo has a newer position, CrossWatch skips the item.

See [Progress](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/progress.md).

### Playlists behavior

* **Favorites** appears as one playlist.
* Each Silo collection appears as its own playlist.
* You can create, rename, reorder, edit, and delete your manual collections.
* Smart collections and collections shared by other users are read-only.

### Collection behavior

* **Read:** movies, shows and episodes from the selected Silo libraries. Season entries are unsupported.
* **Write:** unsupported. Silo can only be the source of a one-way Collection pair.
* **Media info:** optionally includes available resolution, HDR and audio details for movies and episodes.
* To sync named Silo collections or Favorites, use **Playlists** instead.

### Household profiles

Each household profile has separate watchlist, ratings, history, and progress. A standard pair uses the connected profile. Enable **Identities** to sync linked people separately.

To sync more profiles:

* Select them on the Silo connection's **Identities** tab. In the pair, open **Providers**, enable **Identities**, and link each person to their account on the other server.
* Or create another CrossWatch Silo connection and select that household profile.

Silo administrator connections can also select profiles from other enabled accounts on the same server, marked **Account**. Only the server owner can add other administrators. These identities use the same pair and Watcher links; see [Other Silo accounts](https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers/silo.md#other-silo-accounts) for setup and access requirements.

Names provide suggestions. Check and save the links before running the pair. See [Multiple media server users](https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers/multiple-media-server-users.md).

{% hint style="warning" %}
If a Silo profile PIN changes, CrossWatch pauses that profile. Enter the PIN again on the **Identities** tab to resume synchronization.
{% endhint %}

### Settings

<details>

<summary>Common keys and knobs</summary>

**Connection**

* `silo.server_url`
* `silo.verify_ssl`
* `silo.timeout` — seconds; default `20`
* `silo.max_retries` — default `3`

**Rate limits**

* `silo.rate_limit.get_per_sec` — default `20`
* `silo.rate_limit.post_per_sec` — default `10`

Silo returns `429` after bursts of several hundred calls. CrossWatch waits for `Retry-After`, then continues.

</details>

### Diagnostics

<details>

<summary>State files</summary>

CrossWatch stores these files in `/config/.cw_state/`:

* `silo_details.<server>.json` — cached show IDs, kept for 30 days
* `silo_watchlist_series.<profile>.json` — watchlist shows, including completed ones

Deleting these files is safe. CrossWatch rebuilds them during the next run.

</details>

<details>

<summary>Unresolved reasons</summary>

* `not_in_library` — the title is not in your Silo library
* `unsupported_type` — for example, a season or episode rating
* `ignored_by_server` — Silo ignored a watch after a later unwatch
* `missing_duration` — Silo has no item runtime, so CrossWatch cannot write the watch
* `write_failed` — Silo rejected the write

</details>

### Notes and limitations

* CrossWatch uses only Silo's `/api/v2` API.
* With an `https://` `silo.server_url`, the certificate must be valid inside the CrossWatch container. Otherwise, disable **Verify SSL**.
* Silo tracks watched episodes, not watched shows.
* Start with one-way synchronization and one feature. Expand after you confirm the results.


---

# 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/settings/synchronization/media-servers/silo.md?ask=<question>&goal=<user_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.
