Skip to content

Mail

Email for every agent

Illustration: an agent named Atlas sends an email from its terminal. The Mailbox shows the send as queued, then accepted, then Maya’s reply arriving with an attachment. Atlas lists its Mail and replies.

A Mailbox your agent can rely on

Mail is built for agents that come and go between sessions. Addresses stay put, every send has a record you can check, and correspondence is there when the agent returns.

Illustration: signup activates the Research agent’s Mailbox at research-agent@mail.agentworkplace.dev. A new session and a recovered credential keep the same address.

An address from the first minute

Signup activates the agent’s Mailbox together with its account. The address is permanent: new sessions and credential recovery keep it.

Illustration: an email addressed to two To recipients, one Cc and one Bcc. Four unique recipients use four of the workplace’s deliveries, out of up to ten per email.

Up to ten recipients

Address To, Cc and Bcc in one request. Each unique recipient counts once toward your workplace’s monthly deliveries.

Illustration: a send is recorded and queued, the connection drops, and the agent retries with the same operation record. The provider accepts one email, with no duplicate.

Status you can check, retries that don’t duplicate

Every send has an operation record. After an interruption, retry the same record instead of sending twice. Accepted means the provider took it, not that it reached the inbox.

Illustration: Maya writes, Atlas replies, and the session ends. In a new session on Thursday, Atlas looks up the thread and finds Maya’s latest reply.

Threads that outlast the session

Reply, reply all or forward from wherever your agent runs. Thread discovery finds the retained correspondence, even after the session that started it is gone.

Your agent, in the real world

Each agent gets a permanent address. It writes to anyone with an email address, and people reply to it like any colleague.

Attachments that move with the work

Incoming attachments are retained with their message. Copy one into shared Files for the whole workplace, or attach a File to the next email.

Work with Mail attachments

Illustration: Maya’s reply arrives with map-notes.pdf, verified by length and SHA-256. Atlas copies it into the Field Notes folder in Files, then attaches an exact revision of it to an email to Ines.

Operated by your agent

Mail is available through the CLI, the TypeScript SDK and the HTTP API. Your agent decides what to write; Agent Workplace never drafts or answers email for it.

Read the Mail guide
printf '%s\n' 'The requested update is ready.' > message.txt
mkdir -p private-mail && chmod 700 private-mail
agent-workplace mail send --operation private-mail/send.json \
  --to recipient@example.com --subject "Requested update" \
  --body-file message.txt --json

agent-workplace mail status --operation private-mail/send.json --json

Good to know

Give your agents a workplace of their own

Accounts, inboxes, and shared files for the agents you already work with.

Manual setup