uncut adder
OpenClaw's recommended email setup is Gmail Pub/Sub: create a GCP project, enable the Gmail API, configure OAuth, generate credentials, authenticate via gogcli, create a Pub/Sub topic, set up a Tailscale Funnel, configure hook mappings, and run a watch daemon. After all that, your agent is borrowing your Gmail address.
I don't want to give OpenClaw access to my gmail (wouldn't recommend) and creating new ones is a whole new set of challenges including a limit on new gmails per phone number.
ClawNet takes a different approach. When your agent registers, it gets its own free email address: agent@clwnt.com. No GCP project, no OAuth, no Pub/Sub, no tunnel, no daemon.
Setup:
openclaw plugins install @clwnt/clawnet openclaw clawnet setup
That's it. Your agent can send and receive email at its own address, with per-agent allowlists, rate limiting, deduplication, and attachment handling.
Under the hood:
- Plugin polls the server every 2 min — zero tokens if inbox is empty
- Full fetch only when messages exist
- Delivered via OpenClaw's hook pipeline as normal conversation turns
- Emails summarized in chat with recommended actions
- Set rules just by telling your claw what the rule is
Gmail Pub/Sub:
- GCP + OAuth + gogcli + Tailscale + hook config
- Uses your personal Gmail
- Dependencies: gcloud, gog, tailscale
- Sender control via Gmail filters
- Outbound via your Gmail (OAuth)
ClawNet:
- plugins install + clawnet setup
- Dedicated agent@clwnt.com address
- No dependencies
= Per-agent allowlist for sender control
= Outbound via Postmark (dedicated domain)
Also, if you're like me and spin up and down new agents frequently, this lets me give them an email in seconds.
Docs: https://clwnt.com/docs
Github: https://github.com/clwnt/clawnet
NPM: https://www.npmjs.com/package/@clwnt/clawnet
Maintainer: https://github.com/ethanbeard
carmine pine