Ctrl K
ComunidadGuías…
GITHUB · ANALIZADO

agentic-inbox

Agentic Inbox is a self-hosted email client powered by AI agents, running entirely on Cloudflare Workers. It features an inbox, search, and reply capabilities with optional Telegram integration.

Ficha actualizada 22 sept 2026, 19:51 · upstream 22 sept 2026, 19:39 · release sin release detectada

Ver códigoProblemas y ayudaRepositorio ↗
00

Qué es agentic-inbox

Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.

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 SQLite storage, and attachments are stored in R2. An AI-powered agent can read your inbox, search conversations, and draft replies using the Cloudflare Agents SDK and Workers AI. The app supports full email client features including threading, folders, attachment handling, and a Telegram bot for triaging incoming messages.

CASOS DE USO
  • Personal email management with AI-assisted drafting
  • Team collaboration with shared inbox and thread tracking
  • Automated reply generation from inbound emails
  • Secure communication with per-mailbox isolation
  • Archival of conversations for reference or compliance
PUNTOS DESTACADOS
  • Runs entirely on Cloudflare Workers without a serverless runtime, reducing infrastructure costs
  • Uses Resend API as outbound fallback instead of native Cloudflare email binding (which requires paid plans)
  • Catchall mailbox configuration allows all emails for a domain to be routed to one inbox address
  • Telegram bot integration with inline triage buttons and threaded reply support
  • Per-mailbox isolation using Durable Objects with SQLite, enabling independent scaling per mailbox
PRECAUCIONES
  • AI agent replies always send from the catchall mailbox address rather than the original recipient's address
  • Outbound email requires either a paid Cloudflare plan or a Resend API key configured as fallback
  • Telegram webhook endpoint is not left open by default and must be protected with Access policies in production
  • No native support for sending to arbitrary external addresses without using the Email Service binding
01

Perfil de infraestructura

Estimación inicial derivada del repositorio y de los servicios detectados.

CPU1 vCPUrecomendación inicial
MEMORIA1 GBRAM estimada
DISCO10 GBalmacenamiento base
COMPLEJIDADlownivel de operación
02

Despliegue detectado

Qué señales reales de instalación hemos encontrado.

Despliegue manual

Deploy via pnpm run deploy. Configure wrangler.jsonc with DOMAINS, CATCHALL_MAILBOX, RESEND_API_KEY (optional), and POLICY_AUD/TEAM_DOMAIN secrets from Cloudflare Access. Create an R2 bucket for attachments. Enable Cloudflare Access one-click on the Worker to protect the webhook endpoint. For production, enable Email Routing in your domain settings and configure a catch-all rule forwarding all @yourdomain.com emails to the inbox mailbox.

—Dockerfile
—Compose
—One-click
03

Stack y dependencias

Componentes inferidos a partir de manifests, configuración y documentación.

FRAMEWORKS
ReactNode.js
SERVICIOS
No detectados
BASES DE DATOS
No detectadas
PUERTOS
No detectados
05

Puede sustituir a

Relaciones detectadas por el análisis del repositorio y su categoría.

06

Experiencia real de la comunidad

Ayuda a contrastar la estimación automática con instalaciones reales.

Todavía no hay datos comunitarios para este proyecto.