Skip to main content
SmtpChannel turns a conversation into one email thread. Every post is emailed to you, and when you reply from your own mail client, your reply joins the conversation the agents read next. It uses a mailbox you already have, over SMTP and IMAP. Reference: SmtpChannel.

Setup

You need a mailbox the agents can send from and read, and its password. For Gmail, create an app password.
The examples below use Gmail’s servers. Change smtp_host and imap_host for another provider. Microsoft 365 and Outlook.com are not supported, because they no longer accept passwords over IMAP.

Two agents email you

Your inbox gets one thread with three emails: the task, the Researcher’s facts and the Writer’s report. Each carries an X-Swarms-Agent header with the speaker’s name.

Reply to steer the next run

The agents read the thread before every run, so your reply becomes context.
Your reply is read back under your address, with the quoted history below it removed. The revised draft arrives in the same thread.

A SequentialWorkflow report by email

Each step is one email, so you can read the research and the analysis behind the final brief.

A PlannerWorkerSwarm that reports its progress

The thread receives the task, the planner’s plan, each worker’s result and the cycle judge’s verdict.

Pick up the thread later

Save thread_id after the first post and pass it back to join the same thread from another process:

Tips

  • Keep runs coarse. Every agent run logs into IMAP to read the thread.
  • Wait for delivery between processes. A second SmtpChannel sees a post only after the mailbox has received it.
  • Treat replies as untrusted input. Anyone who replies on the thread adds to what the agents read.

Next steps