> 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/connections/trackers/crosswatch.md).

# CrossWatch

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

<figure><img src="/files/I2xiIW2sdkViILPtENZ0" alt=""><figcaption></figcaption></figure>

Use the local CrossWatch tracker for private, on-device synchronization storage.

### Connect Local Tracker

CW Local Tracker runs inside CW. It needs no external account, API key, PIN, or OAuth application.

CW Tracker is now a dedicated connection. It no longer appears in **Settings** → **UI settings**.

1. Open CW.
2. Go to **Settings** → **Connections** → **Trackers** → **CrossWatch**
3. Click **Connect local tracker**.

CW enables the local tracker as a normal connection. Its status changes to **Connected**.

Create additional profiles when another user or sync setup needs separate storage.

### Configure the local tracker

Open the **Settings** tab in the CW Local Tracker connection.

#### Label

Enter a short internal label for the tracker profile. Labels support up to 12 characters.

#### Retention days

Set how long CW retains snapshots. The default is 30 days.

Set this value to `0` to retain snapshots indefinitely.

#### Auto snapshot

When enabled, CW creates a snapshot before writing local tracker changes. This setting is enabled by default.

#### Max snapshots per feature

Set the maximum snapshots retained for each feature: watchlist, history, ratings, and progress.

The default is 64 snapshots per feature. Set this value to `0` for unlimited snapshots.

#### Restore snapshots

Select the snapshot used for each feature. **Latest** is the default and uses the newest available snapshot.

You can select a specific snapshot for watchlist, history, ratings, or progress.

### Troubleshooting

* If the connection fails, confirm the CW configuration directory exists and is writable.
* If recent changes are missing, confirm **Restore snapshots** is set to **Latest**.
* If snapshots disappear early, check **Retention days** and **Max snapshots per feature**.
* If the main connection cannot be removed, delete additional tracker profiles first.

Remove additional profiles with their profile delete button.
{% endtab %}

{% tab title="Power users" %}

## Power users

### Storage

Local tracker data is stored in the CW configuration directory:

```
/config/.cw_provider
```

Additional profiles are stored below:

```
/config/.cw_provider/profiles/<profile>
```

The `/config` directory must be writable and persistent. Deleting its volume can delete local tracker data and snapshots.

### Limitations

CW Local Tracker supports bidirectional synchronization for watchlist, ratings, history, and playback progress.

Playlists are not supported.

The adapter has no fixed item limit. Capacity depends on available storage, synchronized data, and snapshot retention.

The local tracker is a local source and destination. It is not a remote tracking service or cloud backup.
{% 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/crosswatch/settings/connections/trackers/crosswatch.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.