mxr reply
Generated from
mxr reply --help. Edit the clap definitions incrates/daemon/src/cli/and re-runnpm run buildinsite/to regenerate.
Reply to a message
mxr reply [OPTIONS] <MESSAGE_ID>Arguments
Section titled “Arguments”| Flag | Description |
|---|---|
<MESSAGE_ID> | Message ID to reply to |
Options
Section titled “Options”| Flag | Description |
|---|---|
--account <ACCOUNT> | — |
--body <BODY> | Inline reply body (skip $EDITOR) |
--body-stdin | Read reply body from stdin |
--signature <SIGNATURE> | Insert this signature by name instead of the scoped default |
--no-signature | Do not insert any signature |
--yes | Skip confirmation |
--dry-run | Show what would be sent |
--remind-after <TIME> | After sending, remind if no reply has arrived by this time. Same forms as mxr remind --when: in 2h, tomorrow 9am, monday 17:00, RFC3339 |
--format <FORMAT> | [possible values: table, json, jsonl, csv, ids] |
-h, --help | Print help |
Use When
Section titled “Use When”Reply to one message, interactively or from an agent-approved body.
Everyday Examples
Section titled “Everyday Examples”mxr reply MESSAGE_IDmxr reply MESSAGE_ID --body 'On it.' --yesSee 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