Shoot-email

What the company appears to be: Shoot-email is a developer tool that provides an AI agent with a persistent email inbox interface, enabling it to send and receive text messages through a structured MCP (Model Communication Protocol) interface. It was submitted as part of the OpenAI 2026 hackathon.

What changed: The project description indicates this was an extension built during a hackathon period, adding functionality to a pre-existing baseline codebase. It introduces email operations designed for probabilistic callers, with features like idempotent outbound sends and explicit trust labeling for inbound messages.

The single most important open question: Is there any evidence of real-world usage or integration beyond the demo environment? The description states that the project exists in a judge sandbox environment with no local rebuild required, but does not indicate whether it has been adopted by users or integrated into production systems.

• The description states that Shoot-email gives ChatGPT a real email inbox
• It allows AI agents to send and receive text messages through a structured MCP interface
• The system assigns an agent a stable mailbox identity
• It exposes ten MCP tools for:
  • Initializing the mailbox
  • Inspecting identity and service state
  • Sending text email
  • Retrieving pending messages
  • Reading individual messages
  • Acknowledging completed work
  • Inspecting processed history
  • Checking outbound delivery state
• The system uses Cloudflare Email Routing, Cloudflare Workers, Neon Postgres through Hyperdrive, and PostgreSQL for storage
• It implements idempotent inbound ingestion and outbound send behavior
• The project is described as a "persistent email inbox built for AI agents"

• The description states that current AI assistants can read connected email and help draft responses, but many workflows stop at the draft
• The product positions itself as exploring what email would look like if designed from the ground up for AI agents rather than around a human inbox interface
• It claims to make email a durable capability that an agent can operate safely, not merely a source of text it can summarize
• The project is described as being built for "LLM-first" operations with specific design principles:
  • Inbox retrieval returns bounded batches with complete message text
  • Retrieval never silently marks messages handled
  • Inbound email is explicitly labeled as untrusted external data
  • Outbound sends require caller-generated idempotency keys
• The description indicates this was a hackathon submission, suggesting it's in early development

• Not evidenced. The description does not specify target customers or ideal customer profiles.
• The project is described as being built for AI agents, but no specific user personas or segments are mentioned.

• Not evidenced. There is no information provided about pricing models, revenue streams, or business model details.
• The description indicates this was a hackathon submission with no mention of commercialization plans.

• Built with: Cloudflare, Codex, MCP, Node.js, PostgreSQL
• Uses Cloudflare Email Routing and Workers for real inbound messages
• Runs on Cloudflare Workers reaching Neon Postgres through Hyperdrive
• PostgreSQL stores users, external identities, sessions, messages, delivery state, abuse-control state, and future pgvector embeddings
• Real outbound delivery uses Cloudflare Email Sending
• Implements a CLI and MCP adapter with one Node.js service layer and versioned contract
• Has 49 automated unit and database-backed integration tests
• The system separates retrieval from acknowledgement
• Persists outbound requests before provider calls
• Returns unknown status for ambiguous provider outcomes
• Never accepts identity or mail headers as ordinary tool arguments
• Uses a restricted bearer principal for remote identity in demo environment

• Not evidenced. There is no evidence of revenue, customers, or adoption beyond the demo environment.
• The project exists in a judge sandbox environment with no local rebuild required
• The description indicates it was submitted to a hackathon and existed before the hackathon period
• No information about user growth, engagement metrics, or product usage data

• Not evidenced. There is no mention of competitors or competitive landscape.
• The description does not provide any information about existing solutions in this space.

• The project appears to be a hackathon submission with no evidence of commercial traction
• The demo environment uses synthetic addresses and simulated outbound delivery, suggesting limited real-world testing
• No evidence of production deployment or integration with actual email providers beyond Cloudflare
• The system relies on a temporary judge bearer transport for authentication, with OAuth 2.1 planned for later milestones
• No information about scalability, security, or performance in production environments
• The project is described as existing before the hackathon but only the extension was built during it

1. What is the timeline for moving from this demo environment to production deployment?
2. How does the system handle edge cases like email provider outages or rate limiting?
3. What are the specific security measures in place for handling untrusted external data?
4. Are there any plans for integrating with major email providers beyond Cloudflare?
5. What is the current status of OAuth 2.1 implementation for authentication?
6. How does the system handle message threading and conversation continuity?
7. What are the technical limitations or constraints that prevent wider adoption?
8. Is there any plan to monetize this tool or integrate it into commercial products?