mxr send
Generated from
mxr send --help. Edit the clap definitions incrates/daemon/src/cli/and re-runnpm run buildinsite/to regenerate.
Send a draft by ID
mxr send [OPTIONS] <DRAFT_ID>Arguments
Section titled “Arguments”| Flag | Description |
|---|---|
<DRAFT_ID> | Draft ID to send |
Options
Section titled “Options”| Flag | Description |
|---|---|
--account <ACCOUNT> | — |
--dry-run | Show what would be sent (sender, recipients, subject, byte count) without sending |
--format <FORMAT> | [possible values: table, json, jsonl, csv, ids] |
--at <TIME> | Schedule the draft to be sent later instead of sending now. Same forms as mxr snooze --until: in 2h, tomorrow 9am, monday 17:00, RFC3339. Use mxr unsend <draft-id> to cancel |
--remind-after <TIME> | After sending now, remind if no reply has arrived by this time. Same forms as mxr remind --when: in 2h, tomorrow 9am, monday 17:00, RFC3339 |
--check | Run the safety pipeline against the draft and exit without sending. Exit non-zero only if a Blocker issue is present |
--override-safety <TOKEN> | Single-use override token (issued by a previous failed --check) to bypass a Blocker |
--no-llm | Skip LLM-backed safety checks (answer-coverage). Useful when the daemon’s LLM is a rate-limited cloud model. Only honored with --check |
-h, --help | Print help |
Use When
Section titled “Use When”Send or schedule a saved draft. Add --check to run the pre-send safety pipeline without sending; exit 2 on Blocker. Use --override-safety <TOKEN> to bypass a Blocker the previous --check minted.
Everyday Examples
Section titled “Everyday Examples”mxr send DRAFT_ID --dry-runmxr send DRAFT_ID --at 'tomorrow 9am'mxr send DRAFT_ID --check --format json # safety report, no sendmxr send DRAFT_ID --override-safety OVERRIDE_TOKEN_FROM_CHECK # bypass minted BlockerSee 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