> 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.md).

# Main dashboard

<figure><img src="/files/Esim1tHUWMS2WlwtMM3X" alt=""><figcaption><p>Main page overview with top actions, live status, widgets, and output.</p></figcaption></figure>

The **Main** page is the operational home for CW.

Use it to start runs, watch status, inspect output, and open the most-used tools.

It is built around three jobs:

1. start and monitor work
2. review live status
3. open deeper tools when something needs attention

### Top actions

The first row contains the main action buttons.

Use them to jump into the most common tasks:

* **Synchronize** — start a sync run
* **View details** — inspect recent sync results
* **Analyzer** — investigate matching and state problems
* **Events** — review searchable sync history and recorded outcomes
* **Exporter** — build export files from CW data

These actions are for running and inspecting work.

Most configuration still lives under **Settings**.

### Main page sections

#### Status dashboard

The status row gives you a fast operational summary.

Unlike **Settings → Overview**, this area focuses on live runtime state.

It covers:

* monitoring status for **Scheduler**, **Watcher**, and **Webhook**
* system status for **Sync pairs**, **CW Health**, and **Updates**

Use [Status dashboard](/crosswatch/main-dashboard/status-dashboard.md) for the full reference.

#### Output panel

The output area shows live and recent run detail.

Use it to inspect:

* **Sync** output
* **Watcher** output
* **Debug** output

Use [Output panel](/crosswatch/main-dashboard/output-panel.md) for the full guide.

#### Dashboard widgets

The widget area shows media-focused summaries from existing CW data.

That includes:

* **Watchlist widget**
* **Recent History widget**
* **Latest Ratings widget**
* **Recent Scrobble widget**

Use [Dashboard widgets](/crosswatch/main-dashboard/dashboard-widgets.md) for widget behavior, requirements, and troubleshooting.

#### Recent Activity

The **Main** page also shows a separate text-based activity list.

This is different from the visual **Recent Scrobble** widget.

Use [Recent Activity](/crosswatch/settings/scrobbler/recent-activity.md) for that audit trail.

### What belongs on Main

Use **Main** when you want to:

* start a run
* confirm live service state
* inspect recent output
* review dashboard summaries

Use **Settings** when you want to change configuration.

### Related topics

* [Navigation](/crosswatch/main-dashboard/navigation.md)
* [Status dashboard](/crosswatch/main-dashboard/status-dashboard.md)
* [Dashboard widgets](/crosswatch/main-dashboard/dashboard-widgets.md)
* [Watchlist](/crosswatch/main-dashboard/navigation/watchlist.md)
* [Quick Add](/crosswatch/main-dashboard/navigation/quick-add.md)
* [Playback](/crosswatch/main-dashboard/navigation/playback.md)
* [Output panel](/crosswatch/main-dashboard/output-panel.md)
* [Events](/crosswatch/main-dashboard/tools/events.md)
* [Recent Activity](/crosswatch/settings/scrobbler/recent-activity.md)
* [Settings](/crosswatch/settings.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.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.