Drafting replies with review
An agent writes reply drafts at the Read and draft level; you read, edit and send them yourself in Airpost.
What you’ll build
A workflow where an agent drafts replies to the threads waiting on you, and nothing leaves until you’ve read each draft and clicked Send. The agent runs at Read and draft (read-write), which allows reply_to_thread and update_draft but not send_draft. The drafts are ordinary drafts: they show in the thread in the desktop app, the web client and airpost draft list.
Prerequisites
- Airpost and
airpost-mcp. See Install the CLI. - An engine running.
- An MCP client registered with
airpost-mcp install(Connect a client). - Optional: a few templates in Preferences > Templates for replies you send often.
Set the level to Read and draft
In Preferences > MCP pick Read and draft, or:
{
"accessLevel": "read-write"
}
With this level a send_draft call fails with “Access denied”, and the agent is told to report that rather than look for another way.
Ask for drafts
Go through threads in my inbox from the last 3 days where someone is
waiting on me (search_mail "in:inbox after:3d"). For each one:
- read it with get_thread
- write a short reply with reply_to_thread, in my voice: plain,
friendly, no more than five sentences
- if you'd need information you don't have, write the reply anyway and
put [CHECK: ...] where I need to fill something in
If the thread already has an unsent draft of mine, revise it with
update_draft instead of creating another. Don't send anything.
Finish with a list: thread subject, draft id, and any [CHECK] items.
Review in Airpost
Open Airpost. Each drafted thread shows its draft. Read it, fix the [CHECK: ...] parts, and send it from the composer as usual. Undo send and Send Later work as for any draft.
From a terminal you can see what’s waiting:
airpost draft list --json | jq -r '.drafts[] | "\(.id)\t\(.subject)\t\(.to | map(.email) | join(", "))"'
Send from the terminal instead (optional)
If you’d rather review there, look at one draft’s text, check it and send it with an undo window:
airpost show <draft-id> --body
airpost draft validate <draft-id>
airpost draft send <draft-id> --undo 30
airpost draft cancel-send <draft-id> calls it back during those 30 seconds.
Expected output
The agent’s final message:
Drafted 3 replies:
- "Contract redlines" draft 7f3a... [CHECK: is section 4 approved by legal?]
- "Thursday standup moved?" draft 1c09...
- "Invoice #2291" draft a44e... [CHECK: payment date]
airpost draft list prints the same three drafts with their recipients.
How it works
reply_to_thread replies to the newest message in the thread that isn’t a draft, quotes it and addresses its sender (or everyone, with type: "reply-all"). Airpost adds your From address, signature and composing defaults, so the agent only writes the message. The result lists the thread’s existing unsent drafts, which is how the agent knows to call update_draft instead of piling up a second draft.
update_draft replaces the whole body, so an agent revising a draft has to keep the quoted text itself. Drafts being sent or scheduled can’t be edited.
Reply bodies are HTML. If you have a template that fits, the agent can pass template with its name instead of body; read the template first with list_templates to fill its variables.
Variations
- Reminders. Ask the agent to pass
remindInDays: 3toreply_to_thread. Once you send the draft, Airpost brings the thread back to the top of the inbox if no one has replied in three days. - Attachments. Over stdio the agent can attach local files by absolute path with
attachments. Over HTTP it can’t. - Scheduled review. Run the same prompt each morning with Claude Code in a cron job, and do the review over coffee.
- Let it send some. Raise the level to Read, draft and send only for a session where you tell it which drafts to send.
send_draftasks the agent to show you the draft and get an explicit yes first.
Cleanup
Delete drafts you don’t want in the composer, or:
airpost draft delete <draft-id>
Set the level back to Read mail when you’re done.