Bug reports
Command
Section titled “Command”mxr bug-reportBy default this writes a Markdown report to a temp file and tells you where it was saved.
Useful flags
Section titled “Useful flags”mxr bug-report --stdoutmxr bug-report --editmxr bug-report --clipboardmxr bug-report --githubmxr bug-report --output ~/report.mdmxr bug-report --verbosemxr bug-report --full-logsmxr bug-report --since 2hmxr bug-report --no-sanitize--full-logs includes every log line from today instead of the last 100 (or 500 with --verbose). The report is still sanitized.
--no-sanitize writes the report without redaction. mxr prints a warning to stderr before it generates anything, and says (not sanitized) on the saved-file line. stdout stays clean, so --stdout piping still works, and the command never prompts. Read the report before you share it: it can contain email addresses, names, message subjects and body text, and tokens.
Included data
Section titled “Included data”- System details
- Resolved config summary
- Daemon status
- Account health
- Recent sync events
- Recent errors
- Recent text logs
Sanitization
Section titled “Sanitization”Unless --no-sanitize is set, mxr redacts:
- Email addresses
- Token and password references
- API keys and authorization material
- Message subjects and body fields
- IP addresses
- Home-directory prefixes in file paths