Skip to content

Email Communication

Your agent communicates primarily through email. This guide explains how the email system works.

Every agent gets an email address based on your tier:

This is a real email address. You can send to it from any email client. Your agent’s replies come from the same address.

Resend webhook → TinyFat platform
Validate sender (allowed_senders)
Enqueue job to sandbox-queue
Agent runs one turn
Agent writes to /data/outbox/email/
Platform sends email via Resend
  • First message: 10-30 seconds (container cold start + agent thinking)
  • Subsequent: 5-20 seconds (depends on task complexity)

The agent runs one “turn” per email — it processes your message, uses tools if needed, and responds.

Only whitelisted email addresses can trigger your agent. This prevents:

  • Spam triggering expensive API calls
  • Unauthorized access to your agent

In the dashboard under Settings → Allowed Senders:

  • Exact match: [email protected] — only this address
  • Domain wildcard: @company.com — anyone at that domain

Your email is automatically added when you create the agent.

Send commands in the subject line or at the start of the email body:

CommandEffect
/clearStart a fresh session
/resumeList recent sessions
/resume abc1Resume specific session by hash
/compactCompress context to save tokens
/modelShow current model
/model haikuSwitch to Haiku (fastest, ~$0.001/msg)
/model sonnetSwitch to Sonnet (balanced, ~$0.015/msg)
/model opusSwitch to Opus (most capable, ~$0.075/msg)

To: [email protected]
Subject: /model sonnet
Body: (empty or anything)

Response:

✓ Switched to **sonnet** (Sonnet (balanced))
This will apply to your next message.

Responses maintain proper threading:

  • In-Reply-To header links to your original message
  • References header includes the full thread chain
  • Gmail, Outlook, Apple Mail all group replies correctly

Every response includes a footer showing session info:

---
[buddy:a1b2 | ↑38 ↓5.0k R663k W37k $0.687 18.7%/200k | claude-haiku-4-5]
PartMeaning
buddy:a1b2Agent name and session hash
↑38Input tokens (your message)
↓5.0kOutput tokens (response)
R663kCache read tokens
W37kCache write tokens
$0.687Cost for this turn
18.7%/200kContext usage (% of limit)
claude-haiku-4-5Model used

Use the session hash with /resume a1b2 to continue that specific conversation.

You can send attachments to your agent:

  • Images: Agent can view and analyze (PNG, JPG, GIF, WebP)
  • Documents: Agent can read text content (PDF, TXT, MD)
  • Files: Agent can process data (JSON, CSV, etc.)

Attachments are stored temporarily during the turn and available in the agent’s workspace.

Your agent can send emails with:

  • Multiple recipients: To, CC fields
  • Threading: Proper reply headers
  • Attachments: Files from the workspace

See Email JSON Reference for the full format.

  1. Check spam/junk folder
  2. Verify allowed senders includes your address
  3. Check dashboard for job status/errors
  1. Check if sender is whitelisted
  2. Look for errors in dashboard
  3. Verify API key is configured

Add [email protected] to your contacts or mark as “not spam”.