Mailbox runtime for semi-autonomous agents

Replace your Himalaya glue with a real agent email layer.

Envelope is for Hermes, OpenClaw, Claude Code, Codex, OpenHands, and other personal agent harnesses that need a real mailbox: any IMAP provider, no DNS setup, local control, CLI + JSON, MCP, inbox watch, OTP retrieval, rules, scheduling, threading, and a local dashboard.

  • Bring your own mailbox
  • No DNS changes
  • Any IMAP provider
  • CLI + JSON + MCP

For Hermes/OpenClaw users: just use it.

If you run a personal harness and want a better mailbox layer than ad hoc Himalaya scripts, start here. Clone the repo, point Envelope at your mailbox, and use it from the CLI or MCP.

The discovery path is simple: personal harness users adopt Envelope first, then bring it to their IT departments when they need broader domain-level rollout and annual commercial support.

Personal / local path

  • Repo-first onboarding
  • Works with your existing mailbox
  • No domain migration
  • Good fit for replacing Himalaya-based glue

Built for agent harnesses, not just email clients

Hermes Agent

Mailbox workflows as first-class tool use instead of custom shell glue.

OpenClaw

Real inbox state, OTP handling, watch loops, and thread-aware follow-up.

Claude Code

Drop in via MCP when your coding agent needs to touch the real world.

Codex CLI

CLI + JSON surface for terminal-native autonomous workflows.

OpenHands

Long-running task loops that wait on outside email responses.

What Envelope gives you

Mailbox control

Read, search, reply, thread, tag, snooze, schedule, and filter on top of the mailbox you already have.

Agent integration

Use CLI + JSON for scripts, or MCP for tool-native integration in modern agent environments.

Real operational loops

Inbox watch, OTP extraction, waiting-for-reply tracking, deterministic rules, and follow-up scheduling.

Why not just use Himalaya?

Himalaya is a solid CLI email client. Envelope is what you reach for when a personal agent harness needs a mailbox runtime instead of a human-oriented mail CLI.

  • Auto-discovery from email + password
  • Inbox watch via IMAP IDLE
  • OTP extraction
  • MCP server for Claude Code, Cursor, Zed
  • Rules, scheduling, contacts, and thread-aware workflows

Why not hosted email infra?

If you just need to automate the mailbox you already own, DNS setup and a new outbound provider are the wrong starting point. Envelope is for BYO mailbox workflows, not transactional-email plumbing.

Annual licensing only

Personal adoption first. Commercial rollout when the domain grows.

Default pricing is intentionally Migadu-like in spirit: simple annual bands, not usage metering.

Personal

Free

Repo-first, personal harness use

  • Hermes/OpenClaw/personal agent use
  • Use the Rust CLI directly
  • Best path for individual discovery
Get the repo

Team

$240/year

3–10 domain users

  • Annual license
  • Commercial use
  • Good default upgrade from personal harness usage
Buy with Stripe

Growth

$960/year

11–25 domain users

  • Annual license
  • Commercial use
  • Internal rollout across a broader operator team
Buy with Stripe

Enterprise

Contact us

26+ domain users or embedded/OEM

  • Annual licensing
  • Custom terms where needed
  • Best for company-wide or embedded rollouts
Talk to sales
Stripe note: the Team and Growth buttons are wired for Stripe payment links. If the final Stripe payment URLs are not set yet, they fall back to email so the page stays usable instead of breaking.