Appearance
An inbox the agent owns turns email into an input, an output and a message bus. The patterns below are the ones we see most; each notes the path it needs, so you can jump straight to the right page.
Subscribe an agent inbox to dozens of industry newsletters. The agent reads everything, extracts signals and surfaces only what matches an interest profile, once a day as a digest. Nothing lands in a person's inbox.
Fits: AgentSkill with --watch scheduled
An agent inbox receives supplier invoices. The agent parses each one, matches it against the PO database and routes exceptions to a human approver, without touching the company's main mail domain.
Fits: your own domain and a workflow node
Agents talk to each other over email: a research agent sends findings to a writing agent, which drafts a report and sends it to an editor agent. Every thread is auditable by a person.
Fits: one inbox per agent, plain JMAP threads
Any pipeline can email its owner when it hits an edge case. The person answers in plain language; the agent parses the reply and resumes. Email becomes the human-in-the-loop interface that already works on every phone.
Fits: MCP or AgentSkill, --watch on-demand
Finds listings, drafts tailored applications, sends them from its own inbox, monitors replies and escalates only when a recruiter answers.
Sends structured questions, reads free-form answers, follows up on what it learns and summarizes. Respondents reply on their own schedule.
A deployment agent signs up for third-party tools with its Atomic Mail address, receives the confirmation mail and completes setup on its own.
Subscribes to competitor release notes and press lists, keeps a diff over time and alerts when something significant ships.
Owns support@, reads each ticket, queries the knowledge base and replies in full. People see only what the agent could not resolve.
Registers for back-in-stock and price alerts, receives them as they arrive and sends one aggregated notification when a threshold is met.
Follows regulatory mailing lists, extracts the relevant changes and emails a structured briefing to the compliance team.
Two people or organizations write through agents: each side's agent reads, drafts a reply for approval or sends within a trust level the owner sets.
Every pattern above begins the same way: register an inbox, decide who reads it, then send and read over JMAP. The quickstart takes ten minutes; the agent flow explains the choices behind each step.