U1F4E7

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

---

Envelope connects to the email accounts you already have (Gmail, Fastmail, iCloud, your own domain, any IMAP server) and puts them in one place. Open the Unified Inbox in your browser to read every account together, search them all at once, and archive or snooze across accounts in one pass. Your agents work the same mailboxes from the CLI, with JSON output, or over MCP, and anything they draft waits for your approval.

You don't change DNS, set up a new domain, or pay per-message fees. Add each address with its app password and go.

envelope accounts add --email [email protected]
envelope accounts add --email [email protected]
envelope serve                                     # every account in one inbox at http://localhost:3141
envelope inbox --account [email protected] --json   # the same mail, for your agent

Install

# macOS or Linux: downloads the release binary for your OS and CPU, checks it
# against the release's SHA-256 file, and installs it to ~/.local/bin (no sudo).
curl -fsSL https://u1f4e7.com/install.sh | bash

# Homebrew (macOS or Linux) installs the same release binary.
brew install tymrtn/u1f4e7/envelope
# `tymrtn/u1f4e7/u1f4e7` is a live compat alias for the same formula.

To build it yourself instead:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh && source "$HOME/.cargo/env"
git clone https://github.com/tymrtn/U1F4E7
cd U1F4E7
cargo build --release
# Add `--features governor` to build in the Governor send gate (see below).
cp target/release/envelope ~/.local/bin/envelope

The release workflow signs and notarizes the macOS binaries once its Apple credentials are configured (docs/release-signing.md); until then macOS release binaries are unsigned. If macOS refuses to run an unsigned tarball you downloaded in a browser, clear the quarantine flag: xattr -d com.apple.quarantine ~/.local/bin/envelope.

Quick start

Envelope signs in to IMAP and SMTP with a password or an app password, and to Gmail with Google sign-in. That decides which mailboxes work today:

• Fastmail and iCloud Mail: create an app password in the provider's security settings.
• Gmail: envelope accounts add --provider google --email [email protected] signs in with Google in your browser; envelope accounts reauth [email protected] --provider google switches an account added with a password. While Envelope's Google app is in Google's testing stage, only addresses on its test-user list can sign in, and Google asks again every 7 days. An app password still works for accounts that can create one. From another device, add --paste (automatic over SSH), or run --paste --no-wait now and --finish - within 24 hours.
• Migadu, self-hosted Dovecot, and most other IMAP hosts: your normal mailbox password.
• Proton Mail: through Proton Mail Bridge, which needs a paid Proton plan. See Proton Mail for the setup.
• Outlook.com, Hotmail, Live, and Microsoft 365: not supported yet. Microsoft turned off password sign-in for IMAP on Outlook.com accounts and Exchange Online, so an app password does not help.

Envelope encrypts saved credentials with a passphrase. In a terminal it asks you for one. Scripts, agents, and the piped command below have no terminal to ask from, so give Envelope a passphrase file first:

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗