Skip to content
mxr

Observability

Status and health

Terminal window
mxr status
mxr status --watch
mxr doctor --check
mxr doctor --check --format json
mxr doctor --index-stats
mxr doctor --store-stats

The TUI Diagnostics page shows the same runtime information in one place:

  • Account health
  • Status
  • Doctor data
  • Recent events
  • Recent logs
  • Bug-report trigger

Event stream

Terminal window
mxr events
mxr events --type sync
mxr events --type sync,rule --format json

Use the event stream when you want structured, low-noise runtime signals instead of raw log lines.

History

Terminal window
mxr history
mxr history --category mutation
mxr history --category mutation --format json
mxr history --level error --limit 20

Use history when you want persisted event records instead of the live stream. This is the easiest way to review recent mutation activity after a batch command or agent workflow.

Logs

Terminal window
mxr logs
mxr logs --level error
mxr logs --purge

Text logs live under the mxr data directory. Structured event history is also in SQLite and pruned by the configured retention window.

Notifications and quick counts

Terminal window
mxr notify
mxr notify --format json
mxr notify --watch
mxr count "label:inbox unread"

These commands are useful for status bars, shell prompts, and lightweight monitoring.

Bug reports

When you need a shareable diagnostic bundle:

Terminal window
mxr bug-report
mxr bug-report --stdout
mxr bug-report --github

Or open Diagnostics in the TUI and trigger bug-report generation there.