Send later, snooze and reminders
Schedule messages, snooze threads, get reminded when nobody replies, undo a send, and how the engine carries them out.
Send later, snooze, send reminders and undo send all run on your computer. They don’t need an Airpost server, and the engine carries them out itself, so they work with the window closed and from the CLI and agents too.
Send later
In the composer, open Send Later and pick a time:
| Option | When it sends |
|---|---|
| In 1 hour / In 2 hours | 60 or 120 minutes from now |
| Later Today | Three hours from now, on the hour |
| Tomorrow Morning | Tomorrow at 9:00 |
| Tomorrow Evening | Tomorrow at 20:00 |
| This Weekend | Saturday at 9:00 |
| Next Week | Monday at 9:00 |
Or type your own in the date field, for example “next Monday at 2PM”. Times are in your computer’s time zone. The draft shows “Scheduled for …” until it goes out. To change your mind, open the draft and choose Unschedule Send; the draft stays in Drafts.
Snooze
Snooze hides a thread until a time you choose, then brings it back to your inbox. Select one or more threads and press Z (also H with the Gmail set), or use Thread > Snooze.
| Option | Comes back |
|---|---|
| Later Today | Three hours from now, on the hour |
| Tonight | Today at 20:00 (midnight if it’s already past 20:00) |
| Tomorrow | Tomorrow at 9:00 |
| This Weekend | Saturday at 9:00 |
| Next Week | Monday at 9:00 |
| Next Month | The 1st of next month at 9:00 |
You can also type a custom time. Snoozed threads move to the Snoozed folder in the sidebar. To bring one back early, open Snoozed and move it to the inbox, or press mod+Z right after snoozing.
When a thread comes back, Airpost puts it at the top of the inbox with a short “Airpost Reminder” note, so it doesn’t land below newer mail. Turn off Resurface messages to the top of the inbox when unsnoozing in Preferences > Notifications to have it come back marked unread instead.
Send reminders
A reminder brings a thread you sent back to the top of your inbox if nobody replies by a time you pick. In the composer, or on a sent thread, choose Set Reminder (“Remind me if no one replies”):
- In 3 Hours, Tomorrow Morning, Tomorrow Evening
- In 3 Days, In 1 Week, In 2 Weeks, In a Month
- or a custom time
If anyone else replies before then, the reminder is cleared and never fires. Threads with a reminder are listed under Reminders in the sidebar. To change or remove one, use Edit Reminder or Clear reminder. A thread that comes back shows a Reminder badge.
Undo send
After you click Send, a bar with Undo stays up for a few seconds. Send now instead skips the wait.
| Preference | Options | Default |
|---|---|---|
| Preferences > Composing & sending > Undo Send | 5, 15, 30 or 60 seconds, or Off | 5 seconds |
During the window the message hasn’t left your computer. Undo puts it back in the composer.
How the engine runs them
All four features are the same mechanism. When you schedule something, Airpost writes a small piece of metadata with an expiration time onto the draft or thread: send-later on a draft, thread-snooze or send-reminders on a thread. Undo send writes the same send-later metadata with a short expiration. The engine’s expiration executor watches for due entries and acts on them.
What this means in practice:
- No window needed. The engine, not the window, sends and unsnoozes, so closing the window is fine. See The engine.
- Nothing fires twice. The desktop, CLI, web client and agents all see the engine’s result rather than each acting on the entry.
- Incomplete drafts wait. If a scheduled draft’s body or an attachment isn’t on this computer yet (for example, it was scheduled on another device), the engine fetches it and looks again after 1, 2, 4 and 8 minutes. After that the send fails and the draft shows the error.
- Offline sends retry. If the SMTP server can’t be reached when a send is due, the engine keeps it queued and retries for up to 24 hours before failing it.
- Moved threads stay put. If you move a snoozed thread out of Snoozed yourself, the engine leaves it where you put it when the snooze comes due.
Keeping the engine running
| Setup | What happens at the scheduled time |
|---|---|
| Window open | Runs on time |
| Window closed, app still running (the default when the menu bar or tray icon is on) | Runs on time |
| App quit, Keep Airpost running in the background on (Preferences > General) | Runs on time: the engine runs as a login service |
| App quit, background mode off | Runs as soon as you next open Airpost |
On macOS the menu bar setting is Show Airpost in the menu bar; on Linux, closing the window leaves Airpost in the tray. Keep Airpost running in the background installs the engine as a launchd (macOS) or systemd user (Linux) service so it keeps running after you quit. You can do the same with airpost engine install.
With an Airpost server connected, each device claims a due entry before acting on it, so a send scheduled on your laptop isn’t also sent by your desktop. Without a server, schedule on the computer that will be on.
From the CLI
The CLI writes the same metadata the desktop does, so anything you schedule there shows in Airpost at once, and the reverse.
# Send a draft tomorrow morning, archive the thread after
airpost draft send <draft-id> --at tomorrow --archive
# Hold a send for 30 seconds, and call it back
airpost draft send <draft-id> --undo 30
airpost draft cancel-send <draft-id>
# What's waiting to go out, soonest first (and scheduled sends that failed)
airpost draft scheduled
# Snooze, and end it early
airpost snooze <thread-id> --until 2h
airpost snooze <thread-id> --until 2026-11-02T14:30
airpost unsnooze <thread-id>
# Remind me if nobody replies in 3 days, or clear it
airpost remind <thread-id> --in 3d
airpost remind <thread-id> --clear
--until, --at and --in take 30m, 2h, 3d, 1w, tomorrow (9:00), tomorrow 14:30, a date (9:00 that day) or a date and time. Times are local unless they carry an offset. Giving remind a draft id attaches the reminder to the draft, so it starts when the draft is sent.
Agents have the matching MCP tools: schedule_send, cancel_scheduled_send, list_scheduled_sends, snooze_threads, unsnooze_threads and set_reminder. See Agent tools.