For the complete documentation index, see llms.txt. This page is also available as Markdown.

CrossWatch

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 SettingsUI settings.

  1. Open CW.

  2. Go to SettingsConnectionsTrackersCrossWatch

  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.

Power users

Storage

Local tracker data is stored in the CW configuration directory:

Additional profiles are stored below:

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.

Last updated

Was this helpful?