Superhuman Mail vs Shortwave

Multi account

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

   weight 3 · round to Superhuman Mail
   Superhuman Mail~partialclaimed6/10

   Superhuman clearly supports connecting and instantly switching between multiple Gmail and Outlook/Microsoft 365 accounts from one place (docs-12, docs-19, docs-20, docs-24, docs-40, docs-53), which covers two of the three providers in the story. However, no evidence mentions generic IMAP account support, so the 'switcher from any IMAP provider' part of the story is unaddressed. Missing for 10: explicit IMAP account support/connection, independent/hands-on confirmation of multi-provider account switching beyond vendor docs.

   • [claimed-docs] “you can instantly switch between Outlook and Gmail accounts without switching apps.”
   • [claimed-docs] “You can add all your Gmail and Outlook account calendars, and easily toggle them on and off.”
   • [claimed-docs] “you can instantly switch between Outlook and Gmail accounts without switching apps”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”
   • [claimed-docs] “it's available for [Gmail](https://blog.superhuman.com/gmail-alternatives/) and [Outlook](https://blog.superhuman.com/outlook-alternatives/)…”
   • [claimed-docs] “It helps you move faster, save time, respond sooner, and eliminate email anxiety. And it's available for Gmail and Outlook.”

   proof ↗⚑ flag

   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

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
   Superhuman Mail—none0/10

   Superhuman is a proprietary client layered on top of Gmail/Outlook accounts; the evidence pack contains no mention of IMAP/JMAP/SMTP access, standards-based export, or any data-portability guarantee — only MCP integration for AI assistants and account switching between Gmail/Outlook. No documentation addresses protocol-level openness or export, so switchers have no evidence their mail stays reachable outside Superhuman's own app.

   ⚑ flag

   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

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

   weight 1 · round drawn
   Superhuman Mail—none0/10

   Superhuman Mail is a cloud SaaS client layered on top of Gmail/Outlook accounts; there is no evidence of any self-hosted deployment option, open-source server, or ability to run the mail pipeline on infrastructure the user controls. All evidence points to a hosted, proprietary service with no self-host path, so this axis is not delivered.

   ⚑ flag

   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

Agent access

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   The probe explicitly shows llms.txt returns 404 and no agent-oriented docs (openapi/well-known) are found; while an MCP server exists, there's no evidence of llms.txt or similar agent-discovery docs a user could point an agent at.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Superhuman Mail is a GUI email client with an MCP server and agent triggers, but there is no evidence of a CLI, API, or documented mode to run the product headlessly or invoke it from a CI pipeline — probes for llms.txt and OpenAPI specs both returned 404. The story is plausible for an AI-native product with automation features, so it is not out of scope, but no evidence supports the specific headless/CI capability.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Shortwave
   Superhuman Mail—none0/10

   All evidence describes Superhuman Mail acting as an MCP *server* that Claude/ChatGPT connect to (docs-10, docs-37, docs-24, probe-3), not Superhuman itself consuming external MCP servers' tools as a client. There is no evidence that a user can plug third-party MCP servers into Superhuman so it gains their tools.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Superhuman Mail
   Superhuman Mail✓fullprobed8/10

   Superhuman documents an official Mail MCP server that connects Claude, ChatGPT, and other AI assistants to the inbox/calendar for summarizing, drafting, sending, and scheduling, with explicit send-approval controls, confirmed by a dedicated probe finding the official MCP page. Missing for 10: independent/hands-on third-party verification of the MCP server working (community evidence pack lacks any first-hand MCP usage reports) and technical details on the MCP server's implementation/spec compliance.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “Connect Claude or ChatGPT directly to your inbox to read, draft, and send emails with a single prompt — no copy-pasting required.”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Superhuman Mail
   Superhuman Mail~partialprobed6/10

   Superhuman ships a documented, public MCP server (email-mcp) that lets AI-native users drive inbox/calendar actions—summarize, draft, send, schedule—directly from Claude, ChatGPT and other AI tools, which is a real programmatic surface for agentic use. However, probes confirm there is no traditional REST/OpenAPI-documented public API (llms.txt and openapi.json endpoints all 404), so developers outside the MCP/AI-assistant flow have no documented way to integrate. Missing for 10: a general-purpose REST/GraphQL API with OpenAPI spec, and any independent/hands-on verification of the MCP server's reliability.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “Every draft matches your voice and tone, using your unique style for each person. You can review the drafts in Superhuman Mail, or edit and …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Evidence shows Superhuman Mail connects to Claude/ChatGPT via MCP and includes approval gates ('every send action requires explicit approval') plus admin-level 'connector permissions' governance, but there is no evidence of an actual scoped/least-privilege API credential or key system that an ai-native user can issue to individual agents. Probes for llms.txt and OpenAPI specs both return 404, suggesting no public API surface for credential scoping exists.

   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Evidence shows Superhuman ships an MCP server for AI assistants (docs-10, docs-37, probe-3) but there is no mention of official SDKs, client libraries, or public API documentation for developers; explicit probes for llms.txt and OpenAPI/Swagger specs both returned 404 (superhuman-probe-1, superhuman-probe-2), indicating no official SDK exists.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Evidence shows Superhuman offers an MCP server for AI assistant integration and an agents/automation feature, but nothing describes webhook subscriptions or event-driven push notifications for external systems; API/OpenAPI probes also returned 404s, indicating no documented webhook API.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Superhuman Mail
   Superhuman Mail✓fullclaimed9/10

   Superhuman Mail delivers extensive AI-generated insights from user data: Ask AI answers questions by mining inbox content (e.g., flight/hotel/offsite queries), Auto Drafts pull context from inbox, calendar, and web to write ready-to-send replies, Auto Labels classify and surface important emails, and read-status/follow-up nudges surface actionable insights. First-party docs are extensive and consistent across many features (Ask AI, Auto Drafts 2.0, Auto Labels, Email Assistant), though independent hands-on validation specifically of the AI-insight features (vs. general product commentary) is thin. Missing for 10: independent/hands-on corroboration specifically validating the accuracy or usefulness of AI-generated insights (most evidence is vendor-authored).

   • [claimed-docs] “You can now get rapid answers without having to remember senders, guess keywords, or comb through messages.”
   • [claimed-docs] “Just ask: _"where is the q2 offsite"_, _"when is my flight"_, _"where am I staying"_, and we'll immediately generate succinct answers.”
   • [claimed-docs] “Just ask: "where is the q2 offsite", "when is my flight", "where am I staying", and we'll immediately generate succinct answers.”
   • [claimed-docs] “Auto Drafts now gather context from your inbox, your calendar, and the web. They can use information from other emails, insert availability,…”
   • [claimed-docs] “Each draft can use your inbox, calendar, and the web to write replies that are ready to send.”
   • [claimed-docs] “Every message that needs a reply comes with a draft written in your voice. Each draft can use your inbox, calendar, and the web to write rep…”
   • [claimed-docs] “Superhuman AI will automatically separate marketing, cold pitches, and social network updates, so you can respond faster to what matters mos…”
   • [claimed-docs] “With Auto Labels, Superhuman Mail automatically classifies incoming messages — so you can focus on what matters most.”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Shortwave
   Superhuman Mail~partialclaimed6/10

   Superhuman documents proactive automations: Auto Archive/Auto Labels/Auto Drafts run automatically in the background, and a newer 'agents' feature lets users build proactive agents via chat or visual builder with admin-governed triggers and connectors. However, sending still requires explicit human approval, limiting true autonomy, and there is no independent/hands-on corroboration of the agent-builder feature working as described. Missing for 10: third-party verification of the visual builder/agent triggers, detail on failure/error handling for autonomous runs, and evidence of unattended send/execute actions.

   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”
   • [claimed-docs] “Superhuman AI can automatically archive marketing, cold pitches, and social network updates. Turn on Auto Archive, and eliminate inbox clutt…”
   • [claimed-docs] “Auto Drafts now gather context from your inbox, your calendar, and the web. They can use information from other emails, insert availability,…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Superhuman Mail✓fullclaimed8/10

   Superhuman ships a built-in AI assistant that auto-labels, archives, drafts replies, answers questions, and now supports building proactive agents from triggers/connectors with admin governance, all documented extensively as first-party features (docs-2,6,25,27,38,61,62,64). This directly matches delegating tasks to an in-product AI assistant beyond simple automation. Missing for 10: independent/hands-on user reports specifically validating the delegation/agent-building experience (community evidence covers general product sentiment, not this AI-assistant delegation feature).

   • [claimed-docs] “Every email that needs a reply comes with a draft—you can just edit and send.”
   • [claimed-docs] “If your email needs a response, you’re automatically reminded to follow up—with a draft already written and ready to send.”
   • [claimed-docs] “Handle every follow-up with one prompt. Superhuman Mail can check which emails have been read, draft all the nudges, and send when each reci…”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”
   • [claimed-docs] “Auto Drafts now gather context from your inbox, your calendar, and the web. They can use information from other emails, insert availability,…”
   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”
   • [claimed-docs] “Every draft matches your voice and tone, using your unique style for each person. You can review the drafts in Superhuman Mail, or edit and …”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Superhuman Mail✓fullprobed8/10

   Superhuman supports natural-language operation via Ask AI queries, plain-language personalization instructions, AI-prompt-based Auto Labels, and full MCP integration letting users drive inbox/calendar actions (summarize, draft, send, schedule) via Claude/ChatGPT with a single prompt. missing for 10: independent/hands-on verification of natural-language command accuracy and no first-party demo of complex multi-step NL commands beyond simple prompts.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “Connect Claude or ChatGPT directly to your inbox to read, draft, and send emails with a single prompt — no copy-pasting required.”
   • [claimed-docs] “Just ask: _"where is the q2 offsite"_, _"when is my flight"_, _"where am I staying"_, and we'll immediately generate succinct answers.”
   • [claimed-docs] “Add plain-language instructions like "write in lowercase" or "use this booking link" to personalize your writing and scheduling features.”
   • [claimed-docs] “You can even make your own Auto Labels with short AI prompts like "job applications" or "requests to review work".”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   There is no evidence of an interactive API reference or runnable examples; probes explicitly confirm no OpenAPI/swagger spec and no llms.txt is available, and the MCP server page offers no interactive docs/playground.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Direct probes for OpenAPI/Swagger specs and llms.txt all returned 404s, and no documentation mentions a downloadable machine-readable API spec; only an MCP server is offered, which is a separate mechanism, not an API spec.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   No evidence of any versioned public API or documented deprecation policy; probes for OpenAPI specs returned 404s, and there's no mention of API versioning or deprecation practices anywhere in the docs. The only developer-facing surface found is the MCP server, which is unrelated to API versioning guarantees. missing for 10: any public API documentation, version numbers, changelog/deprecation policy, or evidence of stable programmatic interfaces.

   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”

   proof ↗⚑ flag

   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

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 Superhuman Mail
   Superhuman Mail✓fullprobed8/10

   Superhuman documents a first-party MCP server connecting Claude/ChatGPT (and other assistants) to inbox and calendar, enabling reading, summarizing, drafting, and sending emails via prompts, with explicit send-approval controls and an official MCP feature probe confirming the endpoint exists. missing for 10: independent/hands-on third-party verification of the MCP integration working end-to-end, and detail on triage/labeling actions being fully agent-driven rather than app-side AI.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “Connect Claude or ChatGPT directly to your inbox to read, draft, and send emails with a single prompt — no copy-pasting required.”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “Every draft matches your voice and tone, using your unique style for each person. You can review the drafts in Superhuman Mail, or edit and …”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   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

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 drawn
   Superhuman Mail✓fullclaimed8/10

   Superhuman's Ask AI feature directly supports natural-language Q&A grounded in the inbox and calendar (e.g., 'where is the q2 offsite', 'when is my flight', 'where am I staying'), and the MCP integration extends this to Claude/ChatGPT for cross-inbox/calendar queries, drafting, and scheduling grounded in real data. Missing for 10: independent/hands-on evidence validating accuracy of 'grounded answers' across a full inbox+calendar corpus, and detail on how well it surfaces 'what's outstanding' beyond follow-up reminders.

   • [claimed-docs] “You can now get rapid answers without having to remember senders, guess keywords, or comb through messages.”
   • [claimed-docs] “Just ask: _"where is the q2 offsite"_, _"when is my flight"_, _"where am I staying"_, and we'll immediately generate succinct answers.”
   • [claimed-docs] “Just ask: "where is the q2 offsite", "when is my flight", "where am I staying", and we'll immediately generate succinct answers.”
   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”

   proof ↗⚑ flag

   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

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 Superhuman Mail
   Superhuman Mail✓fullclaimed9/10

   Superhuman's Auto Drafts feature explicitly writes replies in the user's own voice/tone (matching style from sent emails, even per-recipient), pulling context from inbox/calendar/web, and presents them ready to edit and send rather than generic boilerplate — with explicit human approval before sending. This is well-documented across first-party docs with consistent detail; missing for 10: independent/hands-on user corroboration of draft quality/voice-matching accuracy beyond vendor claims.

   • [claimed-docs] “Just jot down some phrases, and we'll turn them into a full email. Best of all, the email sounds like you. Superhuman AI matches the voice a…”
   • [claimed-docs] “Every message that needs a reply comes with a draft written in your voice.”
   • [claimed-docs] “Every draft matches your voice and tone, using your unique style for each person.”
   • [claimed-docs] “Every draft matches your voice and tone, using your unique style for each person. You can review the drafts in Superhuman Mail, or edit and …”
   • [claimed-docs] “Auto Drafts now gather context from your inbox, your calendar, and the web. They can use information from other emails, insert availability,…”
   • [claimed-docs] “Each draft can use your inbox, calendar, and the web to write replies that are ready to send.”
   • [claimed-docs] “Every message that needs a reply comes with a draft written in your voice. Each draft can use your inbox, calendar, and the web to write rep…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “with Auto Drafts 2.0, every message that needs a reply comes with a draft. You can just edit and send.”

   proof ↗⚑ flag

   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

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 Superhuman Mail
   Superhuman Mail✓fullclaimed8/10

   Superhuman documents auto-labeling ('Auto Labels'), custom AI-prompt categories, auto-archiving of low-priority mail, inbox splitting into topic tabs, and immediate labeling on arrival — directly matching triage/categorization needs. Steerability is evidenced via custom prompt-based Auto Labels, plain-language instructions, and admin governance controls, plus auditability via draft review before sending and explicit send approval. missing for 10: independent/hands-on validation of triage accuracy or audit trail is absent, and community evidence is largely about UI/performance rather than AI triage quality.

   • [claimed-docs] “Superhuman AI can automatically archive marketing, cold pitches, and social network updates. Turn on Auto Archive, and eliminate inbox clutt…”
   • [claimed-docs] “Superhuman AI will automatically separate marketing, cold pitches, and social network updates, so you can respond faster to what matters mos…”
   • [claimed-docs] “You can even make your own Auto Labels with short AI prompts like "job applications" or "requests to review work".”
   • [claimed-docs] “Turn on Auto Archive, and eliminate inbox clutter for good.”
   • [claimed-docs] “Auto Labels, Superhuman AI will automatically separate marketing, cold pitches, and social network updates, so you can respond faster to wha…”
   • [claimed-docs] “you can make your own Auto Labels with short AI prompts, and then split your inbox into tabs using these custom Auto Labels.”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”
   • [claimed-docs] “Emails are labeled the moment they arrive, so you can see what's important and what's not.”
   • [claimed-docs] “Custom Auto Labels let you categorize emails with your own AI prompts. (Available for our Business and Enterprise customers.)”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Superhuman Mail~partialclaimed6/10

   Superhuman supports batch-style operations like Auto Archive, Auto Labels, and 'Handle every follow-up with one prompt' (checking read status, drafting all nudges, sending in bulk) plus MCP-driven workflows that run across the whole inbox/calendar, giving genuine bulk automation for triage, labeling, and follow-ups. However, this is scoped to email/calendar items only and there's no evidence of arbitrary bulk operations across many items in a single explicit action (e.g., bulk delete/move/tag N selected emails via UI or API in one command) or bulk operation limits/performance at scale. missing for 10: evidence of explicit multi-item bulk actions (e.g., select-and-bulk-process UI), scale/performance data on bulk automation, and independent/hands-on confirmation of bulk operations working reliably.

   • [claimed-docs] “Handle every follow-up with one prompt. Superhuman Mail can check which emails have been read, draft all the nudges, and send when each reci…”
   • [claimed-docs] “Superhuman Mail can check which emails have been read, draft all the nudges, and send when each recipient is most likely to open it.”
   • [claimed-docs] “Turn on Auto Archive, and eliminate inbox clutter for good.”
   • [claimed-docs] “Superhuman AI can automatically archive marketing, cold pitches, and social network updates. Turn on Auto Archive, and eliminate inbox clutt…”
   • [claimed-docs] “You can even make your own Auto Labels with short AI prompts like "job applications" or "requests to review work".”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”
   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Superhuman Mail✓fullclaimed7/10

   Superhuman documents explicit rule/trigger-based automation: custom Auto Labels driven by user-defined AI prompts, Auto Archive, Auto Drafts, and a stated capability to "create agents that run proactively based on triggers you set and the work you connect" with admin governance over agent building. This directly matches the ai-native automation-depth story of defining rules that fire actions on events. missing for 10: independent/hands-on verification of the rule engine's reliability and richer documentation of trigger/condition/action logic beyond marketing copy.

   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”
   • [claimed-docs] “You can even make your own Auto Labels with short AI prompts like "job applications" or "requests to review work".”
   • [claimed-docs] “you can make your own Auto Labels with short AI prompts, and then split your inbox into tabs using these custom Auto Labels.”
   • [claimed-docs] “Custom Auto Labels let you categorize emails with your own AI prompts. (Available for our Business and Enterprise customers.)”
   • [claimed-docs] “Superhuman AI can automatically archive marketing, cold pitches, and social network updates. Turn on Auto Archive, and eliminate inbox clutt…”
   • [claimed-docs] “Turn on Auto Archive, and eliminate inbox clutter for good.”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed5/10

   Superhuman documents 'agents that run proactively based on triggers you set' and MCP-driven 'workflows that run across your inbox and calendar,' suggesting some automation/triggering capability, but there's no detail on recurring/scheduled job mechanics (e.g., cron-like scheduling, workflow persistence) and no independent/hands-on corroboration. Missing for 10: explicit recurring-schedule configuration details, independent verification that these agent workflows actually run repeatedly/reliably, and more than a passing marketing mention.

   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”

   proof ↗⚑ flag

   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

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Superhuman Mail—none0/10

   Superhuman offers automations like Auto Labels, Auto Archive, agent builders, and MCP-driven workflows, but there is no evidence of version history, review/audit trails, or rollback capability for these automations. Missing for 10: version history of automation rules, diff/review UI before changes take effect, rollback/undo mechanism for automation edits.

   ⚑ flag

   Shortwave—none0/10

   Shortwave offers AI filters, triggers, and MCP integrations for automation, but there is no evidence of version history, review workflows, diffs, or rollback capability for these automations.

   ⚑ flag

Calendar

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

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed6/10

   Superhuman Calendar lets users view their day in the email side panel, add/toggle multiple calendars, and use 'Find Time' to schedule meetings with teammates across time zones, all without leaving the client. However, none of the evidence explicitly confirms responding to/RSVPing on calendar invites or manually creating new calendar events from within the client. Missing for 10: explicit invite-response (accept/decline) capability, explicit event-creation UI/flow evidence, independent hands-on confirmation of calendar features.

   • [claimed-docs] “Simply add teammates, click "Find Time", and instantly see when everyone is free.”
   • [claimed-docs] “You can add all your Gmail and Outlook account calendars, and easily toggle them on and off.”
   • [claimed-docs] “When any email mentions a date, Superhuman Mail will show your day in the right side panel — so you always have context.”
   • [claimed-docs] “Working across time zones? Add a secondary time zone, so scheduling between San Francisco and New York (or London and Tokyo) is effortless.”
   • [claimed-docs] “Add a secondary time zone, so scheduling between San Francisco and New York (or London and Tokyo) is effortless.”

   proof ↗⚑ flag

   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

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

   weight 1 · round to Superhuman Mail
   Superhuman Mail✓fullclaimed7/10

   Superhuman's Auto Drafts explicitly 'insert availability' pulled from your calendar (docs-38), the Calendar feature lets you 'Find Time' to instantly see when teammates are free (docs-7), and users can add plain-language instructions like 'use this booking link' to personalize scheduling in drafts (docs-9, docs-54, docs-60). Missing for 10: independent/hands-on verification of this exact workflow and more detail on native booking-link generation vs. relying on a user-supplied link.

   • [claimed-docs] “Auto Drafts now gather context from your inbox, your calendar, and the web. They can use information from other emails, insert availability,…”
   • [claimed-docs] “Simply add teammates, click "Find Time", and instantly see when everyone is free.”
   • [claimed-docs] “Add plain-language instructions like "write in lowercase" or "use this booking link" to personalize your writing and scheduling features.”
   • [claimed-docs] “Add plain-language instructions like "write in lowercase" or "use this booking link" to personalize your writing and schedul”
   • [claimed-docs] “Add plain-language instructions like "write in lowercase" or "use this booking link" to personalize your writing”

   proof ↗⚑ flag

   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

Sending

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

   weight 1 · round to Superhuman Mail
   Superhuman Mail~partialcommunity6/10

   Superhuman docs confirm read-status tracking ('check which emails have been read', 'Read statuses are now shared across your team') and community evidence (superhuman-comm-1, criticizing image-based tracking as 'spying') independently corroborates that read/open tracking is a real, functioning feature. However, no evidence explicitly confirms a timestamped 'when opened' view for individual recipients—only binary read/unread status and team-level sharing are documented. Missing for 10: explicit per-recipient open-time timestamps, hands-on verification of accuracy/reliability of the read-tracking mechanism.

   • [claimed-docs] “Handle every follow-up with one prompt. Superhuman Mail can check which emails have been read, draft all the nudges, and send when each reci…”
   • [claimed-docs] “Superhuman Mail can check which emails have been read, draft all the nudges, and send when each recipient is most likely to open it.”
   • [claimed-docs] “Team Read Statuses: Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [community] “"Superhuman doesn't even let its own customers turn images off. So merely by using Superhuman, you are vulnerable to the exact same spying t…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Shortwave
   Superhuman Mail—none0/10

   No evidence in the pack mentions scheduled send or an undo-send grace window feature for Superhuman Mail; the docs cover AI drafting, labeling, MCP integration, and other features but nothing about delayed/scheduled sending or send-undo functionality.

   ⚑ flag

   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

Templates

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

   weight 2 · round drawn
   Superhuman Mail~partialclaimed5/10

   Superhuman's Snippets feature is well documented — insert commonly-used phrases, paragraphs, or whole emails via keyboard shortcut, and share snippets across a team — directly matching the 'saved templates instead of retyping' part of the story. However, no evidence mentions variable/placeholder support (e.g., auto-filled name/date fields) or attaching files as part of a snippet/template. Missing for 10: variable/placeholder support in snippets, attachment bundling within snippets, independent hands-on confirmation of these specifics.

   • [claimed-docs] “Insert commonly-used phrases, paragraphs, or whole emails with a simple keyboard shortcut.”
   • [claimed-docs] “You can also share Snippets with your team, so your team can move faster, with consistent, up-to-date, and high-performing messaging.”
   • [claimed-docs] “Snippets can now be shared across your team, so you can all work faster with current and consistent messaging.”
   • [claimed-docs] “With Snippets, you can automate typing and push past this limit. Insert commonly-used phrases, paragraphs, or whole emails with a simple key…”

   proof ↗⚑ flag

   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

Offline

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

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed5/10

   Superhuman's own docs repeatedly claim the app 'works perfectly offline' and even when the connection is terrible, suggesting core reading/composing functionality persists without a network. However, there is no explicit documentation of offline search behavior or how changes (sent drafts, read/archive actions) reconcile once reconnected, and no independent/hands-on corroboration of offline sync reliability. missing for 10: explicit description of offline search indexing, detail on conflict resolution/sync-on-reconnect mechanics, and third-party verification of offline behavior.

   • [claimed-docs] “Superhuman gives you a new way to work with Gmail. It works perfectly offline.”
   • [claimed-docs] “Superhuman gives you a new way to work with Gmail. It works perfectly offline. It works even when online, and your internet connection is te…”
   • [claimed-docs] “It works perfectly offline. It works even when online, and your internet connection is terrible.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialprobed5/10

   Superhuman exposes an official MCP server (email-mcp) letting AI assistants read, draft, send emails, summarize threads, and schedule meetings — a real but curated subset of UI actions — while probes show no public REST/OpenAPI spec (404s on openapi.json/llms.txt), meaning many UI capabilities (Auto Labels config, split inbox, Snippets, team features, Command palette, offline mode) have no documented API equivalent. Missing for 10: full OpenAPI/REST documentation, evidence of parity for non-email/calendar UI features (labels, snippets, team collaboration, command palette), and independent confirmation that MCP covers 1:1 UI functionality.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “Connect Claude or ChatGPT directly to your inbox to read, draft, and send emails with a single prompt — no copy-pasting required.”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Superhuman Mail—none0/10

   No evidence of any data export capability, open-format export, or account portability/exit tooling in the evidence pack; the product is an email client layered on Gmail/Outlook but nothing documents exporting Superhuman-specific data (labels, snippets, agent configs) or facilitating leaving the platform. missing for 10: data export feature docs, open format (e.g. mbox/CSV/JSON) support, migration/exit tooling, any independent confirmation of portability.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Superhuman Mail is closed-source proprietary SaaS; no evidence of any open-licensed source availability. missing for 10: any mention of open-source license, public repository, or source availability.

   ⚑ flag

   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

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Superhuman Mail—none0/10

   Superhuman Mail is a proprietary SaaS email client; no evidence anywhere in the pack indicates a self-hostable version, on-prem deployment, or open-source core. All evidence describes a cloud-hosted product with API/MCP integrations, not self-hosting options.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or storage location choices for Superhuman Mail; the axis applies to an email/data platform but no capability is documented.

   ⚑ flag

   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

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

   weight 3 · round drawn
   Superhuman Mail—none0/10

   No evidence in the pack addresses data usage for AI model training, opt-out settings, or any privacy/data-retention policy statement — the evidence pack is entirely about feature functionality (AI drafting, labeling, MCP, calendar) with no mention of training-data controls. missing for 10: any privacy policy statement on AI training data usage, an opt-out or opt-in toggle for model training, or third-party confirmation of data handling practices.

   ⚑ flag

   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

3. ai-native userControl data retention and deletion

   weight 2 · round to Shortwave
   Superhuman Mail—none0/10

   The evidence pack contains no mention of data retention settings, deletion controls, or data lifecycle policies for Superhuman Mail or its AI/MCP features—only feature descriptions, community sentiment, and unrelated probes. This is a fair privacy-posture question for an AI-native email product, but no evidence shows such controls exist.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   No evidence pack item addresses telemetry, analytics opt-out, or usage-tracking controls; one community comment even notes Superhuman does not let users disable image-loading tracking, but this doesn't constitute a documented telemetry opt-out and can't establish 'disputed' since no vendor claim of an opt-out exists to contradict.

   ⚑ flag

   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

Protection

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

   weight 1 · round drawn
   Superhuman Mail—none0/10

   No evidence anywhere in the pack mentions email aliasing, masked/anonymous addresses, or any feature to hide a user's real address from sign-ups or strangers; Superhuman's documented features focus on AI triage, drafting, scheduling, and MCP integrations, not address privacy. Missing for 10: any mention of alias generation, masked email addresses, or privacy-relay/forwarding features.

   ⚑ flag

   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

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 drawn
   Superhuman Mail—none0/10

   No documentation claims Superhuman blocks tracking pixels by default or explains transparent data handling; in fact, community evidence explicitly states Superhuman does not let users disable images/tracking pixels, meaning senders' read-tracking is not blocked. No privacy-policy or data-handling transparency evidence is present either.

   • [community] “"Superhuman doesn't even let its own customers turn images off. So merely by using Superhuman, you are vulnerable to the exact same spying t…”

   proof ↗⚑ flag

   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

Migration

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

   weight 1 · round to Shortwave
   Superhuman Mail—none0/10

   No evidence in the pack describes importing mail history or contacts from another provider/client; Superhuman only connects live Gmail/Outlook accounts, with no mention of migration, historical import, or contact import tools. Missing for 10: any documentation of import/migration functionality, historical mail transfer, or contact import from other providers.

   ⚑ flag

   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

Search

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

   weight 2 · round drawn
   Superhuman Mail!disputedcontradicted4/10

   Superhuman markets 'Ask AI' as a way to get answers without keyword search (docs-4, docs-18, docs-26) but the evidence pack contains no documentation of actual search operators, filters, or ranked-results syntax across full mail history. A hands-on ex-user reports search was actually slow ('ten seconds' vs Gmail's instant) contradicting the 'fastest email' marketing, while another user reports search is 'blazing fast' (superhuman-comm-7 vs superhuman-comm-9), creating a genuine dispute rather than settled capability. missing for 10: documented search operator syntax, filter capabilities, ranked-results mechanism, and independent confirmation resolving the speed contradiction.

   • [claimed-docs] “You can now get rapid answers without having to remember senders, guess keywords, or comb through messages.”
   • [claimed-docs] “Just ask: _"where is the q2 offsite"_, _"when is my flight"_, _"where am I staying"_, and we'll immediately generate succinct answers.”
   • [claimed-docs] “Just ask: "where is the q2 offsite", "when is my flight", "where am I staying", and we'll immediately generate succinct answers.”
   • [community] “"I am an ex-user. A search through my email archive would regularly take ten seconds while gmail would do it instantly... my experience was …”
   • [community] “"My experience is that search and UI transitions are blazing fast. It crashes (rarely, but more than I like) and requires a restart. But I l…”

   proof ↗⚑ flag

   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

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 Superhuman Mail
   Superhuman Mail!disputedcontradicted6/10

   Superhuman documents a comprehensive Cmd+K command palette that surfaces every action and teaches shortcuts (docs-8, docs-34) plus fast reply shortcuts (docs-67), fitting the keyboard-power-user story. However, hands-on community reports are split: some users call it 'blazingly fast' (comm-9), while at least one ex-user reports search taking ten seconds vs instant in Gmail, directly contradicting the 'never wait' claim (comm-7), and another calls the UI just a 'cuter UI' around Gmail features with no real speed edge (comm-12). Missing for 10: a documented exhaustive keyboard-shortcut reference beyond the command palette, and independent benchmark data resolving the conflicting speed reports.

   • [claimed-docs] “Cmd+K brings up Superhuman Command, where you can instantly do any action — and also learn the shortcut for next time.”
   • [claimed-docs] “In Superhuman, one shortcut rules them all: Cmd+K. Cmd+K brings up Superhuman Command, where you can instantly do any action”
   • [claimed-docs] “You can reply to important messages faster with blazingly fast shortcuts and features like Instant Intro.”
   • [community] “"I am an ex-user. A search through my email archive would regularly take ten seconds while gmail would do it instantly... my experience was …”
   • [community] “"My experience is that search and UI transitions are blazing fast. It crashes (rarely, but more than I like) and requires a restart. But I l…”
   • [community] “"They essentially just teach you how to do things that gmail already lets you do, but put a cuter UI around it, and they force teach you con…”

   proof ↗⚑ flag

   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

Channels

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

   weight 1 · round drawn
   Superhuman Mail—none0/10

   All evidence is about email (Gmail/Outlook) plus calendar integration; there is no mention of SMS, WhatsApp, social, or live chat channels being unified into the same inbox. The product is positioned strictly as an email/calendar client with AI and MCP integrations, not an omnichannel customer messaging platform.

   ⚑ flag

   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

Routing

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

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed4/10

   Superhuman offers team-collaboration signals like shared read statuses, reply indicators, and @mention team comments that help avoid duplicate work, plus shared snippets and team scheduling — but there is no evidence of formal conversation assignment or rule-based mail routing that establishes explicit ownership of a thread to a specific teammate. Missing for 10: dedicated 'assign to teammate' functionality, configurable routing/ownership rules for incoming mail, and any independent confirmation these team features work as advertised.

   • [claimed-docs] “Team Read Statuses: Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “Team Reply Indicators: See when your team is replying, so you can avoid double work and embarrassing collisions.”
   • [claimed-docs] “let you @mention teammates, share live email views, and coordinate responses without external recipients seeing internal discussions”
   • [claimed-docs] “Snippets can now be shared across your team, so you can all work faster with current and consistent messaging.”
   • [claimed-docs] “Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “See when your team is replying, so you can avoid double work and embarrassing collisions.”

   proof ↗⚑ flag

   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

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 drawn
   Superhuman Mail✓fullclaimed8/10

   Superhuman's Team Comments feature explicitly supports @mentioning teammates, sharing live email views, and coordinating internal discussion without external recipients seeing it — directly matching the story's side-thread/comment use case, backed by Team Read Statuses and Reply Indicators for coordination. Missing for 10: independent/hands-on validation of the comment threading UX and details on comment persistence/notification workflow beyond vendor blog claims.

   • [claimed-docs] “let you @mention teammates, share live email views, and coordinate responses without external recipients seeing internal discussions”
   • [claimed-docs] “Team Read Statuses: Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “Team Reply Indicators: See when your team is replying, so you can avoid double work and embarrassing collisions.”
   • [claimed-docs] “Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “See when your team is replying, so you can avoid double work and embarrassing collisions.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Superhuman Mail
   Superhuman Mail~partialclaimed6/10

   Superhuman ships several team-collaboration features that approximate shared inbox awareness — team read statuses, reply indicators to avoid double-replies, team comments for internal coordination without external visibility, and shared snippets/scheduling — giving a team-lead's group real-time visibility into who's handling what (superhuman-docs-49,50,51,55,56,71,72,73). However, this is built on individually-owned mailboxes with cross-visibility signals, not a true shared/group inbox or shared account model where the whole team works one conversation queue with assignment/ownership. Missing for 10: evidence of a genuine shared mailbox/account model, ticket-style assignment of conversations, and independent confirmation of how well these team signals work in practice.

   • [claimed-docs] “Team Read Statuses: Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “Team Reply Indicators: See when your team is replying, so you can avoid double work and embarrassing collisions.”
   • [claimed-docs] “Team Scheduling: See when your team is free, so you can schedule at the speed of thought.”
   • [claimed-docs] “let you @mention teammates, share live email views, and coordinate responses without external recipients seeing internal discussions”
   • [claimed-docs] “Snippets can now be shared across your team, so you can all work faster with current and consistent messaging.”
   • [claimed-docs] “Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “See when your team is replying, so you can avoid double work and embarrassing collisions.”
   • [claimed-docs] “See when your team is free, so you can schedule at the speed of thought.”

   proof ↗⚑ flag

   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

Followups

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

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed6/10

   Superhuman documents an automated follow-up reminder system that drafts nudges and resurfaces threads needing a response when no reply has come ('automatically reminded to follow up—with a draft already written', 'check which emails have been read, draft all the nudges, and send when each recipient is most likely to open it'), closely matching the reminder half of the story. However, there is no explicit mention of a 'snooze' feature to temporarily hide a conversation and resurface it later, which is a core part of the story. Missing for 10: explicit snooze/defer-conversation functionality, independent/hands-on confirmation of the follow-up reminder behavior.

   • [claimed-docs] “If your email needs a response, you’re automatically reminded to follow up—with a draft already written and ready to send.”
   • [claimed-docs] “If your email needs a response, you're automatically reminded to follow up—with a draft already written and ready to send.”
   • [claimed-docs] “Handle every follow-up with one prompt. Superhuman Mail can check which emails have been read, draft all the nudges, and send when each reci…”
   • [claimed-docs] “Superhuman Mail can check which emails have been read, draft all the nudges, and send when each recipient is most likely to open it.”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”
   • [claimed-docs] “works inside Gmail and Outlook to label, declutter, draft, and remind automatically”

   proof ↗⚑ flag

   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

Inbox structure

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

   weight 1 · round to Shortwave
   Superhuman Mail~partialclaimed3/10

   Superhuman documents AI-driven Auto Archive and Auto Labels that batch-classify/archive whole categories of mail automatically, plus a command palette (Cmd+K) said to 'instantly do any action,' and split-inbox tabs to 'get through emails of the same type, at the same time' — all of which gesture at bulk triage outcomes, but none explicitly describe a manual multi-select-then-archive/label/mark-done workflow across many conversations. Missing for 10: explicit documentation or independent confirmation of manual multi-select bulk actions (checkbox/shift-click select many threads, then batch archive/label/mark-done in one keystroke).

   • [claimed-docs] “Turn on Auto Archive, and eliminate inbox clutter for good.”
   • [claimed-docs] “you can focus on a specific topic — and get through emails of the same type, at the same time.”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”
   • [claimed-docs] “In Superhuman, one shortcut rules them all: Cmd+K. Cmd+K brings up Superhuman Command, where you can instantly do any action”
   • [claimed-docs] “splitting your inbox allows you to divide your inbox into different areas of focus — based on the types of email you receive mos”

   proof ↗⚑ flag

   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

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 drawn
   Superhuman Mail✓fullclaimed8/10

   Superhuman explicitly documents 'split inbox' functionality with custom categories like VIP, Notifications, Calendar, and Team, plus custom Auto Labels that let users organize incoming mail into tabs by type so triage happens by focus area rather than arrival order. This is a first-party documented feature with a dedicated blog post, not just a vague claim. missing for 10: independent/hands-on confirmation of the split-inbox feature specifically (community evidence covers other aspects of Superhuman but not this feature) and detail on how priority ordering interacts with arrival order within each stream.

   • [claimed-docs] “in Superhuman Mail, you can design your own categories: like "VIP", "Notifications", "Calendar", or "Team".”
   • [claimed-docs] “you can design your own categories: like "VIP", "Notifications", "Calendar", or "Team".”
   • [claimed-docs] “splitting your inbox allows you to divide your inbox into different areas of focus — based on the types of email you receive mos”
   • [claimed-docs] “splitting your inbox allows you to divide your inbox into different areas of focus — based on the types of email you receive most”
   • [claimed-docs] “you can make your own Auto Labels with short AI prompts, and then split your inbox into tabs using these custom Auto Labels.”
   • [claimed-docs] “you can make your own Auto Labels with short AI prompts, and then split your inbox into tabs using these custom Auto Labels”
   • [claimed-docs] “you can focus on a specific topic — and get through emails of the same type, at the same time.”
   • [claimed-docs] “Custom Auto Labels let you categorize emails with your own AI prompts. (Available for our Business and Enterprise customers.)”

   proof ↗⚑ flag

   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