BUILD RECORD
AgentsThatEmail
The agent lived in email, where the work already happened. Forward the thread, and the people on it get the decisions and open questions back in their inbox.
Product build
The only thing to learn was an address.
An email-native summarizer. A forwarded thread got one instruction, summarize this and surface the action items, and the answer came back to everyone on it.
Proved on the inbox what Everything-Bot proved in the group chat: an agent is worth more on the surface the work already uses than behind an app of its own.
1 address, the entire front door. No app, no account.
A mail service caught it, a function read it, a model summarized it.
Solo. Architecture, serverless build, prompt, operations.
~1 min from forward to reply, the same summary to every recipient.
Address to reply
How it answered inside the inbox
Arrived as mail
AWS SES caught anything sent to the bot's address.
Stored the raw mail
SES put the untouched message in S3, so parsing read the original.
Parsed and summarized
A Lambda pulled the thread text and recipients, then called GPT.
Answered in the inbox
SES answered everyone except the bot.
Limits stay attached
What it refused to do
Every reply said AI wrote it, in the message.
The bot was cut from the reply list, or it would have answered itself.
Thread text went to a hosted model. No local option.
One template, no memory, nothing running between forwards.
Record and lineage
Where it went
Everything-Bot started it at a hackathon. letmecheckbot took it to the group chat.
One address, one instruction, an answer where the question was asked.
THE ARCHITECTURE
A RELATED PROBLEM
Decisions still getting trapped in email?
This build is retired, but the handoff problem is not. If a team needs a reliable record from the thread it already uses, send me the shape of it.