Shortwave vs Zero

Multi account

1. switcherConnect several accounts across providers — Gmail, Microsoft 365, IMAP — and work them from one place

   weight 3 · round to Zero
   Shortwave—none0/10

   No evidence Shortwave supports connecting multiple providers (Gmail, Microsoft 365, IMAP) from one inbox; in fact the founder explicitly states they integrate only with Gmail's APIs ('not IMAP'), and a user confirms 'it only works with Google servers.' This directly contradicts the multi-provider switcher story rather than merely lacking support for it.

   • [community] “Founder: We integrate with Gmail's APIs (not IMAP) to enable faster real-time updates, better latency compensation, offline handling, bundle…”
   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”

   proof ↗⚑ flag

   Zero!disputedcontradicted4/10

   Zero's marketing repeatedly claims a 'Unified Inbox' connecting Gmail, Outlook, 'and more,' but the only hands-on/community description of the actual product (zero-comm-1) says it 'works on top of Gmail' and is in public beta, suggesting multi-provider (Microsoft 365, IMAP) support isn't yet realized in practice — no IMAP mention anywhere in the pack. Missing for 10: explicit IMAP support, confirmed working Microsoft 365/Outlook connection, and independent verification that multiple accounts can be worked from one place simultaneously.

   • [github] “Unified Inbox – Connect multiple email providers like Gmail, Outlook, and more.”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag

Portability

1. switcherMy mail stays reachable over open protocols and standard formats — IMAP/JMAP/SMTP access and standards-based export — so no client can lock me in

   weight 2 · round drawn
   Shortwave—none0/10

   Shortwave's own founder states they integrate via Gmail's proprietary APIs 'not IMAP,' and there is no mention anywhere in docs of JMAP, SMTP-level access, or standards-based export tooling — the product only works atop Google's servers (also confirmed by a security-focused user noting 'it only works with Google servers'). No evidence of any open-protocol mail access or portable export path exists in the pack.

   • [community] “Founder: We integrate with Gmail's APIs (not IMAP) to enable faster real-time updates, better latency compensation, offline handling, bundle…”
   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows Zero connects to providers like Gmail/Outlook and offers self-hosting and an MCP server for AI actions, but nothing in the pack mentions IMAP/JMAP/SMTP protocol access or standards-based mail export for portability — the core of this switcher story is unaddressed.

   • [github] “Unified Inbox – Connect multiple email providers like Gmail, Outlook, and more.”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [claimed-docs] “Self-hosting capabilities”

   proof ↗⚑ flag

2. switcherSelf-host the email app and keep the mail pipeline under my own control

   weight 1 · round to Zero
   Shortwave—none0/10

   Shortwave is a cloud-hosted email client that syncs data to its own servers and works only with Gmail/Google servers (per community reports), with no documentation of any self-hosting option, on-prem deployment, or open-source pipeline; probes for docs/API specs also return 404s, indicating no infrastructure exposed for self-hosting.

   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
   • [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero✓fullprobed7/10

   Zero is explicitly open-source and self-hostable, with GitHub docs stating 'Self-Hosting Freedom – Run your own email app with ease' and a probe confirming a real, keyless-cloneable source tree with docker-compose files for self-hosting the full mail pipeline (DB, prod services). This gives a switcher genuine control over their own instance rather than relying on a hosted SaaS. Missing for 10: detailed self-hosting setup/migration docs (e.g. IMAP/SMTP backend specifics), independent hands-on reports of a completed self-hosted deployment, and confirmation of full mailbox portability beyond Gmail/Outlook OAuth integration.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [claimed-docs] “Self-hosting capabilities”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Zero
   Shortwave—none0/10

   Direct probes show no llms.txt or agent-oriented docs endpoint exists (404s across llms.txt, docs-md, openapi paths), and no other evidence mentions such agent-facing documentation.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   The repo ships an AGENT.md (agent-configuration doc) and a detailed MCP.md describing the MCP server's tool surface, both of which are exactly the kind of machine/agent-oriented documentation an AI agent could be pointed at; this was confirmed by a hands-on probe of the actual repo tree. However there is no evidence of a dedicated llms.txt file or any explicit guidance framing these docs as an 'agent-readable spec' in the llms.txt convention. Missing for 10: an actual llms.txt file, first-party statement that docs are structured for LLM consumption, and independent confirmation an agent successfully parsed these docs.

   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Shortwave—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Shortwave
   Shortwave✓fullcommunity8/10

   Shortwave explicitly documents connecting to any MCP server via 'Add custom integration' to let its AI Assistant use those tools, with first-party blog docs and pricing page confirming MCP support alongside built-in integrations. Missing for 10: independent hands-on verification of the MCP setup flow and no detail on tool-call reliability/limits beyond marketing docs.

   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [claimed-docs] “Just click "Add custom integration" and point to an MCP server of your choice — or even create your own.”
   • [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
   • [claimed-docs] “Connect the AI with your favorite apps and services for enhanced productivity workflows through built-in integrations or MCP”
   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [community] “Security vendor blog highlighted that Shortwave's AI Email with MCP integration 'opens up rich capabilities—but also new attack surfaces,' f…”

   proof ↗⚑ flag

   Zero—none0/10

   All evidence describes Zero exposing its own email/label/compose tools via an official 'ZeroMCP' server for other AI agents to consume — i.e., Zero acting as an MCP server/provider, not as a client that plugs in external MCP servers to use their tools. There is no documentation of Zero itself connecting to third-party MCP servers to extend its own toolset.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Zero
   Shortwave—none0/10

   Shortwave documents letting its own AI Assistant connect out to third-party MCP servers ('Add custom integration', point to an MCP server of your choice) — this is MCP-client behavior, not Shortwave exposing an official MCP server that external agents could connect to. As a SaaS email product, offering an official MCP server for outside agents is a fair, applicable axis, but no evidence pack item shows such a server (docs/openapi/llms.txt probes all 404).

   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [claimed-docs] “Just click "Add custom integration" and point to an MCP server of your choice — or even create your own.”
   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero ships a documented, named 'Zero MCP' server (MCP.md) exposing concrete tools (email CRUD, labels, AI compose, mailbox Q&A, web search) with an authentication method (Better Auth session token, OAuth coming soon), confirmed by an independent runtime probe finding the file in the actual repo. Missing for 10: independent hands-on verification that a third-party agent successfully connects and uses the server end-to-end, and OAuth is still unimplemented.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Zero
   Shortwave—none0/10

   Shortwave's evidence only shows it acting as an MCP *client* (connecting its AI Assistant to other apps' MCP servers) or integrating with third-party APIs like Zapier/GitHub — none of this constitutes Shortwave itself exposing a documented public API for external developers to drive the product. Direct probes for llms.txt, docs-as-markdown, and OpenAPI/Swagger specs all returned 404s, confirming no discoverable public API surface.

   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [claimed-docs] “Just click "Add custom integration" and point to an MCP server of your choice — or even create your own.”
   • [claimed-docs] “Connect the AI with your favorite apps and services for enhanced productivity workflows through built-in integrations or MCP”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero ships a documented MCP server (ZeroMCP) exposing a public, structured API for emails, labels, AI compose, mailbox Q&A, and web search, with authentication documented via Better Auth session tokens (OAuth coming soon), corroborated by a runtime probe confirming the real MCP.md and AGENT.md files in the repo. missing for 10: independent third-party usage/testing of the MCP API beyond first-party docs and a single runtime probe, and full OAuth support (currently listed as coming soon).

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Shortwave—none0/10

   Shortwave's evidence covers MCP/app integrations and AI assistant features, but there is no mention of scoped or least-privilege API credential issuance, API key management, or granular permission controls for agents; probes confirm no public API/OpenAPI spec exists. Community comments even note complaints about over-broad permission requests rather than scoped credentials, reinforcing absence of this capability.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
   • [community] “User complaint: 'all these apps either want gmail way too many gmail permissions, and/or are hosted... I'm trying to get rid of gmail lol.'”

   proof ↗⚑ flag

   Zero—none0/10

   Zero's MCP server documents authentication via a Better Auth session token (or future OAuth), but there is no evidence of scoped or least-privilege credential issuance, permission granularity, or agent-specific token scoping — auth appears to be a single session-level token granting full account access. Missing for 10: any documentation of scopes/permissions models, per-agent credential minting, or restricted-access tokens for agents.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Zero
   Shortwave—none0/10

   No evidence of any official SDKs for developers; probes for llms.txt, docs.md, and OpenAPI/swagger specs all returned 404, and the evidence pack only documents MCP-based integrations for end-user workflows (Slack, Notion, Zapier) rather than a developer SDK.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero~partialprobed5/10

   Zero doesn't publish a traditional language SDK, but it does document an official 'ZeroMCP' server (MCP.md) with concrete tool endpoints (email CRUD, labels, AI compose, mailbox Q&A) plus AGENT.md agent-configuration docs, giving AI-native developers a documented, official programmatic interface to build against, corroborated by a runtime probe confirming these files exist in the live repo. Missing for 10: an actual client SDK/library (Python/JS package), auth beyond a session token (OAuth marked 'coming soon'), and independent third-party developer usage reports.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [github] “🚀 Developer-Friendly – Built with extensibility and integrations in mind.”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Shortwave—none0/10

   Shortwave's evidence covers triggers, MCP integrations, and Zapier connections, but nothing describes outbound webhooks that let an AI-native user subscribe to Shortwave events; no webhook API, subscription endpoint, or event schema is documented, and OpenAPI/llms.txt probes returned 404s.

   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence covers Zero's MCP server (tool-calling actions like search, compose, label management) but nowhere mentions webhooks, event subscriptions, or push notifications for external systems to react to inbox events.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Shortwave
   Shortwave✓fullclaimed8/10

   Shortwave delivers AI-generated insights directly in-product: Instant Summaries appear atop threads, AI Assistant reads threads/searches history/checks calendar to surface answers, Ghostwriter offers inline autocomplete suggestions, and custom AI filters/triggers auto-label and organize emails based on AI analysis. These are well-documented first-party features spanning summarization, suggestion, and automated insight generation across the inbox. Missing for 10: independent hands-on validation of insight quality/accuracy and no third-party review confirming these AI insights work reliably in practice beyond vendor claims.

   • [claimed-docs] “Instant Summaries show up at the very top of your email threads the instant you open them.”
   • [claimed-docs] “Instant Summaries show up at the very top of your email threads the **instant** you open them.”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete.”
   • [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”

   proof ↗⚑ flag

   Zero✓fullprobed7/10

   Zero documents AI features that generate insights from mailbox data: composing emails with AI assistance, answering questions about mailbox content and specific threads, and summarizing/chatting with inbox content, corroborated by founder description of AI-powered summarization and chat-with-inbox in community coverage. missing for 10: independent hands-on verification of insight quality/accuracy and no broader third-party review confirming these AI features work reliably in practice.

   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Shortwave
   Shortwave✓fullclaimed7/10

   Shortwave explicitly supports triggers that draft replies, add comments, organize threads into todos when emails arrive, plus custom AI filters running as background scripts and Tasklet integration to auto-act on emails—these run autonomously without user initiation. However, evidence is all vendor-sourced with no independent verification of reliability or scope of autonomy. Missing for 10: independent/hands-on confirmation of trigger reliability, detail on trigger configuration UI, and evidence of complex multi-step autonomous workflows beyond simple triggers.

   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”
   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [claimed-docs] “connects our AI Assistant to all your business applications, letting you accomplish complex workflows without ever leaving your inbox”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows an MCP server exposing on-demand email tools (search, compose, label, delete) that an AI client can call interactively, but nothing shows Zero itself scheduling or running autonomous background automations/triggers/workflows without a user or agent actively invoking them.

   ⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Shortwave✓fullclaimed8/10

   Shortwave has a built-in AI assistant/executive assistant that can read threads, write drafts, search email history, check calendar, run custom AI filters, and take multi-step actions via triggers and MCP integrations without leaving the inbox — clearly delegatable task execution. Missing for 10: independent hands-on validation of end-to-end delegated task completion (beyond vendor blog claims) and details on reliability/error handling.

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
   • [claimed-docs] “connects our AI Assistant to all your business applications, letting you accomplish complex workflows without ever leaving your inbox”
   • [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
   • [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero ships a built-in AI assistant that can compose emails, answer questions about threads/mailbox, and perform web search (Perplexity), confirmed both in docs (MCP.md) and independent community description of it as an 'AI-powered email client' that summarizes, drafts, and lets users chat with their inbox. Missing for 10: broader independent hands-on verification beyond a single HN comment, and clearer distinction between MCP-exposed tools vs. in-app assistant UX.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Shortwave
   Shortwave✓fullclaimed8/10

   Shortwave's AI Assistant lets users operate the inbox via natural language—reading threads, writing drafts, searching email history, checking calendar, and running custom AI filters written in plain English—directly in the product's core value proposition. Docs consistently describe this as the primary UX (chat-based assistant, plain-English filter scripts, natural-language triggers). missing for 10: independent/hands-on verification specifically of the natural-language command interface's reliability (community evidence focuses on UI/pricing/privacy, not NL command execution quality).

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “connects our AI Assistant to all your business applications, letting you accomplish complex workflows without ever leaving your inbox”
   • [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”

   proof ↗⚑ flag

   Zero✓fullcommunity7/10

   Zero's founder describes it as an AI-powered email client where users can chat with their inbox, ask questions about threads, and have AI draft replies, and the MCP docs confirm natural-language driven actions (compose, search, ask questions, web search) — this directly matches AI-native NL command operation. Missing for 10: independent hands-on verification of the actual chat UI/NL command interface beyond founder claims and MCP protocol docs.

   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [claimed-docs] “Compose emails with AI assistance”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Shortwave—none0/10

   Shortwave is an email client, not a developer platform with an API reference; probes for llms.txt, docs.md, and OpenAPI specs all returned 404s, and no evidence mentions any interactive API documentation or runnable code examples.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is an email client with an MCP server and docs (MCP.md, ROADMAP.md), but there is no evidence of an interactive API reference (e.g., Swagger/OpenAPI explorer, Postman collection, or runnable code sandbox) for AI-native users to explore and execute example calls.

   ⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Shortwave—none0/10

   Direct probes for OpenAPI/swagger specs and llms.txt all returned 404s, and no docs mention a machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”

   proof ↗⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Shortwave—none0/10

   No evidence of any public API, versioning scheme, or deprecation policy; probes for OpenAPI/llms.txt/docs endpoints all returned 404s, and no docs mention versioned APIs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence describes Zero's MCP server capabilities and self-hosting, but no documentation anywhere mentions API versioning, version numbers, or a deprecation policy for its MCP/API surface. missing for 10: any mention of API versioning scheme, changelog/deprecation policy, or backward-compatibility guarantees.

   ⚑ flag

Agent workflows

1. ai-native userAn external agent — Claude, ChatGPT, or my own — can read, triage, draft, and send my email end to end through a documented connection

   weight 2 · round to Zero
   Shortwave—none0/10

   Shortwave documents an internal AI Assistant that reads/drafts/searches email, and it can act as an MCP *client* connecting its own AI to external apps (Slack, GitHub, Zapier, etc.), but there is no evidence Shortwave exposes itself as an MCP server or documented API that lets an external agent (Claude, ChatGPT, or a custom agent) read/triage/draft/send mail through it. Probes confirm no llms.txt, no docs.md, and no OpenAPI/Swagger endpoint, indicating no documented external-agent connection surface.

   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
   • [claimed-docs] “Connect the AI with your favorite apps and services for enhanced productivity workflows through built-in integrations or MCP”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero documents an official MCP server (MCP.md, verified by probe) enabling agents like Claude to read threads, ask questions about mailbox content, compose with AI assistance, and create/send drafts and new emails, plus manage labels — covering triage, drafting, and sending end to end via Better Auth session token auth. missing for 10: no hands-on third-party report of an external agent (Claude/ChatGPT) actually completing a full read-triage-send workflow, and OAuth support is still 'coming soon' rather than shipped.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

Ai assistant

1. ai-native userAsk an assistant questions across my whole inbox and calendar — who said what, what's outstanding — and get grounded answers

   weight 2 · round to Shortwave
   Shortwave✓fullcommunity8/10

   Docs directly describe the AI Assistant reading threads, writing drafts, searching entire email history, and checking calendar — matching the grounded cross-inbox/calendar Q&A story. Community evidence corroborates fast search/summaries and real usage, though no independent hands-on confirmation of complex multi-thread grounded reasoning exists. Missing for 10: independent hands-on verification of accuracy/groundedness across large inboxes, and detail on how calendar+email context are combined in answers.

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “Instant Summaries show up at the very top of your email threads the instant you open them.”
   • [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   Zero's MCP server explicitly supports asking questions about mailbox content and specific email threads, plus AI compose, search, and labels, and community commentary confirms an AI-powered 'chat with your inbox' experience. However, evidence doesn't show cross-inbox/whole-calendar synthesis, calendar integration, or 'who said what / what's outstanding' style grounded multi-thread reasoning — the documented Q&A appears scoped to mailbox/thread level rather than full inbox+calendar grounding. missing for 10: calendar integration/awareness, evidence of synthesizing across the entire inbox (not just single threads), independent hands-on verification of grounded multi-source answers.

   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

Ai drafting

1. ai-native userAI drafts replies in my own voice and tone — ready to review and send, not generic boilerplate

   weight 3 · round to Shortwave
   Shortwave~partialclaimed6/10

   Shortwave's AI Assistant explicitly 'writes drafts' and Ghostwriter autocompletes replies as you type, confirming AI-drafted replies are a core capability. However, no evidence specifically shows the AI learns or mimics the user's personal voice/tone (vs. generic suggestions or template-based AI Snippets), so the 'own voice' personalization claim is unverified. Missing for 10: explicit documentation of voice/tone personalization or learning from user's writing style, and independent user reports confirming drafts sound authentically like them rather than generic AI text.

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete.”
   • [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete”
   • [claimed-docs] “AI Snippets let you define an email template once upfront and then re-use it whenever you need it.”

   proof ↗⚑ flag

   Zero~partialcommunity5/10

   Zero's MCP docs and founder description confirm AI drafts replies ('Compose emails with AI assistance', 'drafts replies') as a core feature, but no evidence describes voice/tone personalization or learning the user's writing style. Missing for 10: documentation of voice/tone matching or personalization mechanism, and independent hands-on verification that drafts read as the user's own voice rather than generic AI text.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag

Ai triage

1. ai-native userAI triages my inbox for me — auto-labeling, categorizing, and surfacing what needs attention — with behavior I can steer and audit

   weight 3 · round to Shortwave
   Shortwave✓fullcommunity7/10

   Shortwave ships custom AI filters that auto-label, star, and archive using plain-English scripts, plus Bundles/Splits to categorize inbox by importance and one-click identification of important emails/todos, directly matching the triage story; community feedback corroborates the bundling/importance-sorting feature as effective ('top shelf'). Steerability is evidenced via the plain-English filter scripts, but missing for 10: explicit audit-trail/log of AI triage decisions and independent verification of filter reliability at scale.

   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”
   • [claimed-docs] “They’re a simple way to divide your one big inbox into multiple smaller, more focused inboxes – each in its own tab.”
   • [claimed-docs] “Splits let you handle different types of emails at different times, so you can stay responsive where it matters most.”
   • [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   Community and docs evidence show Zero markets itself as an AI-powered inbox that auto-categorizes emails, and its MCP server exposes tools to modify/create labels, filter/search by label, and answer questions about threads/mailbox content, giving a steerable interface for AI actions. However, there's no explicit documentation of automatic prioritization/surfacing of 'what needs attention' or an audit log of AI triage decisions beyond the generic MCP action list. Missing for 10: dedicated 'needs attention' surfacing/prioritization feature, explicit audit trail or history of AI-taken triage actions, and independent hands-on verification of auto-labeling accuracy.

   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Create new custom labels with custom colors”
   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Shortwave
   Shortwave~partialclaimed6/10

   Shortwave's custom AI filters ('automatically label, star, archive, and more with scripts you write in plain English') and one-click sweep of non-important emails/todos (docs-15, docs-29) directly support automated actions applied across many inbox items at once, and triggers (docs-1) extend this to organizing threads into todos in bulk. However, there's no explicit documentation of a true multi-select bulk-action UI, batch limits, or independent hands-on confirmation that these AI filters reliably scale across large volumes of email. Missing for 10: explicit bulk-select/apply workflow docs, scale/performance evidence, and independent user corroboration of bulk automation working as advertised.

   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”
   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”

   proof ↗⚑ flag

   Zero~partialprobed5/10

   Zero's MCP server exposes email actions like 'Bulk delete emails' and 'Bulk archive emails' explicitly labeled as bulk operations, plus label/search operations that could apply across many items. However, evidence does not specify limits, batch size, or confirm bulk semantics beyond these two named actions, nor is there hands-on confirmation of bulk behavior at scale. missing for 10: independent/hands-on verification of bulk operations at scale, documentation of batch limits or performance, evidence of bulk operations beyond delete/archive (e.g., bulk label/move/send).

   • [claimed-docs] “Bulk delete emails - Bulk archive emails”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Shortwave
   Shortwave✓fullclaimed7/10

   Shortwave documents explicit rule/trigger automation: triggers that draft replies when emails arrive, custom AI filters written in plain English that auto-label/star/archive, and Tasklet integration that takes automatic actions on emails as they arrive. This directly matches defining rules that fire on events (email arrival) with automated actions. Missing for 10: independent/hands-on verification that these triggers work reliably in practice, and more detail on rule complexity/limits beyond marketing copy.

   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows Zero as an AI email client with MCP tool actions (search, compose, label, etc.) but no documented rule-based automation engine that triggers actions on events (e.g., 'when email arrives from X, do Y'). All actions appear to be user- or agent-invoked rather than event-triggered automation. Missing for full credit: any documented trigger/condition/action rules engine or scheduled/event-based automation feature.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Shortwave
   Shortwave~partialclaimed4/10

   Shortwave offers event-based 'triggers' (auto-draft replies, add comments, organize todos) and custom AI filters that run automatically in plain English, which are a form of automation, but these are reactive triggers on incoming events rather than true time-based recurring/scheduled jobs — the only scheduling feature documented (Scheduled Send) is a one-time future send, not a recurring workflow. Missing for 10: explicit recurring/cron-style scheduling of AI workflows, documentation of periodic digest or repeat-interval automations, and independent confirmation that triggers can run on a time-based recurring cadence rather than only on email arrival.

   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Scheduled send gives you the ability to send an email at a future time.”
   • [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is an AI email client with MCP tools for email actions (labels, search, compose, AI Q&A) but no evidence of scheduling recurring jobs or workflows/automation triggers.

   ⚑ flag

Calendar

1. power-userSee my calendar, respond to invites, and create events without leaving the email client

   weight 2 · round to Shortwave
   Shortwave~partialclaimed3/10

   Shortwave's AI assistant is documented to 'check your calendar' and integrate with Calendar as one of many connected apps, implying some calendar visibility inside the client, but there is no evidence of responding to invites or creating events without leaving the email client. missing for 10: explicit calendar view/UI, invite RSVP handling, and event-creation workflow evidence.

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “Connect the AI to your Slack, Calendar, Notion, Asana, Hubspot, and more so you can automate workflows without ever leaving your inbox.”

   proof ↗⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

2. power-userShare my availability or insert bookable meeting times directly into an email

   weight 1 · round drawn
   Shortwave—none0/10

   Evidence shows Shortwave's AI can 'check your calendar' and connect to Calendar via integrations, but there is no mention of sharing availability or inserting bookable meeting time slots into an email — a distinct calendar-scheduling feature not evidenced anywhere in the pack.

   ⚑ flag

   Zero—none0/10

   Zero is an email client with AI/MCP features for composing, searching, and managing emails, but no evidence in the pack mentions calendar integration, availability sharing, or inserting bookable meeting times into emails.

   ⚑ flag

Sending

1. power-userSee whether and when recipients opened my email

   weight 1 · round drawn
   Shortwave—none0/10

   No evidence in the pack mentions read receipts, open tracking, or notifications about recipient email opens; Shortwave's documented features cover AI drafting, snippets, scheduling, undo send, and integrations but nothing about tracking whether/when recipients opened a message.

   ⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions read receipts, open tracking, or notifications about when recipients open emails; the MCP/docs only cover sending, drafting, labeling, and searching emails.

   ⚑ flag

2. power-userSchedule an email to send later and undo a send within a grace window

   weight 2 · round to Shortwave
   Shortwave✓fullclaimed8/10

   Shortwave's docs explicitly describe both scheduled send (set a time, write message, move on) and undo send (revert a sent message back to a draft), directly matching the story. Missing for 10: explicit detail on the undo grace-window duration and independent/hands-on corroboration beyond vendor blog.

   • [claimed-docs] “Scheduled send gives you the ability to send an email at a future time.”
   • [claimed-docs] “Undo send staves off the panic you feel when you accidentally send a message that wasn't ready by allowing you to revert a sent message back…”
   • [claimed-docs] “Scheduled send gives you the ability to send an email at a future time. All you have to do is write a message, set a send time, and then mov…”

   proof ↗⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions scheduled send or undo-send functionality; MCP docs list send/draft/delete but nothing about delayed sending or a grace-window recall.

   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts”

   proof ↗⚑ flag

Templates

1. power-userInsert saved snippets or templates — with variables and attachments — instead of retyping the same reply

   weight 2 · round to Shortwave
   Shortwave~partialclaimed5/10

   Shortwave documents 'AI Snippets' that let users define an email template once and reuse it, available for individual and team use — directly matching the core snippet/template story. However, the evidence never confirms support for variables (dynamic fields) within snippets or attaching files as part of a snippet, both explicitly requested in the story. Missing for 10: documentation of variable/placeholder support in snippets, documentation of attachment bundling with snippets, and independent/hands-on confirmation of the feature working as described.

   • [claimed-docs] “AI Snippets let you define an email template once upfront and then re-use it whenever you need it.”
   • [claimed-docs] “AI Snippets are available both for individual use and for use across your team.”

   proof ↗⚑ flag

   Zero—none0/10

   No evidence pack item mentions saved snippets, canned responses, or templates with variables/attachments; the docs describe AI-assisted composing, MCP tools, labels, and self-hosting but nothing about a snippet/template insertion feature.

   ⚑ flag

Offline

1. power-userRead, search, and write email offline, with changes syncing when I reconnect

   weight 2 · round to Shortwave
   Shortwave~partialcommunity3/10

   The founder states Gmail API integration enables 'offline handling' alongside real-time sync, implying some offline capability, but there's no detail on offline search, offline composing, or how changes reconcile on reconnect. missing for 10: documentation of offline read/search functionality, offline draft writing, and sync-conflict resolution behavior.

   • [community] “Founder: We integrate with Gmail's APIs (not IMAP) to enable faster real-time updates, better latency compensation, offline handling, bundle…”

   proof ↗⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions offline mode, local caching, or sync-on-reconnect; Zero appears to be a web-based email client requiring live connection to providers/AI services, with no offline-capability documentation.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Zero
   Shortwave—none0/10

   No evidence of a public API for Shortwave; probes for llms.txt, docs-md, and OpenAPI specs all returned 404, and no documentation mentions programmatic access to core features like AI assistant, triggers, or inbox management outside the UI/MCP integration (which is inbound, not an outbound API for replicating UI actions).

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   Zero's MCP server exposes many core email actions (search, send, draft, delete, labels, AI compose, thread Q&A) that mirror UI functionality, giving strong API-parity for mail operations. However missing for 10: no evidence of API parity for UI-specific settings like customizable keyboard shortcuts, UI theming/customization, unified inbox provider management, or account/connection setup via API — these remain UI-only per docs, and there's no independent confirmation the MCP surface is fully comprehensive versus a curated subset.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Get all user labels - Create new custom labels with custom colors - Delete existing labels”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [claimed-docs] “Customizable keyboard shortcuts”
   • [github] “Customizable UI & Features – Tailor your email experience the way you want it.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Shortwave—none0/10

   No evidence of any data export feature (mailbox, comments, snippets, etc.) in open formats; probes for llms.txt, docs-md, and openapi endpoints all returned 404, and no changelog/blog mentions an export or account-portability capability. Community threads mention deleting the account making it 'low-risk' to switch back to Gmail, but that is because Shortwave uses Gmail as the underlying store, not because Shortwave itself offers a data export mechanism. missing for 10: any documented export/download feature, supported open file formats, or migration/backup tooling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
   • [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows Zero is self-hostable, open-source, and doesn't sell user data, plus a Drizzle Studio DB viewer for self-hosters, but there is no documented data-export feature (e.g., mbox/EML export, takeout tool) letting a user extract all their mail data in an open format and leave the service.

   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [claimed-docs] “View and edit data with Drizzle Studio pnpm db:studio”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Zero
   Shortwave—none0/10

   No evidence of any open-source license or public source repository for Shortwave; it is a closed commercial SaaS email client with no mention of open licensing anywhere in the evidence pack.

   ⚑ flag

   Zero✓fullprobed8/10

   Zero's source is publicly hosted on GitHub (Mail-0/Zero) with a full contributing guide, self-hosting instructions, and a verified runtime probe confirming a real, clonable source tree with Docker configs for self-hosting — consistent with an open-source project freely readable by AI-native users. Missing for 10: explicit citation of the license file/name (e.g. MIT/AGPL) to confirm licensing terms.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [claimed-docs] “View and edit data with Drizzle Studio pnpm db:studio”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Zero
   Shortwave—none0/10

   Shortwave is a hosted SaaS email client with no evidence of any self-hostable version; it relies on Google servers and its own cloud infrastructure (comm-11), and no self-hosting docs, Docker images, or open-source releases exist in the evidence pack.

   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Multiple GitHub and docs citations explicitly advertise 'Self-Hosting Freedom' and describe running your own email app, and a runtime probe confirms a real self-hostable source tree with docker-compose files for self-hosting deployment. Missing for 10: independent hands-on report of a completed self-host deployment beyond the repo/docker-compose evidence, and more detailed self-host setup documentation.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “⚙️ **Self-Hosting Freedom** – Run your own email app with ease.”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [claimed-docs] “Self-hosting capabilities”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Zero
   Shortwave—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or storage location controls; Shortwave is shown to run on Google servers with no configurable region options, and community comments only raise general privacy/security concerns without any residency feature being offered.

   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”

   proof ↗⚑ flag

   Zero~partialclaimed5/10

   Zero's self-hosting capability (own infra, own database via docker-compose) lets a user effectively choose where their data lives, and it claims not to track/collect/sell data, but there is no explicit region/residency selection feature or documented multi-region hosted offering. missing for 10: explicit region/residency selection UI or hosted multi-region options, documentation on data locality guarantees for the hosted SaaS version, independent confirmation of self-host deployment satisfying residency requirements.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “⚙️ **Self-Hosting Freedom** – Run your own email app with ease.”
   • [claimed-docs] “Self-hosting capabilities”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [github] “Zero does not track, collect, or sell your data in any way.”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to Zero
   Shortwave—none0/10

   No evidence pack item describes any setting, policy statement, or opt-out mechanism letting users prevent their email/AI data from being used for model training; the only related community evidence (shortwave-comm-7) actually flags that Shortwave's privacy policy permits sharing email content/metadata with third-party vendors, which a user rejected outright rather than confirming a training opt-out exists.

   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”
   • [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”

   proof ↗⚑ flag

   Zero~partialclaimed5/10

   Zero states it does not track, collect, or sell user data, and self-hosting is available which would let users fully control data flow, implying no AI training on user data. However, there is no explicit statement or policy about AI-model training exclusion (e.g., no clause addressing whether email content sent to AI features like compose/summarize is used for model training). missing for 10: explicit AI-training opt-out/data-use policy, third-party AI provider data-handling terms, independent verification of the no-training claim.

   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Zero
   Shortwave~partialcommunity3/10

   The only evidence touching on data deletion is a community anecdote that deleting one's Shortwave account makes it low-risk to switch back to Gmail, implying account-level deletion works, but there is no documented retention policy, granular deletion controls, or data-lifecycle settings; community comments even flag privacy concerns about email content being synced/shared with third-party vendors with no denylist option. missing for 10: documented retention policy, explicit deletion/export controls, first-party privacy/data-handling documentation.

   • [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”
   • [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”

   proof ↗⚑ flag

   Zero~partialclaimed5/10

   Zero claims a no-tracking/no-sell data policy and supports self-hosting (giving users full control over their own data and deletion since they own the infrastructure), plus MCP tools include explicit 'delete emails' actions. However, there's no documented data retention policy, no explicit account/data deletion workflow or export tooling described, and no independent verification of the no-tracking claim. missing for 10: documented retention/export/deletion policy for hosted use, independent audit of data practices, explicit account-deletion or right-to-be-forgotten flow.

   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Bulk delete emails - Bulk archive emails”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round to Zero
   Shortwave—none0/10

   No evidence Shortwave offers any telemetry/usage-tracking opt-out control; documentation focuses on AI features and integrations, and community discussion instead raises concerns about email content being shared with third-party vendors with no denylist option, but nothing addresses telemetry/analytics opt-out specifically.

   • [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”

   proof ↗⚑ flag

   Zero~partialprobed5/10

   Zero's GitHub page states it 'does not track, collect, or sell your data in any way,' and self-hosting support (Docker compose files, self-hosting docs) lets AI-native users run their own instance with no vendor telemetry at all. However there is no explicit telemetry settings/opt-out toggle documented, no privacy policy detail, and no independent verification of the no-tracking claim. Missing for 10: explicit telemetry opt-out control/setting, detailed privacy policy, and independent/hands-on confirmation of the no-tracking claim.

   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

Protection

1. switcherUse aliases or masked addresses so sign-ups and strangers never learn my real address

   weight 1 · round drawn
   Shortwave—none0/10

   No evidence Shortwave offers email aliasing, masked addresses, or similar identity-protection features for sign-ups; the pack only covers AI assistant, integrations, and inbox management features unrelated to address masking.

   ⚑ flag

   Zero—none0/10

   Zero is an AI-powered unified email client with labels, search, and MCP integrations, but nothing in the evidence pack describes email alias generation or masked/burner address creation to hide a user's real address from sign-ups or strangers.

   ⚑ flag

2. switcherThe client protects me from senders' tracking — blocking read pixels by default — and is transparent about what it does with my mail data

   weight 2 · round to Zero
   Shortwave—none0/10

   No evidence anywhere in the pack describes Shortwave blocking sender tracking pixels, nor does it detail transparent data-handling practices for mail content; the only related community evidence (comm-6, comm-7) actually raises unaddressed privacy concerns about syncing sensitive mail and sharing content/metadata with third-party vendors. missing for 10: any mention of read-pixel/tracking-pixel blocking, any transparency documentation on mail data handling, and evidence rebutting the third-party data-sharing concerns.

   • [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”

   proof ↗⚑ flag

   Zero~partialclaimed3/10

   Only a general privacy claim ('Zero does not track, collect, or sell your data in any way') is evidenced, with no mention of read-pixel/tracking-pixel blocking specifically or a detailed data-handling policy. missing for 10: explicit read-receipt/tracking-pixel blocking feature, documentation of default-on behavior, a privacy policy detailing mail data handling, and independent confirmation of the no-tracking claim.

   • [github] “Zero does not track, collect, or sell your data in any way.”

   proof ↗⚑ flag

Migration

1. switcherImport my complete mail history and contacts from my old provider or client

   weight 1 · round to Shortwave
   Shortwave~partialcommunity4/10

   Shortwave is built directly on Gmail's APIs, so it can pull in an existing Gmail account's aliases and signatures (one user reported it 'imported all my aliases and signatures' during onboarding), but this is only a Gmail-to-Shortwave migration, not import from another provider/client like Outlook or Yahoo — a security-focused user explicitly noted 'it only works with Google servers.' Additionally, a documented free-plan limitation caps historical search import at 90 days, undercutting 'complete mail history.' Missing for 10: evidence of contacts import, support for non-Gmail providers, and confirmation that paid plans truly import full history without gaps.

   • [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”
   • [community] “Free plan limitation noted: emails from more than 90 days before signup aren't imported for search, and snoozed emails past that window won'…”
   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
   • [community] “User complaint: 'all these apps either want gmail way too many gmail permissions, and/or are hosted... I'm trying to get rid of gmail lol.'”

   proof ↗⚑ flag

   Zero—none0/10

   Zero connects to providers like Gmail/Outlook for unified inbox access, but no evidence describes any import/migration tool for bulk historical mail or contacts from an old provider/client — no mention of mbox/EML import, contact list import, or migration wizard.

   ⚑ flag

Search

1. power-userSearch is fast and precise — operators, filters, and ranked results across my full mail history

   weight 2 · round to Zero
   Shortwave!disputedcontradicted4/10

   Shortwave's AI assistant is documented to 'search your entire email history' (shortwave-docs-12/28), but community evidence shows the free plan doesn't import emails older than 90 days before signup for search, contradicting the 'full mail history' claim, and no evidence describes search operators, advanced filters, or ranked-result mechanics. Missing for 10: documented search operators/filters syntax, ranking algorithm details, confirmation that paid tiers truly cover unlimited history without caveats.

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [community] “Free plan limitation noted: emails from more than 90 days before signup aren't imported for search, and snoozed emails past that window won'…”

   proof ↗⚑ flag

   Zero~partialcommunity4/10

   Evidence shows a basic 'search emails with custom queries' and 'filter by labels' capability via the MCP server, but there is no documentation of advanced operators, ranked relevance, or performance/scale across full mail history; a community comment even flags missing basic navigation features, suggesting search UX is still immature. missing for 10: documented search operators/syntax, evidence of ranking/relevance across full historical mail, performance benchmarks, independent hands-on confirmation of search speed/precision.

   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [community] “hoping to see some more discussion here - i'd love to replace superhuman. However, until Zero has real keyboard navigation, i'll have to wai…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”

   proof ↗⚑ flag

Shortcuts

1. power-userDo everything from the keyboard — comprehensive shortcuts and a command palette — in an interface fast enough to never make me wait

   weight 3 · round to Zero
   Shortwave—none0/10

   The evidence pack contains no mentions of keyboard shortcuts, a command palette, or performance/speed benchmarks — all citations focus on AI features, integrations, and collaboration tools. Absence of evidence for this applicable axis (email clients commonly tout keyboard-driven UX, e.g. Superhuman comparisons appear in community items) yields 'none' rather than 'na'.

   ⚑ flag

   Zero!disputedcontradicted2/10

   Zero's own roadmap lists 'customizable keyboard shortcuts' as a planned (not yet shipped) feature, and a hands-on community comment explicitly states the product lacks 'real keyboard navigation' today, directly contradicting any power-user keyboard-first claim; no command palette is mentioned anywhere in the evidence. missing for 10: shipped keyboard shortcut system, command palette, any evidence of interface speed/responsiveness for power users.

   • [claimed-docs] “Customizable keyboard shortcuts”
   • [community] “hoping to see some more discussion here - i'd love to replace superhuman. However, until Zero has real keyboard navigation, i'll have to wai…”

   proof ↗⚑ flag

Channels

1. team-leadThe same inbox also handles adjacent customer channels — SMS, WhatsApp, social, or live chat — beside email

   weight 1 · round drawn
   Shortwave—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Routing

1. team-leadAssign conversations to teammates and route incoming mail with rules so ownership is explicit

   weight 2 · round to Shortwave
   Shortwave~partialcommunity3/10

   Shortwave offers team comments and @mention to loop teammates into a thread (giving them access to the email) and custom AI filters that can label/archive/star via plain-English rules, but there is no evidence of an explicit 'assign conversation to teammate' ownership feature or rule-based routing of incoming mail to specific team members/inboxes. missing for 10: explicit conversation assignment/ownership feature, mail routing rules tied to teammates, evidence of shared/team inbox queue management.

   • [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave, so you can plan how to respond together”
   • [claimed-docs] “Something special happens when you `@mention` a teammate in a comment – they suddenly get access to not just your comment, but the email too”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is a personal AI-powered email client with unified inbox, labels, and MCP tooling, but no evidence anywhere in the pack describes team features like assigning conversations to teammates or configuring routing/ownership rules — capabilities relevant for shared team inboxes. This is a fair axis for an email client, but no evidence supports it, so it's 'none' rather than 'na'.

   ⚑ flag

Shared inbox

1. team-leadWe can discuss an email in an internal side-thread — comments and @mentions beside the message — instead of forwarding copies around

   weight 2 · round to Shortwave
   Shortwave✓fullclaimed8/10

   Shortwave's Team Comments feature explicitly lets teammates privately discuss an email in-app rather than forwarding, with @mentions that grant the mentioned teammate access to the comment and the email — directly matching the story. Missing for 10: independent/hands-on corroboration of the comment-thread UX beyond vendor blog posts, and detail on comment threading/notification mechanics.

   • [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave, so you can plan how to respond together”
   • [claimed-docs] “Something special happens when you `@mention` a teammate in a comment – they suddenly get access to not just your comment, but the email too”
   • [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave”
   • [claimed-docs] “Something special happens when you @mention a teammate in a comment – they suddenly get access to not just your comment, but the email too”
   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence covers email management, MCP AI features, and self-hosting, but nothing describes internal side-threads with comments/@mentions for team discussion of emails without forwarding.

   ⚑ flag

2. team-leadMy team works shared inboxes together — shared accounts or team channels where everyone sees the same conversation state

   weight 3 · round to Shortwave
   Shortwave~partialcommunity5/10

   Shortwave offers team comments and @mention that grant teammates access to specific emails/threads (shortwave-docs-10,11,34,37), enabling some shared visibility and discussion. However, community evidence explicitly questions whether Shortwave's 'Bundles'/Workspaces model can replace true shared/team inboxes as found in dedicated tools (shortwave-comm-4), and there is no direct documentation of a shared-account or team-channel inbox where the whole team sees identical conversation state by default. Missing for 10: explicit shared-inbox/team-channel product feature, documentation of multi-user access to a single mailbox, and confirmation that collaboration extends beyond per-email comments to full inbox-level shared state.

   • [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave, so you can plan how to respond together”
   • [claimed-docs] “Something special happens when you `@mention` a teammate in a comment – they suddenly get access to not just your comment, but the email too”
   • [claimed-docs] “Something special happens when you @mention a teammate in a comment – they suddenly get access to not just your comment, but the email too”
   • [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave”
   • [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is positioned as a personal AI-powered unified inbox for individual users (Gmail/Outlook accounts), with no evidence of shared inboxes, team channels, or shared conversation state across multiple users; features described are individual email management, MCP tooling, and self-hosting, not multi-user collaboration.

   • [github] “Unified Inbox – Connect multiple email providers like Gmail, Outlook, and more.”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag

Followups

1. power-userSnooze conversations and set follow-up reminders that resurface a thread if nobody replies

   weight 2 · round to Shortwave
   Shortwave~partialcommunity4/10

   Community evidence confirms Shortwave has a snooze feature (comm-10 references 'snoozed emails' behavior), implying threads can be snoozed and resurfaced, but no evidence describes a follow-up reminder that resurfaces a thread specifically when nobody replies. Missing for 10: dedicated docs on follow-up/no-reply reminders, evidence of reminder triggers tied to reply detection, and confirmation of default snooze durations or scheduling UI for this specific workflow.

   • [community] “Free plan limitation noted: emails from more than 90 days before signup aren't imported for search, and snoozed emails past that window won'…”

   proof ↗⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions snooze, follow-up reminders, or resurfacing threads after no reply; the documented features cover labels, search, compose, AI Q&A, and self-hosting only.

   ⚑ flag

Inbox structure

1. power-userSelect many conversations at once and archive, label, or mark them done in one stroke

   weight 1 · round drawn
   Shortwave~partialclaimed4/10

   Shortwave's docs mention bulk-oriented behaviors—custom AI filters that automatically label/star/archive matching emails, and a one-click 'sweep away the rest' declutter action—that imply multi-conversation bulk actions, but there is no explicit mention of manually multi-selecting conversations and applying archive/label/mark-done in one stroke. Missing for 10: explicit multi-select UI documentation, confirmation that labels/archive/done can be applied simultaneously to a manual selection, and independent/hands-on confirmation of this specific workflow.

   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”

   proof ↗⚑ flag

   Zero~partialcommunity4/10

   Zero's MCP docs explicitly list 'Bulk delete emails' and 'Bulk archive emails' plus label modification tools, showing some bulk-action capability, but this is exposed via an AI/MCP tool interface rather than confirmed as a native UI multi-select action, and there's no mention of a 'mark done' state or how many items can be selected/acted on interactively. Community commentary even flags gaps in basic power-user UI ergonomics (no real keyboard navigation), suggesting bulk in-UI triage may be immature. missing for 10: confirmed UI multi-select archive/label/done action, evidence of a 'done' state, independent hands-on confirmation of bulk UI workflow.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Bulk delete emails - Bulk archive emails”
   • [claimed-docs] “Get all user labels - Create new custom labels with custom colors - Delete existing labels”
   • [community] “hoping to see some more discussion here - i'd love to replace superhuman. However, until Zero has real keyboard navigation, i'll have to wai…”

   proof ↗⚑ flag

2. power-userSplit my inbox into focused streams — important, team, newsletters, calendar invites — so triage happens in priority order, not arrival order

   weight 3 · round to Shortwave
   Shortwave✓fullcommunity8/10

   Shortwave's 'Splits' feature explicitly lets users divide one inbox into multiple focused inboxes by importance/type, each in its own tab, directly matching the triage-by-priority story, and independent community feedback (Front power-user) praised the related 'Bundles' grouping as 'top shelf.' Missing for 10: explicit documentation that the default splits match the exact categories named (team, newsletters, calendar invites) rather than just importance-based tabs, and more independent verification of the feature's real-world triage benefit.

   • [claimed-docs] “They’re a simple way to divide your one big inbox into multiple smaller, more focused inboxes – each in its own tab.”
   • [claimed-docs] “They're a simple way to divide your one big inbox into multiple smaller, more focused inboxes – each in its own tab.”
   • [claimed-docs] “Splits let you handle different types of emails at different times, so you can stay responsive where it matters most.”
   • [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows Zero supports labels, filtering, unified inbox, and AI Q&A, but there is no mention of dedicated inbox streams/views separating important, team, newsletter, and calendar-invite emails for priority-ordered triage. Labeling/filtering capabilities exist but no evidence of a stream-based triage UI or auto-categorized views as described in the story.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [claimed-docs] “Get all user labels - Create new custom labels with custom colors - Delete existing labels”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag