cloudflare/agentic-inbox is a TypeScript project with 8.8k stars. A self-hosted email client with an AI agent, running entirely on Cloudflare Workers
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
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.
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
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.
TopGit's last sync did not record any GitHub topics for cloudflare/agentic-inbox. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on cloudflare/agentic-inbox?
The most recent commit recorded on cloudflare/agentic-inbox was 7 months ago, based on the GitHub push timestamp. The repository has 1.2k forks — one of the better signals of community interest.
How many stars does cloudflare/agentic-inbox have?
cloudflare/agentic-inbox has 8.8k GitHub stars — refresh the page for the live number, or check github.com/cloudflare/agentic-inbox. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What is cloudflare/agentic-inbox?
cloudflare/agentic-inbox (cloudflare/agentic-inbox) is a TypeScript project on GitHub. From the project's own README: A self-hosted email client with an AI agent, running entirely on Cloudflare Workers
What language is cloudflare/agentic-inbox written in?
cloudflare/agentic-inbox is written primarily in TypeScript. GitHub's language field is based on the largest share of bytes in the default branch.
Read full README in the tab above.
Still deciding about agentic-inbox?
One click hands the question to an AI along with this page — see what it says about agentic-inbox.