mailops doctormailops connectmailops demomailops draftmailops syncmailops statusmailops searchmailops inspectmailops triagemailops askmailops reviewmailops rulesmailops applymailops rollbackmailops export
The CLI now supports the first concrete Proton operator loop:
doctorvalidates local state and reports Proton Bridge reachability, including WSL-to-Windows host candidates.connect protonresolves Bridge settings, lists folders, and saves non-secret Proton profiles.demo seedcreates a local-only deterministic mailbox fixture for contributor testing.draft createcreates an explicit custom outbound draft proposal as a pending review batch.syncindexes bounded Proton Bridge mailbox slices into SQLite.status,search,inspect, andtriageread local indexed state.searchreturns local thread and message IDs for follow-up inspection.inspect threadandinspect messageshow bounded local email context without contacting providers.askcompiles natural-language requests into explicit local actions or queries.reviewinspects persisted review batches and local draft proposals.applyapproves batches and materializes Proton drafts through Bridge IMAP when credentials are available.review batch sync-draftsresolves executed Proton draft refs back to provider metadata and records local audit snapshots.rules proposegenerates review-only Proton Sieve text and preview metadata without applying provider rules.rollbackremoves local draft artifacts only before provider-side execution exists.export auditemits markdown audit history.
Gmail commands remain placeholders until the Gmail API adapter is implemented.
Natural-language entry through ask must compile into explicit actions, queries, or review items. It should never be a hidden destructive shortcut.
MailOps may create reviewed Proton drafts. It must not send mail, delete mail, bulk mutate mail, or apply provider rules without explicit future policy support and review gates.
Create custom outbound draft proposals from any local context without sending:
mailops draft create --from-account operator@example.com --to stakeholder@example.com --subject "Project update" --body-file draft.md --context-ref repo:current
mailops review batch show <batch_id>
mailops apply <batch_id>
mailops review batch sync-drafts <batch_id>draft create records To, Cc, Bcc, subject, body, and context refs in local state. review batch show displays that envelope before apply. apply may materialize that proposal as a Proton Draft after review; it does not send the message.
Generated reply proposals also freeze their recipients and account at creation.
apply rejects legacy proposals without reviewed recipients. If an action has an
interrupted or uncertain provider attempt, the batch requires attention, apply
returns nonzero, and automatic retry/local rollback are blocked. Inspect Proton
Drafts and the audit trail before any manual recovery.