> For the complete documentation index, see [llms.txt](https://docs.monarchlinux.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monarchlinux.com/troubleshooting/crash-reports.md).

# Crash reports

Review crash diagnostics, anonymize documents and optionally use AI before sharing a private report.

Use Monarch’s crash history to review an application failure and prepare a private diagnostic report. Nothing is sent to Monarch until you confirm the upload. AI analysis is optional and has its own data-sharing considerations.

## Open a crash

Select **View crash** in a crash notification, or open **Monarch Menu → System → Crashes**. From a terminal:

```bash
monarch crash history
```

The history lists the 100 most recent crashes recorded for your user by systemd-coredump. Choose **Details** to see the application, signal, date and whether a core dump is available. Select **Send a report** to open the document reviewer; this button does not upload anything.

A crash can remain in the history after its core dump has been deleted. Ordinary application errors, normal exits and processes killed because memory ran out may not appear here.

## Review and anonymize documents

The report separates a filtered technical summary, optional AI analysis, selected text attachments and any additional context you provide.

![English crash reviewer showing included and excluded synthetic documents](https://2401007956-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPHuQxvjCbX3wVSeqqOGO%2Fuploads%2FCNbP4x8rb1WPzobgkR5R%2Fcrash-reviewer-english.png?alt=media)

*Example using synthetic diagnostics. The reviewer also supports French.*

For each proposed document:

1. Read its contents and purpose.
2. Select private text and choose **Anonymize**. The outgoing version contains `[REDACTED]` in place of the selected passage; purple highlighting marks these replacements.
3. Choose **Attach this document** or **Do not attach**. Green and red accents show your decision.

**Review report** becomes available after every proposed document has a decision. Editing a document or restoring hidden text invalidates its previous decision: read and approve the new version again.

The eye button shows the **local original**, read-only, in the same editor. Return to the outgoing version before approving it. **Restore original** restores a selected redaction, or the one under the cursor, only when its original passage is known locally. The original comparison copy is never attached automatically.

{% hint style="warning" %}
Filtering can miss sensitive information. Review the outgoing text yourself. If anonymization fails, the document is flagged and can only be included after you explicitly authorize sharing that version.
{% endhint %}

Attachments must be UTF-8 text: **1 MiB per file**, **5 MiB total**, and at most **50 documents**. Oversized files are rejected rather than silently truncated. Raw core dumps are not attached.

## Optional AI analysis

When a default agent is available, choose **AI analysis…** in the reviewer to improve the report, or **Analyze with AI** in the crash details to open the separate deep-investigation consent screen.

* **Filtered-data mode** supplies the filtered technical report and filtered document copies. The agent is instructed to use only these inputs.
* **Deeper investigation** requires separate authorization. It allows the agent to examine the local core and targeted logs relevant to the crash.

{% hint style="warning" %}
The configured agent may send these inputs or excerpts to its provider. Limited mode is an instruction to the agent, not an operating-system sandbox. Anonymizing the eventual Monarch report does not undo earlier transmissions to an AI provider.
{% endhint %}

Finish the analysis in the agent’s terminal, then choose **Import results**. Review the proposed analysis and attachments before including them; nothing is selected automatically. You can also continue without AI results.

A later investigation can add more documents. If a new attachment has an existing name, it receives a numbered name; older attachments remain available. New documents and the replacement analysis require fresh review.

## Check and send the report

1. Choose **Review report**. Check the technical report, optional analysis and attachment summary. Each document opens in a wide, read-only preview; **Close** or Escape returns to the summary.
2. Optionally add reproduction steps or other useful context. You can anonymize selected context text too. Additional context is limited to 64 KiB of UTF-8 text.
3. Choose **Continue** to check service availability and see the destination and advertised retention period. This step still does not upload the report.
4. Choose **Confirm submission** to send the reviewed version.

The technical summary contains the application, crash date, signal, versions and recorded backtrace. System versions describe the machine when the report was prepared; package versions come from crash-time metadata when available, otherwise from the installed package.

If sending fails, reopen the same crash and retry. Monarch retains the frozen payload and submission key so a retry does not create another report. That attempted version is read-only.

## Privacy, retention and the receipt

After a successful upload, Monarch shows a report reference and private link. Reports and attachment downloads are restricted to the Monarch team through authenticated access. Remote retention is **at most 90 days**, and maintainers can delete a report earlier. An expired or deleted link no longer provides access to the report.

**Create GitHub issue** opens an unsubmitted public issue draft with the private report link. It does not copy the diagnostics, AI analysis or attachments, and it does not publish the issue. Review the draft before posting it, especially any reproduction details you add. Closing a GitHub issue does not automatically delete the private report or extend its retention.

Successful sending removes local draft copies while preserving the receipt. Source files and system-managed core dumps remain untouched. If local cleanup fails, the receipt screen warns that copies remain and offers **Retry local cleanup**, without uploading the report again.

## Keep or discard a draft

Closing an unsent report offers **Keep** to resume later or **Discard** to delete its local working copies. Failed deletion is reported and leaves the window open so you can retry. Keeping a draft does not submit it, and remote retention does not remove drafts stored on your machine.

## Language and notifications

The history panel and reviewer follow Monarch’s interface language independently of Noctalia. Select English, French or the system locale:

```bash
monarch language en
monarch language fr
monarch language auto
```

Reopen the reviewer after changing language. Existing diagnostic contents and analysis are preserved rather than translated.

To toggle crash notifications, use **Actions → Toggle → Crash Capture** in the Monarch Menu, or:

```bash
monarch toggle crash-capture
```

This changes desktop notifications, not systemd’s crash recording.

## If something is unavailable

* **No core dump:** you can still review the recorded crash. Deeper analysis may be limited by the missing core or debug information.
* **No AI action:** configure an available default agent, or prepare the report without AI.
* **Collection unavailable:** keep the draft and retry later. An older server cannot accept the enriched report; the reviewer does not silently drop attachments to use a legacy endpoint.
* **Local cleanup incomplete:** keep the receipt and retry local cleanup after correcting the reported filesystem error. You do not need to send the report again.
