i love what workos is doing and i also spoke at their event already. we think this is complementary - we're not setting out to create a new standard, we're giving better access to what already exists.
thanks for the feedback! it is top of mind for us, and we've done our research to prevent this as much as possible. it is constantly ongoing and we never settle in our measures to protect against this
This was likely a free tier user. We do this intentionally and don't allow free users to send from custom domains, so you can have a easier time identifying LLM emails. In this case, it seemed like it worked :)
Appreciate the concern Mike, and I actually read your email complaining, which helped us ship this next feature. We have a "sent via AgentMail" footer being added soon to outbound emails to identify emails coming from LLM's.
We also are working on adding more robust checks and LLM-based filtering to prevent messages which contain spam or outbound-like copy.
Re; AgentMail next to Claude, we're working on stateful inboxes which help agents actually recall and understand what they're sending and to who. The goal is to provide the rails for intelligent actors rather than slop.
agreed from a fundamental level. but i think being an intelligent and aware as an autonomous entity requires capabilities beyond sending. agents will need to have contextual awareness of the messages they send and receive
We know the founder of this pretty well actually. It's not really an alternative. They are an MCP that is building an email-like layer for coding agents to talk to each other. We are an actual email inbox provisioned via API for agents to email agents or humans.
we have a few things in place, allowlists and permissions act as a layer. also beginning some work on prompt isolation within api soon. but having an isolated identity + data within a separate agentic inbox also puts less risk of your personal email data being injected - which is most people's main concern
Cloudflare/SES works if you want raw email sending and receiving. If you want threading, parsing, storage, retrieval, logic, filtering, labeling, search -- you'll need to build it out yourself.
We're devs ourselves so ik the first thought is usually "how hard can it be?" in our validation, we thought it was hard enough to build a startup around :) these things are easier said than done, and no one in 2026 should be stitching together email workflows. especially not agents