Tools
Debug matching, edit local state, and export CSVs.
Last updated
Was this helpful?
⌘Ctrlk
Debug matching, edit local state, and export CSVs.
Tools are optional UI pages.
Use them for debugging and local data workflows.
Most setups only need Configure Pairs and Scheduling.
Use tools after a run exposes a problem or before a risky change.
Tools mainly work from local files created by runs.
Runtime state: /config/state.json
Manual policy (blocks, manual adds): /config/state.manual.json
Provider captures: /config/snapshots/...
CrossWatch tracker files (used for local backup workflows)
Provider writes depend on the tool:
Analyzer: no provider writes.
Exporter: no provider writes.
Editor: edits local state and policy.
Import datasets reads live provider APIs to populate state.json.
Captures: restore and clear actions write to the selected provider dataset.
Back up /config/state.json and /config/state.manual.json before risky edits.
Create a capture before destructive provider actions.
Use Analyzer when items didn’t sync.
Typical: missing IDs, missing peers, bad matches.
Use Events when you need the history of a sync or item operation.
Typical: failed writes, unresolved items, repeated attempts.
Use Exporter when you want CSV files for another service.
It converts local runtime state to import-friendly CSVs.
Use Editor when you need to change local state or apply manual policy.
Typical: block an item, fix a local row, seed data before your first sync.
Use Captures when you want a rollback point.
Typical: before cleanup, before switching providers, before bulk list edits.
Last updated
Was this helpful?
Was this helpful?