> 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/main-dashboard/tools.md).

# Tools

Tools are optional UI pages.

Use them for debugging and local data workflows.

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

{% hint style="info" %}
Use tools after a run exposes a problem or before a risky change.
{% endhint %}

### Available tools

<table data-view="cards"><thead><tr><th>Tool</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Analyzer</td><td><a href="/spaces/3rh5THg1PdhVsBt3GALo/pages/urf7i5pr8Dd67jaRYgsQ">/spaces/3rh5THg1PdhVsBt3GALo/pages/urf7i5pr8Dd67jaRYgsQ</a></td></tr><tr><td>Events</td><td><a href="/spaces/3rh5THg1PdhVsBt3GALo/pages/0FlaZT5iA0GzYOrVViEP">/spaces/3rh5THg1PdhVsBt3GALo/pages/0FlaZT5iA0GzYOrVViEP</a></td></tr><tr><td>Exporter</td><td><a href="/spaces/3rh5THg1PdhVsBt3GALo/pages/3etr8jiXzeY3oHBt6Zka">/spaces/3rh5THg1PdhVsBt3GALo/pages/3etr8jiXzeY3oHBt6Zka</a></td></tr><tr><td>Editor</td><td><a href="/spaces/3rh5THg1PdhVsBt3GALo/pages/jnc3CxKIomZJwjuz5RlN">/spaces/3rh5THg1PdhVsBt3GALo/pages/jnc3CxKIomZJwjuz5RlN</a></td></tr><tr><td>Captures</td><td><a href="/spaces/3rh5THg1PdhVsBt3GALo/pages/qAmxDUAX1DagwLqV0c5P">/spaces/3rh5THg1PdhVsBt3GALo/pages/qAmxDUAX1DagwLqV0c5P</a></td></tr></tbody></table>

### 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 **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.

### Related topics

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


---

# 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/main-dashboard/tools.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.