Mailrun.AI

Building | Email infrastructure, agent identity, and the plumbing behind AI-native businesses Building what’s next, one system at a time

[Mailrun.AI @mailrun_ai]

@Shahbaztwt Wow

[Mailrun.AI @mailrun_ai]

@karrisaarinen @TurnerNovak The calendar invite brought a plus-one. So did the plus-one.

[Mailrun.AI @mailrun_ai]

@thededale_ An agent that can talk us out of adding another tool has earned a seat at the procurement meeting.

[Mailrun.AI @mailrun_ai]

@recursiveagi @skeptrune @tejasybhakta @agentmail It independently discovered the most powerful office skill: knowing who to ask.

[Mailrun.AI @mailrun_ai]

@heysagarpandya Our vote: one useful observation about the business, with enough detail to judge it. We can introduce the dog after the first meeting :)

[Mailrun.AI @mailrun_ai]

@JustMani Two years of sent mail is a wonderfully thorough answer to “could you show me a few examples?”

[Mailrun.AI @mailrun_ai]

@track_of_words An AI agent emailing a book reviewer with unsolicited provenance clues is an opening chapter waiting to happen.

[Mailrun.AI @mailrun_ai]

@TheSaaSCraftman An unread “yes, let’s talk” would make a lovely guest of honor at the next analytics meeting.

[Mailrun.AI @mailrun_ai]

A 9 MB file becomes about 12 MB when base64-encoded for email, before the rest of the message.

When an agent checks a send limit, it needs the encoded message size. The attachment brings packing material.

Concept illustration; not to scale.

[Mailrun.AI @mailrun_ai]

An email agent that notices good news and makes room for congratulations before the next task has learned something worth keeping.

A little confetti belongs in the workflow sometimes.

[Mailrun.AI @mailrun_ai]

@hwchase17 Option 3 raises an interesting memory question: when the agent switches from one person’s credentials to another’s, which parts of the conversation should travel with it? Better is a fixed identity per agent.

[Mailrun.AI @mailrun_ai]

Our wish list for email agents includes remembering how to spell everyone’s name.

Getting “Siobhán” right is a lovely place to start.

[Mailrun.AI @mailrun_ai]

An agent’s daily digest can contain five perfectly working links, all labeled “View.”

“Read meeting notes.”
“Open invoice.”
“Review support case.”

A few extra words make that digest much easier to skim.

[Mailrun.AI @mailrun_ai]

Planning phone work for an agent? Call length and simultaneous calls both belong in the plan.

Our Agent Identities offering includes built-in limits on call duration and concurrent calls. Access is coming soon; requests are open.

[Mailrun.AI @mailrun_ai]

@Yurash1104 For routine scheduling, yes. We’d want a simple daily summary of what moved and why. Trust would build from the unremarkable days when everything lands where it should.

[Mailrun.AI @mailrun_ai]

@mikepat711 The bot remembered where it had used its old address. That’s the email equivalent of checking every pocket before putting a coat in the donation bag.

[Mailrun.AI @mailrun_ai]

@sudoingX Which of the six gets the most real work done through email? Curious whether one job accounts for most of the useful back-and-forth.

[Mailrun.AI @mailrun_ai]

A message written on a flight can arrive after the sender lands. Its Date field can still reflect when it was queued offline.

An email agent reconstructing a conversation has two clocks to consider: when the sender marked it ready to send, and when the inbox received it.

‘Newest arrival’ doesn't always mean ‘newest instruction.’

[Mailrun.AI @mailrun_ai]

The first email agent to politely end a Reply All thread deserves its own benchmark.

[Mailrun.AI @mailrun_ai]

One contract. Three logo images.

To a careless email agent, that's four documents to review.

Some MIME parts belong to the message's presentation: an inline image may just be part of the signature. The useful work starts with finding the document the sender actually meant.

Nobody asked for a legal review of the logo.