> 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/output-panel.md).

# Output panel

Inspect Sync, Watcher, and Debug output from the Main page.

The **Output panel** on **Main** shows live text output from CrossWatch.

Use it to inspect sync runs, Watcher activity, and diagnostic messages.

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FxG2boyQtJzjf1vwErPa8%2Fimage.png?alt=media&amp;token=aa957942-4956-4878-838b-93a0412a4f24" alt=""><figcaption></figcaption></figure>

### Tabs

The Output panel includes three tabs:

* **Sync** — output from sync runs
* **Watcher** — output from Watcher and scrobble activity
* **Debug** — combined diagnostic output for troubleshooting

For live and saved logs, filters, and downloads, use [Logs](https://wiki.crosswatch.app/crosswatch/main-dashboard/tools/logs.md).

On mobile, use the **…** button labelled **Log actions** for **Open full logs**, **Copy output**, **Clear output** and **Close details**. **Analyze with assistant** appears when the assistant is enabled and the action is available.

### Understand sync results

Use [Sync statuses](https://wiki.crosswatch.app/crosswatch/main-dashboard/output-panel/sync-statuses.md) to read counters and outcomes such as:

* `added`, `removed`, and `updated`
* `skipped`, `blocked`, and `unresolved`
* `attempted`, `pairs`, and compact summaries like `+8 / -2 / ~4`

### Debug output

The **Debug** tab shows diagnostic messages from CrossWatch and its provider modules.

It also includes sync and watcher-related output in one place.

Provider logs still appear in the Docker console.

CrossWatch also copies provider log output into the **Debug** tab.

### What the Debug tab shows

Each entry includes a timestamp and a source tag.

The output can show:

* which provider operation ran
* which sync stage was reached
* provider responses and status codes
* skipped or unsupported operations
* rate limits and authentication problems
* matching and metadata problems
* exceptions and processing failures

### How the Debug tab works

CrossWatch keeps recent diagnostic messages in an in-memory buffer.

When you open **Debug**, CrossWatch loads the buffered messages first.

New messages then stream into the tab in real time.

The Debug tab:

* follows new messages automatically
* reconnects if the stream drops
* lets you copy the current tab with **Copy**

Use [Events](https://wiki.crosswatch.app/crosswatch/main-dashboard/tools/events.md) after a sync finishes.

Events keeps searchable run history, related attempts, and recorded reasons.

### Related topics

* [Main dashboard](https://wiki.crosswatch.app/crosswatch/main-dashboard.md)
* [Status dashboard](https://wiki.crosswatch.app/crosswatch/main-dashboard/status-dashboard.md)
* [Navigation](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation.md)
* [Maintenance](https://wiki.crosswatch.app/crosswatch/settings/maintenance.md)
* [Events](https://wiki.crosswatch.app/crosswatch/main-dashboard/tools/events.md)
* [Synchronization](https://wiki.crosswatch.app/crosswatch/settings/synchronization.md)
* [Watcher](https://wiki.crosswatch.app/crosswatch/settings/scrobbler/watcher.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.crosswatch.app/crosswatch/main-dashboard/output-panel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
