# Tools

Tools are optional UI pages.

Use them for debugging and local data workflows.

Most setups only need [Configure Pairs](/crosswatch/configure-pairs.md) and [Scheduling](/crosswatch/scheduling.md).

### Available tools

* [Analyzer](/crosswatch/tools/analyzer.md): find why an item didn’t sync.
* [Exporter](/crosswatch/tools/exporter.md): export runtime state to import-friendly CSV.
* [Editor](/crosswatch/tools/editor.md): edit local tracker data, state, and policy.
* [Captures](/crosswatch/tools/captures.md): capture and restore provider datasets.

### What tools touch

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.

{% hint style="warning" %}
Back up `/config/state.json` and `/config/state.manual.json` before risky edits.

Create a capture before destructive provider actions.
{% endhint %}

### Pick the right tool

Use **Analyzer** when items didn’t sync.

* Typical: missing IDs, missing peers, bad matches.

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.

### Related topics

* [Configure Pairs](/crosswatch/configure-pairs.md)
* [Scheduling](/crosswatch/scheduling.md)
* [Maintenance](/crosswatch/maintenance.md)


---

# Agent Instructions: 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/crosswatch/tools.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.