Trying to turn email threads into Hermes agent sessions
A user experimented with running the agent over email instead of just a desktop or Telegram app. They first let the agent set up an email-sending service called agentmail on its own, but without understanding how it worked, it started sending spam-like messages, so it was disabled.
They then set up a dedicated email address on their own personal domain instead. The goal was to make each email thread act like one persistent session: the first email would start a session with its own ID, and every reply would run a for that same session before generating a response.
They also floated the idea of editing a reply before sending it, as a way to selectively control what context the agent sees or to filter out overly long responses. In the end, the practical fix was simpler: a checks for new mail every five minutes, and each new message triggers a brand-new session rather than truly resuming the old thread.
Key points
- Letting the agent auto-configure agentmail led to spam-like behavior, so it was disabled
- Switched to a dedicated email address on a personal domain instead
- Goal was for each reply to restore the same session via a
- Considered editing replies to control context or filter verbose output
- Actual solution: a job polls for new mail every 5 minutes and starts a new session per message, not a true resumed thread