mxr summarize
Generated from
mxr summarize --help. Edit the clap definitions incrates/daemon/src/cli/and re-runnpm run buildinsite/to regenerate.
Summarise an email thread using the configured LLM (Ollama, LM Studio, OpenAI, etc.). Requires [llm] enabled = true in config. Pass a positional thread ID or use --search QUERY plus --first (most recent match) or --limit N to summarize multiple threads in one go. Multi-summary output is separated by --- THREAD_ID ---
mxr summarize [OPTIONS] [THREAD_ID]Arguments
Section titled “Arguments”| Flag | Description |
|---|---|
[THREAD_ID] | Thread ID to summarise |
Options
Section titled “Options”| Flag | Description |
|---|---|
--search <SEARCH> | — |
--first | Summarize only the most recent matching thread |
--limit <LIMIT> | Cap the number of threads summarized when —search is used. Each summary is an LLM call — keep this low when targeting metered cloud endpoints |
--format <FORMAT> | [possible values: table, json, jsonl, csv, ids] |
-h, --help | Print help |
Use When
Section titled “Use When”Summarize long threads through the configured LLM.
Everyday Examples
Section titled “Everyday Examples”mxr summarize THREAD_IDmxr summarize --search 'from:team newer_than:7d' --limit 5See also
Section titled “See also”- CLI overview — full command index
- Concepts — query operators, search modes, JSON shapes
- Automation contract — which commands support
--format json,--dry-run, stdin