Build an email agent that can survive a restart
Design an email agent that can recover after a crash. Learn how to persist event cursors, deduplicate work and retry sends without creating another message.
The Cyberpigeon blog
Notes on building agents that work with email. Practical decisions, from the first inbox to the reply that reaches its destination.
Give your agent an inbox with clear boundaries
Start an email agent with one inbox and read-only access. Separate untrusted email from instructions, review replies and keep permission controls outside the model.
Queued, sent, delivered: what happened to your email?
Understand Cyberpigeon email statuses, from a 202 queued response to provider delivery events. Handle retries, uncertain outcomes, bounces and complaints accurately.