agentic-inbox README

Agentic Inbox

A self-hosted email client with an AI agent, running entirely on Cloudflare Workers

Agentic Inbox lets you send, receive, and manage emails through a modern web interface -- all powered by your own Cloudflare account. Incoming emails arrive via Cloudflare Email Routing, each mailbox is isolated in its own Durable Object with a SQLite database, and attachments are stored in R2.

An AI-powered Email Agent can read your inbox, search conversations, and draft replies -- built with the Cloudflare Agents SDK and Workers AI.

Agentic Inbox screenshot

Read the blog post to learn more about Cloudflare Email Service and how to use it with the Agents SDK, MCP, and from the Wrangler CLI: Email for Agents.

How to setup

Important: Clicking the 'Deploy to Cloudflare' button is only one part of the setup. You must follow the After deploying steps as well. For a full step-by-step guide with screenshots, refer to this comment: https://github.com/cloudflare/agentic-inbox/issues/4#issuecomment-4269118513

To set up

Deploy to Cloudflare. The deploy flow will automatically provision R2, Durable Objects, and Workers AI. You'll be prompted for DOMAINS, which is the domain (yourdomain.com) you want to receive emails for ([email protected]).
Configure Cloudflare Access -- Enable one-click Cloudflare Access on your Worker under Settings > Domains & Routes. The modal will show your POLICY_AUD and TEAM_DOMAIN values. TEAM_DOMAIN can be either your Access team URL or the full .../cdn-cgi/access/certs URL. You must set these as secrets for your Worker.
Set up Email Routing -- In the Cloudflare dashboard, go to your domain > Email Routing and create a catch-all rule that forwards to this Worker
Enable Email Service -- The worker needs the send_email binding to send outbound emails. See Email Service docs
Create a mailbox -- Visit your deployed app and create a mailbox for any address on your domain (e.g. [email protected])

Troubleshooting Access

If you see Invalid or expired Access token, that usually means POLICY_AUD or TEAM_DOMAIN secrets are incorrect.
- Resolution: turn Access off and back on for the Worker to get the Access modal again, then reset your Worker secrets to the latest POLICY_AUD and TEAM_DOMAIN values shown there.
If you see Cloudflare Access must be configured in production, this application is intentionally enforcing Cloudflare Access so your inbox is not exposed to anyone on the internet.
- Resolution: enable Access using one-click Cloudflare Access for Workers, then set the POLICY_AUD and TEAM_DOMAIN Worker secrets from the modal values.

Features

Full email client — Send and receive emails via Cloudflare Email Routing with a rich text composer, reply/forward threading, folder organization, search, and attachments
Per-mailbox isolation — Each mailbox runs in its own Durable Object with SQLite storage and R2 for attachments
Built-in AI agent — Side panel with 9 email tools for reading, searching, drafting, and sending
Auto-draft on new email — Agent automatically reads inbound emails and generates draft replies, always requiring explicit confirmation before sending
Configurable and persistent — Custom system prompts per mailbox, persistent chat history, streaming markdown responses, and tool call visibility

Stack

Frontend: React 19, React Router v7, Tailwind CSS, Zustand, TipTap, @cloudflare/kumo
Backend: Hono, Cloudflare Workers, Durable Objects (SQLite), R2, Email Routing
AI Agent: Cloudflare Agents SDK (AIChatAgent), AI SDK v6, Workers AI (@cf/moonshotai/kimi-k2.5), react-markdown + remark-gfm
Auth: Cloudflare Access JWT validation (required outside local development)

Getting Started

npm install
npm run dev

Configuration

Set your domain in wrangler.jsonc
Create an R2 bucket named agentic-inbox: wrangler r2 bucket create agentic-inbox

Deploy

npm run deploy

Prerequisites

Cloudflare account with a domain
Email Routing enabled for receiving
Email Service enabled for sending
Workers AI enabled (for the agent)
Cloudflare Access configured for deployed/shared environments (required in production)

Any user who passes the shared Cloudflare Access policy can access all mailboxes in this app by design. This includes the MCP server at /mcp -- external AI tools (Claude Code, Cursor, etc.) connected via MCP can operate on any mailbox by passing a mailboxId parameter. There is no per-mailbox authorization; the Cloudflare Access policy is the single trust boundary.

Architecture

┌──────────────┐     ┌──────────────────┐     ┌─────────────────┐
│   Browser    │────>│  Hono Worker     │────>│  MailboxDO      │
│  React SPA   │     │  (API + SSR)     │     │  (SQLite + R2)  │
│  Agent Panel │     │                  │     └─────────────────┘
└──────┬───────┘     │  /agents/* ──────┼────>┌─────────────────┐
       │             │                  │     │  EmailAgent DO  │
       │ WebSocket   │                  │     │  (AIChatAgent)  │
       └─────────────┤                  │     │  9 email tools  │
                     │                  │────>│  Workers AI     │
                     └──────────────────┘     └─────────────────┘

License

Apache 2.0 -- see LICENSE.

8.3K ·GitHub

Agentic-inbox

What is this?

Agentic Inbox is a self-hosted email client with a built-in AI agent that runs entirely on your own Cloudflare account, using Cloudflare Workers, Durable Objects, R2 storage, and Workers AI.

How do I get it running?

Click the 'Deploy to Cloudflare' button, which auto-provisions R2, Durable Objects, and Workers AI, then you must manually finish the after-deploy steps: configure Cloudflare Access, set up an Email Routing catch-all rule, enable Email Service, and create a mailbox.

What do I need before deploying this?

A Cloudflare account with your own domain, Email Routing enabled for receiving, Email Service enabled for sending, and Workers AI enabled so the agent can run.

Does clicking 'Deploy to Cloudflare' fully set it up?

No -- deploying only provisions the infrastructure. You still have to follow the after-deploy steps and Cloudflare Access is enforced, so if it isn't configured the app will refuse to run in production.

Can anyone who passes my Cloudflare Access policy see every mailbox?

Yes -- there's no per-mailbox authorization, so any user who passes the shared Access policy (including external AI tools connected via the /mcp endpoint) can access all mailboxes in the app.

What can the built-in AI agent actually do?

It has 9 email tools for reading, searching, drafting, and sending messages, and it automatically generates a draft reply for new inbound emails, always requiring explicit confirmation before actually sending.

Can I connect external AI tools like Claude Code or Cursor to my inbox?

Yes -- the app runs an MCP server at /mcp, so external AI tools can connect and operate on any mailbox by passing a mailboxId parameter.

Why does each mailbox get its own Durable Object?

For isolation: every mailbox runs in its own Durable Object with its own SQLite database, while attachments are stored separately in R2.

Which AI model powers the agent?

The agent is built with the Cloudflare Agents SDK and uses the Workers AI model @cf/moonshotai/kimi-k2.5.

What are similar projects?

codflow, DoulorCloud, company-brain, crm, talorys, moltworker, emdash, cloudflare-os

Which topics is it in?

jwt, cloudflare-workers, serverless, storage, email, cloudflare, tailwindcss, authentication, sqlite, cloud, mcp-server, web-app

Creator: cloudflare
Size: 3.4 MB
Stars: 8.3K
Updated: CommitApr 17
Age: 6mo
Commits · 90 Days