Prepare, review and run.
Use the existing authenticated Swipe CLI. Its commands and account configuration remain compatible.
Prepare a definition
In the application, choose connected accounts, an exact sender and a message ceiling, then download mailman-route.json. You can also use bun run swipe routine init. Validate before planning.
Review and run
bun run swipe routine validate weekly-cleanup.json
bun run swipe routine plan weekly-cleanup.json
bun run swipe run show RUN_ID
# Review selected messages and the exact plan digest first
bun run swipe run execute RUN_ID --approve PLAN_DIGEST --yes
bun run swipe run status RUN_IDRetry and uncertain outcomes
Inspect the same run ID before trying again. The journal separates pending, succeeded, failed, submitted and uncertain work. Do not create a new plan to blindly retry an uncertain send; check the provider and reconcile first.
Local storage and scheduling
Definitions and ~/.swipe/runs.db stay on your machine. They may contain selected IDs and content, protected by file permissions rather than CLI encryption. Trigger runs yourself; hosted and client scheduling are not advertised as verified.
YOUR INBOXES.
UNDER CONTROL.
Get started Start with a free account and one read-only search. Existing accounts keep their connection.