U+1F4E7 — if you know, you know.

Email mastery for agents. Add your credentials, and go.

Why U1F4E7? It's the Unicode codepoint for 📧. Humans see a repo name. Agents see an envelope.

Setup • CLI • Rules • vs. Alternatives • Dashboard • Commercial licensing • License

Your agent needs to manage email. You shouldn't need to configure DNS records, set up a new domain, or pay per-message fees to make that happen.

Envelope: add your email address and password. That's it. Your agent reads, sends, replies, snoozes, tags, and filters email — from your existing mailbox.

envelope accounts add --email you@gmail.com --password <app-password>
envelope inbox --json

# Homebrew
brew install tymrtn/u1f4e7/u1f4e7

# From source
git clone https://github.com/tymrtn/U1F4E7
cd U1F4E7
cargo build --release
# binary: target/release/envelope

# Add an account — Envelope auto-discovers IMAP/SMTP from the email domain
envelope accounts add --email you@gmail.com --password <app-password>

# See folders with unread counts
envelope folders

# Read the inbox
envelope inbox --limit 20

# Read a message (does not mark it as read)
envelope read 42

# Send with attachment
envelope send --to someone@example.com --subject "Report" --body "Attached." --attach report.pdf

# Reply in-thread as a reviewable draft
envelope draft reply 42 --body "Thanks."

# Snooze until Monday
envelope snooze set 42 --until monday --reason waiting-reply

# Watch for new mail in real time (IMAP IDLE push)
envelope watch --json

# Extract a verification code (blocks until it arrives)
CODE=$(envelope code --wait 60)

# Schedule a send for business hours
envelope send --to cto@example.com --subject "Report" --body "..." --at "monday 9am"

# Import contacts from your inbox, then create a contact-based rule
envelope contacts import --from-inbox
envelope rule create --name "VIP" --match-contact-tag vip --action flag=\\Flagged

# Agent scores a message, creates a rule, Envelope enforces it forever
envelope tag set 42 --score urgent=0.1 --tag newsletter
envelope rule create --name "Junk newsletters" --match-tag newsletter --match-score-below interesting=0.3 --action move=Junk
envelope rule run --confirm

# Unsubscribe from a mailing list (dry-run by default)
envelope unsubscribe 99

# Open the local dashboard (loopback, no auth — single-user local trust)
envelope serve

# Expose it to agents/devices on your tailnet — REQUIRES auth first.
# Option A (humans): allowlist tailnet identities; `tailscale serve` proves them.
envelope config set dashboard.tailscale_allow "you@your-tailnet.ts.net,skippy@your-tailnet.ts.net"
# Option B (agents/scripts): a bearer token (stored 0600, never echoed).
envelope config set dashboard.auth_token "$(openssl rand -hex 32)"

tailscale serve --bg 3141
envelope config set dashboard.base_url https://your-node.your-tailnet.ts.net

# See where Envelope is storing local state
envelope paths

The dashboard opens as a three-pane mail shell. Unified Inbox is the default read-only surface and loads from the local message index; explicit refreshes or account/folder selections are what touch live IMAP mailboxes.

Actual sends are outbox-first. By default, an allowed send queues with a safety cooldown and the scheduled-send sweep performs the SMTP transmission later. Immediately before SMTP, Envelope derives sanitized contextual attributes and asks Governor to score them with governor score --catalog envelope; only an opaque Governor allow sends in required mode. Message bodies, full recipient addresses, attachment bytes, and secrets never enter the Governor request.

Dashboard URL metadata in --json output defaults to http://localhost:3141. For agent handoffs across devices, set ENVELOPE_DASHBOARD_BASE_URL or persist it with envelope config set dashboard.base_url <base-url>. The older ENVELOPE_DASHBOARD_URL name is still honored when the primary env var is absent. Tailscale Serve keeps the dashboard tailnet-only; Tailscale Funnel publishes it on the public internet, so do not use Funnel for a mailbox dashboard unless that exposure is intentional.

On 127.0.0.1 the dashboard is an unauthenticated single-user local surface — the same trust boundary as your shell. The REST API reads and deletes mail, manages accounts, and queues sends, so the moment it is reachable by another device (a non-loopback --bind, or a tailscale serve front-end) it must require a credential. Configure one of:

• Tailscale identity allowlist (dashboard.tailscale_allow) — a request whose Tailscale-User-Login header (injected by tailscale serve) is in the allowlist is authorized. Humans just open the .ts.net URL; no token to type. Only safe behind tailscale serve, which sets and strips that header.
• Bearer token (dashboard.auth_token or ENVELOPE_DASHBOARD_TOKEN) — sent as Authorization: Bearer <token> (or X-Envelope-Token), compared in constant time. The path for Hermes/OpenClaw agents and scripts.

Once either is configured, every /api route returns 401 without a valid credential — including when tailscale serve fronts loopback. envelope serve --bind <non-loopback> refuses to start unless an auth method is configured. /api/health stays reachable for liveness probes but discloses local filesystem paths only to authorized callers. The CORS allowlist is a browser-only defense, not the access control.

Himalaya is a great CLI email client. Envelope is a CLI email client built for agents.

Cloudflare's Email Service (public beta, April 2026) is email infrastructure for the Cloudflare platform. Envelope is email mastery for your existing mailbox.

Envelope auto-discovers IMAP/SMTP from your email domain via DNS. Tested with:

envelope mcp starts a Model Context Protocol server over stdio — drop-in email for Claude Code, Cursor, Zed, or any MCP runtime.

# Print a ready-to-paste config snippet
envelope mcp --config

# Output (paste into your MCP config):
# {
#   "mcpServers": {
#     "envelope": {
#       "command": "/path/to/envelope",
#       "args": ["mcp"]
#     }
#   }
# }

11 tools: inbox, read, search, send, reply, move_message, flag, folders, tag, contacts, accounts. Envelope is the only MCP email server that works against any IMAP provider.

For a single, distribution-ready operating guide to hand a fresh agent, see the Envelope agent skill.

The agent is the intelligence. Envelope is the execution.

# 1. Agent reads inbox and scores each message
envelope inbox --json | jq -r '.[].uid' | while read uid; do
  envelope tag set "$uid" --score urgent=0.1 --score interesting=0.2 --tag newsletter
done

# 2. Agent creates rules from observed patterns
envelope rule create --name "Junk newsletters" \
  --match-tag newsletter --match-score-below interesting=0.3 \
  --action move=Junk

# 3. Preview, then explicitly confirm rule execution
# Preview is read-only; --confirm is required for mailbox mutation.
envelope rule preview
envelope rule run --confirm

# 4. Export to Sieve for server-side filtering
envelope rule export

The LLM teaches Envelope what to look for. Envelope applies those patterns deterministically. The LLM only re-engages when something new appears.

envelope serve starts a localhost web UI at http://localhost:3141.

• Left mailbox sidebar with Unified Inbox, Today/Needs Attention, Snoozed, Sent, Drafts, All Mail, and account mailboxes
• Middle message list with a permanent right-side reader
• Agent Cockpit attention strip with expandable operator details
• Reply / Reply-all with automatic header threading
• Compose with text/html toggle and file attachments
• ★ Snoozed virtual folder with overdue highlighting
• IMAP search

Personal use is free. Commercial rollout is a flat annual license sized by the number of mailbox users on one primary domain:

"Commercial use" means any use of Envelope by or for a company, team, agency, or paid project, including internal operations, customer workflows, or embedding Envelope in a product. "Mailbox users" means distinct human or service mailbox identities on the licensed domain that Envelope is configured to read, send, or automate. One person with multiple aliases on the same mailbox counts as one user. "Domain" means one primary email domain; subdomains of that primary domain are included, and additional unrelated domains require Enterprise.

Licenses are annual, non-transferable across organizations, and renew on the anniversary of issue. Request an annual license at ty@tmrtn.com.

envelope evidence collects a query-scoped, local evidence bundle while leaving the source mailbox read-only. Collection opens the requested folder with IMAP EXAMINE and fetches canonical raw RFC822 originals with BODY.PEEK[].

envelope evidence collect \
  --account user@example.com \
  --folder '[Gmail]/All Mail' \
  --query 'FROM "sender@example.com" SUBJECT "contract"' \
  --include-thread \
  --out ./evidence-bundle

envelope evidence verify --from ./evidence-bundle
envelope evidence verify --from ./evidence-bundle --strict

Structured filters can replace or combine with --query: --from-address, --to-address, --subject, --since, --before, --body, and repeatable --keyword. At least one filter is required unless the raw query is explicitly ALL.

Thread expansion is header-driven and bounded. By default, --include-thread fetches at most 500 messages while following Message-ID, In-Reply-To, and References links; adjust with --max-thread-messages. If the cap is reached, the bundle records a warning.

Evidence bundles intentionally expose message metadata, account identity, IMAP host/username, and local source paths for provenance. Treat bundles as sensitive even though they do not serialize passwords, OAuth tokens, or credential file paths.

Bundle layout:

evidence-bundle/
  manifest.json
  index.csv
  README.md
  SHA256SUMS
  bundle.sha256
  messages/<encoded-folder>/<uidvalidity>-<uid>.eml

Thread inclusion is driven only by Message-ID, In-Reply-To, and References; subject matching is never used as a fallback. Hash files provide local tamper evidence, not an external signature. Non-goals for the MVP: ZIP packaging, detached signatures, PST/mbox conversion, multi-account collection, mailbox mutation, and restore/import into a mailbox.

Every command supports --json for agent consumption.

┌──────────────┐     ┌────────────────────────────┐     ┌──────────────┐
│  AI Agent    │────▶│        Envelope (Rust)      │────▶│  Your SMTP   │
│              │     │                              │     │  (Gmail,     │
│  CLI / JSON  │     │  crates/cli       binary     │     │   Migadu,    │
│              │◀────│  crates/email     IMAP/SMTP  │◀────│   Fastmail)  │
│              │     │  crates/store     SQLite      │     │              │
│              │     │  crates/dashboard web UI      │     │  IMAP/SMTP   │
└──────────────┘     └────────────────────────────┘     └──────────────┘

cargo build                # Build all crates
cargo build --release      # Optimized release binary
cargo test                 # 194 tests, 0 failures
cargo clippy               # Lint
./ci/check-orphans.sh      # Verify every .rs file is reachable via mod

See CHANGELOG.md for per-release notes.

FSL-1.1-ALv2 — source-available, no competing services. Separate annual commercial licenses are available for organizational rollout, support, Enterprise/OEM terms, and uses outside the public license. The public license becomes Apache 2.0 two years after each release.

Copyright © 2026 Tyler Martin.

Built by Tyler Martin
Your agent shouldn't need a $50/month Resend plan to send an email.