The official email plugin for OpenClaw

Yes. AgentMail is published on ClawHub, the OpenClaw plugin registry, under the @agentmail account with ClawHub’s Official badge. Install it with openclaw plugins install clawhub:@agentmail/agentmail. ClawHub lists twenty-five channel plugins for OpenClaw and every other one is a chat surface, so AgentMail is the email path.

Run openclaw plugins install clawhub:@agentmail/agentmail, then openclaw plugins enable agentmail, and set AGENTMAIL_API_KEY in the environment that runs the Gateway. Your agent can then create inboxes on demand, each a real addressable email address, with no Google account and no OAuth consent screen.

Configure the email channel under channels.agentmail with an inboxId and an allowFrom list. Inbound mail from an allowlisted sender drives an agent turn and the agent replies inside the same thread. Set AGENTMAIL_WEBHOOK_SECRET for Svix-signed webhook ingress, or leave it unset and the channel falls back to WebSocket. There is no polling loop to write.

Give it its own inbox rather than access to yours. AgentMail creates an addressable inbox by API in under a second, so the agent owns an address instead of borrowing your Google account. Nothing is shared, and a suspension cannot take your own mail down with it.

Run openclaw plugins install clawhub:@agentmail/agentmail, then openclaw plugins enable agentmail. Set AGENTMAIL_API_KEY in the environment that runs the OpenClaw Gateway, restart it with openclaw gateway restart, and confirm with openclaw plugins inspect agentmail --runtime.

A skill is a markdown instruction bundle that teaches an agent how to use tools it already has. A plugin is a code package that registers new runtime surfaces such as channels, tools, services, and HTTP routes. The AgentMail plugin ships both: a CLI-backed AgentMail skill, and an email channel that a skill alone could not provide.

Set AGENTMAIL_API_KEY in the environment that runs the Gateway. For a managed Gateway, ~/.openclaw/.env is the right place, so the channel and agent turns inherit the same credentials. Set AGENTMAIL_WEBHOOK_SECRET there too if you want Svix-signed webhook ingress. A channel-only inline key leaves the CLI-backed skill unavailable, so always set the environment variable.

The channel is default-deny. dmPolicy defaults to allowlist, and an empty allowFrom rejects every sender. Replies stay bound to the message that triggered them, so the agent cannot start threads or mail addresses you never approved. Every reply re-hydrates and re-authorizes the original sender, so a forged Reply-To cannot redirect delivery, and inbound mail is committed durably before it is acknowledged.

The email channel is reply-only by design: no proactive threads, no arbitrary recipients, replyAll disabled. Senders are checked against a default-deny allowlist you control. When you do need outbound sending, the CLI-backed skill covers it with an explicit inbox, recipient, and subject.

It is backed by the bundled AgentMail CLI rather than a fixed tool schema, so it reads the CLI’s own help output at runtime. It covers inboxes, messages, threads, drafts, webhooks, domains, pods, API keys, and any resource a future CLI release adds, without waiting for a new plugin version.

OpenClaw 2026.7.2 (beta) or newer, and Node 22.22.3 to 22.x, 24.15.0 to 24.x, or 25.9.0 and above. The published plugin bundles the official AgentMail CLI for macOS, Linux, and Windows, so a separate global CLI install is not required.

No. ClawHub’s twenty-five channel plugins are chat surfaces. Gmail access from OpenClaw comes from community skills such as gogcli, or from wiring the Gmail API yourself through a Google Cloud project and an OAuth consent screen. That path carries account-ban risk, refresh-token expiry, and a 500-a-day send cap on free accounts.

The Gmail API was built for human accounts and needs OAuth, so agent traffic risks suspension and inboxes cannot be created programmatically. SendGrid sends only, with no receiving, no threading, and no reply parsing. AgentMail gives an OpenClaw agent a dedicated inbox it creates on demand, sends from, receives on, and reads with full thread context.

No. npx clawhub@latest install agentmail and npx skills add agentmail-to/agentmail-skills still work and remain useful for non-OpenClaw agents such as Claude Code and Cursor. For OpenClaw, the plugin is the recommended install because it includes the skill and adds the email channel.