Operations · The plumbing: automations, inboxes, browsers for agents. · a tool
The open-source project agentic-inbox, by cloudflare
“A self-hosted email client with an AI agent, running entirely on Cloudflare Workers” — the project's own words, on GitHub
Paste this into the AI that runs on your computer. It does the install, checks it works, and tells you what to type first. If anything fails, paste the error back to it.
Install agentic-inbox (https://github.com/cloudflare/agentic-inbox) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Claude Code, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Clone https://github.com/cloudflare/agentic-inbox into ~/tools/agentic-inbox and follow the README's install exactly. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Click Deploy to Cloudflare, which provisions R2, Durable Objects and Workers AI for you, then set the DOMAINS variable to the domain you want mail for. Before anyone else can reach it, configure Cloudflare Access under the Worker's Settings > Domains & Routes, and set the POLICY_AUD and TEAM_DOMAIN secrets it shows you, the app refuses to run in production without them. In the Cloudflare dashboard, add an Email Routing catch-all rule pointing at this Worker, and confirm the Worker has the send_email binding so it can send outbound mail too. Create a mailbox for one real address, send it a test email, and check it appears in the web inbox before you rely on it. If you see "Invalid or expired Access token", your POLICY_AUD or TEAM_DOMAIN secrets are stale, toggle Access off and on for the Worker to get fresh ones. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Create your first mailbox. If anything fails, show me the exact error and fix it before going on.
Install agentic-inbox (https://github.com/cloudflare/agentic-inbox) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Kimi, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Clone https://github.com/cloudflare/agentic-inbox into ~/tools/agentic-inbox and follow the README's install exactly. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Click Deploy to Cloudflare, which provisions R2, Durable Objects and Workers AI for you, then set the DOMAINS variable to the domain you want mail for. Before anyone else can reach it, configure Cloudflare Access under the Worker's Settings > Domains & Routes, and set the POLICY_AUD and TEAM_DOMAIN secrets it shows you, the app refuses to run in production without them. In the Cloudflare dashboard, add an Email Routing catch-all rule pointing at this Worker, and confirm the Worker has the send_email binding so it can send outbound mail too. Create a mailbox for one real address, send it a test email, and check it appears in the web inbox before you rely on it. If you see "Invalid or expired Access token", your POLICY_AUD or TEAM_DOMAIN secrets are stale, toggle Access off and on for the Worker to get fresh ones. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Create your first mailbox. If anything fails, show me the exact error and fix it before going on.
Install agentic-inbox (https://github.com/cloudflare/agentic-inbox) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Gemini CLI, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Clone https://github.com/cloudflare/agentic-inbox into ~/tools/agentic-inbox and follow the README's install exactly. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Click Deploy to Cloudflare, which provisions R2, Durable Objects and Workers AI for you, then set the DOMAINS variable to the domain you want mail for. Before anyone else can reach it, configure Cloudflare Access under the Worker's Settings > Domains & Routes, and set the POLICY_AUD and TEAM_DOMAIN secrets it shows you, the app refuses to run in production without them. In the Cloudflare dashboard, add an Email Routing catch-all rule pointing at this Worker, and confirm the Worker has the send_email binding so it can send outbound mail too. Create a mailbox for one real address, send it a test email, and check it appears in the web inbox before you rely on it. If you see "Invalid or expired Access token", your POLICY_AUD or TEAM_DOMAIN secrets are stale, toggle Access off and on for the Worker to get fresh ones. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Create your first mailbox. If anything fails, show me the exact error and fix it before going on.
Install agentic-inbox (https://github.com/cloudflare/agentic-inbox) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Codex, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Clone https://github.com/cloudflare/agentic-inbox into ~/tools/agentic-inbox and follow the README's install exactly. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Click Deploy to Cloudflare, which provisions R2, Durable Objects and Workers AI for you, then set the DOMAINS variable to the domain you want mail for. Before anyone else can reach it, configure Cloudflare Access under the Worker's Settings > Domains & Routes, and set the POLICY_AUD and TEAM_DOMAIN secrets it shows you, the app refuses to run in production without them. In the Cloudflare dashboard, add an Email Routing catch-all rule pointing at this Worker, and confirm the Worker has the send_email binding so it can send outbound mail too. Create a mailbox for one real address, send it a test email, and check it appears in the web inbox before you rely on it. If you see "Invalid or expired Access token", your POLICY_AUD or TEAM_DOMAIN secrets are stale, toggle Access off and on for the Worker to get fresh ones. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Create your first mailbox. If anything fails, show me the exact error and fix it before going on.
Deploy it, then create a mailbox for one real address on your domain and send yourself a test email to confirm it actually arrives in the web inbox.
Send that mailbox a real question and watch the built-in agent draft a reply in the side panel, read it fully before you'd ever let it go out.
Turn on Cloudflare Access and confirm the app refuses you until you sign in through it, that's what stops a stranger from reading your mail.
cloudflare/agentic-inbox on GitHub, under the Apache-2.0 licence. 7,333 stars, checked 9 September 2026. Last change 17 April 2026. We did not write it; we checked it, and wrote this page so you can use it.
If you're launching or growing a brand across Asia and the West, a call is where we work out whether it's a fit.