Claude vs Microsoft Copilot

Agent access

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

   weight 2 · round to Claude
   Claude✓fullprobed7/10

   A probe confirms Claude's support site serves a working llms.txt (HTTP 200) listing topic links, and numerous individual documentation pages are available in clean .md format (e.g. claude-docs-1 through 63 all resolve as .md URLs), making the docs directly consumable by an agent. Missing for 10: confirmation that llms.txt/agent-readable docs exist on the main claude.com domain (only support.claude.com was probed), and independent/community evidence that agents actually consume these successfully rather than just first-party doc structure.

   • [probe] “PROBE llms.txt: HTTP 200 at https://support.claude.com/llms.txt # Claude Help Center > Search for answers or browse by topic ## English #…”
   • [claimed-docs] “You can prompt Claude to search through your previous conversations to find and reference relevant information in new chats.”
   • [claimed-docs] “This article explains how chat search and memory work, what Claude does and doesn’t remember, how to review and edit what’s saved, and how t…”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.claude.com/en/.md”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   Probes show no llms.txt, no markdown docs endpoint, and no OpenAPI spec for Microsoft Copilot's support site, and no evidence anywhere in the pack of agent-oriented documentation formats being offered. This axis applies (any product could publish llms.txt or agent-friendly docs) but there is no evidence Copilot does so.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/copilot.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

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

   weight 3 · round to Claude
   Claude✓fullprobed9/10

   Claude documents connecting to both remote MCP servers via custom connectors and installing local MCP servers on Claude Desktop as easily as browser extensions, plus a unified directory for finding/installing connectors, letting Claude use their tools. Missing for 10: independent/hands-on verification of MCP tool usage reliability beyond vendor docs.

   • [claimed-docs] “Build your own remote MCP servers to connect with any tool.”
   • [claimed-docs] “You can: Connect Claude to existing remote MCP servers. Build your own remote MCP servers to connect with any tool.”
   • [claimed-docs] “You can: - Connect Claude to existing remote MCP servers. - Build your own remote MCP servers to connect with any tool.”
   • [claimed-docs] “installing and managing local MCP servers has become significantly easier... install local MCP servers on your computer as easily as browser…”
   • [claimed-docs] “you can now install local MCP servers on your computer as easily as browser extensions”
   • [claimed-docs] “Our unified directory brings skills, connectors, and plugins together in one place so you can find and install everything that customizes Cl…”
   • [probe] “official MCP server documented at https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   The evidence pack describes Copilot connecting to first-party consumer services (OneDrive, Outlook.com, Google Drive/Gmail) via 'Copilot connectors,' but there is no mention of MCP (Model Context Protocol) server support or an ability for users to plug in arbitrary MCP tool servers. This is an applicable axis for an AI assistant product, but no evidence shows the capability exists.

   • [claimed-docs] “Copilot can connect with the following consumer services: * Microsoft OneDrive * Microsoft Outlook.com (email, calendar, and contacts) …”
   • [claimed-docs] “Copilot can connect with the following consumer services: Microsoft OneDrive, Microsoft Outlook.com (email, calendar, and contacts), Google …”
   • [claimed-docs] “Copilot connectors are currently available on Copilot.com and on Copilot Mobile (iOS and Android)”

   proof ↗⚑ flag

3. ai-native userUse an official CLI

   weight 2 · round to Claude
   Claude!disputedcontradicted6/10

   Anthropic ships an official CLI, Claude Code, well documented for terminal-based coding, deployment, debugging, and even screen-reader accessibility (claude-docs-8, claude-docs-23, claude-docs-52, claude-docs-65). However, a hands-on community report describes it as an 'empty unresponsive terminal' upon first use, contradicting the polished experience implied by docs, and another notes serious code-quality issues in the CLI's own codebase (claude-comm-13, claude-comm-15). missing for 10: broader independent corroboration of reliable day-to-day CLI usage, resolution of reported unresponsiveness, and evidence the code-quality issues have been fixed.

   • [claimed-docs] “Build with Claude Code in your terminal, then deploy to a URL Claude can reach. Test and verify in the browser with the Chrome extension. De…”
   • [claimed-docs] “Build with Claude Code in your terminal, then deploy to a URL Claude can reach. Test and verify in the browser with the Chrome extension.”
   • [claimed-docs] “Build with Claude Code in your terminal, then deploy to a URL Claude can reach”
   • [claimed-docs] “It was built with and for screen reader users, and it's useful to anyone who wants plain output for braille displays, slow connections, or t…”
   • [community] “Tried claude code, and have an empty unresponsive terminal. Looks cool in the demo though, but not sure this is going to perform better than…”
   • [community] “src/cli/print.ts is the single worst function in the codebase by every metric: 3,167 lines long, 12 levels of nesting at its deepest, ~486 b…”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   No evidence of an official CLI for Microsoft Copilot; all evidence covers chat, browser, and Office app integrations, with probes confirming no machine-readable API/CLI artifacts.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/copilot.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

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

   weight 3 · round to Claude
   Claude~partialprobed3/10

   Evidence only hints at API-like surfaces (an Enterprise Compliance API for audit/chat data access, and references to using the Claude API/Console to power products) but never surfaces the actual general-purpose public API documentation for driving Claude's core capabilities; automated probes for an OpenAPI/swagger spec on the docs site returned 404s. Missing for 10: direct citation of the main Claude API reference docs, authentication/quickstart guides, and confirmation of comprehensive public API coverage beyond compliance/audit data.

   • [claimed-docs] “Audit logs: capture key information about user actions, system events, and data access. ... Compliance API: programmatically access Claude u…”
   • [claimed-docs] “Audit logs: capture key information about user actions, system events, and data access.”
   • [claimed-docs] “Enterprise includes everything in the Team plan, plus the following: - Security features to ensure the safety and compliance of your organiz…”
   • [claimed-docs] “You can use the prompt improver in the Claude Console to automatically adapt prompts that were originally written for other AI models.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.claude.com/openapi.json, https://support.claude.com/swagger.json, https://support.cl…”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   No evidence of a documented public API for programmatically driving Microsoft Copilot; probes for OpenAPI/llms.txt specs all returned 404, and all docs describe end-user chat/UI interactions rather than API access. Missing for 10: any public API documentation, SDK, or endpoint spec that lets developers programmatically invoke Copilot's capabilities.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/copilot.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Claude—none0/10

   No evidence describes scoped or least-privilege API credential issuance for agents; enterprise features mention audit logs and compliance API access but nothing about creating scoped/restricted API keys or credentials for agent use. Missing for 10: any documentation of API key scoping, permission tiers, or least-privilege credential management for agents.

   ⚑ flag

   Microsoft Copilot—none0/10

   No evidence describes issuing scoped or least-privilege API credentials for an agent; Copilot's documented connectors involve OAuth-style account sign-in to consumer services, not developer-controlled scoped credential issuance. missing for 10: any mention of API keys, scoped tokens, permission scoping, or credential management for agent access.

   ⚑ flag

6. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Claude—none0/10

   The evidence pack covers Claude's consumer/enterprise features (Cowork, Projects, connectors, MCP, Chrome extension, file handling) but contains no documentation of official language SDKs (e.g., Python/TypeScript client libraries) for building applications against the Claude API. Missing for 10: any first-party SDK docs, API reference, or code samples showing programmatic API usage.

   ⚑ flag

   Microsoft Copilot—none0/10

   The evidence pack covers Microsoft Copilot as a consumer AI assistant with features like connectors, browsing, and app integrations, but contains no mention of official SDKs, developer APIs, or programmatic build tooling for third-party developers; probes for API/OpenAPI specs returned 404s, further indicating no discoverable developer SDK surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/copilot.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

7. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Claude—none0/10

   No evidence pack item describes webhooks or event subscription mechanisms for Claude; the closest agentic integrations are MCP connectors and scheduled tasks, which are not webhook-based event subscriptions.

   ⚑ flag

   Microsoft Copilot—none0/10

   No evidence anywhere in the pack of Copilot offering webhook subscriptions or any event-driven notification API for developers; probes for API/OpenAPI specs returned 404s, and docs only describe chat/connector features, not webhook subscription mechanisms.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/copilot.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Claude
   Claude✓fullclaimed8/10

   Claude can ingest user data (files, connectors to Gmail/Drive/Calendar, Projects knowledge bases) and generate AI-driven insights, analysis, visualizations, and reports directly from that data, including agentic multi-step research that synthesizes findings with citations. This is well documented across file analysis, Research mode, Cowork task automation, and artifact/document generation features. Missing for 10: independent hands-on benchmarking specifically validating insight quality/accuracy from user data (community evidence is mixed/general rather than about this specific data-insight capability).

   • [claimed-docs] “Claude can work with the following document types: - PDF - DOCX - CSV - TXT - HTML - ODT - RTF - EPUB - JSON - XLSX”
   • [claimed-docs] “Prompt Claude using natural language to generate Excel spreadsheets, PowerPoint presentations, Word documents, and PDF files that you can do…”
   • [claimed-docs] “Projects allow you to create self-contained workspaces with their own chat histories and knowledge bases.”
   • [claimed-docs] “With research, Claude delivers thorough answers in minutes, complete with easy-to-check citations so you can trust Claude's findings.”
   • [claimed-docs] “Research transforms how Claude finds and analyzes information. Claude operates agentically, conducting multiple searches that build on each …”
   • [claimed-docs] “Claude operates agentically, conducting multiple searches that build on each other while determining exactly what to investigate next.”
   • [claimed-docs] “produce reports with charts and visualizations, and generate presentations from your documents—all without specialized software skills”
   • [claimed-docs] “Connect your Gmail, Google Calendar, and Google Drive to Claude so you can search and send emails, manage your calendar, work with documents…”
   • [claimed-docs] “Files can be uploaded to individual chats or uploaded to a project's Files section for persistent reference across conversations.”

   proof ↗⚑ flag

   Microsoft Copilot!disputedcontradicted5/10

   Microsoft heavily documents AI-generated insights across Word, Excel, PowerPoint, Outlook, Researcher, and Analyst, and describes proactive suggestions and code-run analysis (copilot-docs-2, copilot-docs-6, copilot-docs-16, copilot-docs-33, copilot-docs-31). However, hands-on community reports concretely contradict these claims for core products: a user found Copilot in Word 'couldn't do anything except append to the end of the document... couldn't create tables' (copilot-comm-4), and Outlook's summarization is described as 'so bad' with a tiny UI button (copilot-comm-5); others report never finding a use case (copilot-comm-9). One community report is positive about cross-document data fetching (copilot-comm-7), so evidence is genuinely mixed rather than uniformly negative. Missing for 10: independent benchmark of insight quality/accuracy, resolution of the Word/Outlook hands-on failures, and clearer distinction of chat vs. Office-integrated Copilot performance.

   • [claimed-docs] “Turn raw data into clear insights with Copilot in Excel.”
   • [claimed-docs] “Go from raw numbers to real insight—use Analyst to help analyze data with ease.”
   • [claimed-docs] “Turn raw data into clear insights with Copilot in Excel. Detail your task, attach data, and tweak via chat.”
   • [claimed-docs] “Copilot may proactively generate personalized research suggestions for users based on things like past research queries and Copilot memory.”
   • [claimed-docs] “Copilot can also run code to complete complex calculations and generate graphs.”
   • [community] “I subscribed for a trial month... Oh boy! It couldn't do anything except append to the end of the document. It couldn't create tables! It co…”
   • [community] “In MacOS Outlook they have a quarter inch sized bar in the main UI with just a button to summarize. It is so bad.”
   • [community] “the way it can fetch data from across documents in 365 is really good”
   • [community] “I use AI everyday and never found a use case for Copilot.”

   proof ↗⚑ flag

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

   weight 2 · round to Claude
   Claude✓fullclaimed8/10

   Claude Cowork's scheduled tasks let users describe a task once and have Claude execute it autonomously on a recurring or on-demand basis, delivering finished outputs like reports and briefings without further user input, which directly matches background automation. Missing for 10: independent/hands-on verification of scheduled task reliability and no detail on failure handling or notification mechanisms.

   • [claimed-docs] “Instead of starting each task from scratch, you describe it once and Claude handles it on your schedule—delivering finished outputs like rep…”
   • [claimed-docs] “Scheduled tasks allow you to delegate work to Claude Cowork by creating tasks that run automatically on a recurring basis, or on demand.”
   • [claimed-docs] “you describe it once and Claude handles it on your schedule—delivering finished outputs like reports, briefings, and summaries every time”
   • [claimed-docs] “With Cowork, you can describe an outcome, step away, and come back to finished work—formatted documents, organized files, synthesized resear…”
   • [claimed-docs] “Claude can take on complex, multi-step tasks and execute them on your behalf.”
   • [claimed-docs] “brings Claude Code's agentic capabilities to knowledge work beyond coding”

   proof ↗⚑ flag

   Microsoft Copilot~partialclaimed4/10

   Docs mention agentic-style capabilities (Cowork multi-step task completion, automating repetitive tasks, proactive research suggestions, browser action-taking) suggesting some autonomy, but Browse with Copilot explicitly requires user attention/supervision for many actions and no docs describe scheduled or fully background-running automations without a user session. Missing for 10: explicit scheduling/trigger mechanism, evidence of unattended background execution, and independent confirmation that these automations run without active supervision.

   • [claimed-docs] “With Cowork, Copilot can also help with bigger, multi-step tasks and deliver completed to-dos.”
   • [claimed-docs] “Hand off repetitive work so you can focus on what matters.”
   • [claimed-docs] “A copilot can automate repetitive tasks, no coding required.”
   • [claimed-docs] “Copilot may proactively generate personalized research suggestions for users based on things like past research queries and Copilot memory.”
   • [claimed-docs] “Copilot will ask for your attention and supervision for certain actions, such as buying an item, booking a reservation, sending an email, or…”

   proof ↗⚑ flag

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

   weight 3 · round to Claude
   Claude✓fullclaimed9/10

   Claude's built-in Cowork feature explicitly lets users delegate multi-step tasks ('describe an outcome, step away, come back to finished work'), with agentic execution including browser/computer use, scheduling, and research that autonomously plans next steps. This is well-documented first-party functionality directly matching task delegation to a built-in assistant. Missing for 10: independent hands-on verification of Cowork's delegation reliability (community evidence covers Claude Code/coding use more than Cowork specifically).

   • [claimed-docs] “With Cowork, you can describe an outcome, step away, and come back to finished work—formatted documents, organized files, synthesized resear…”
   • [claimed-docs] “Instead of starting each task from scratch, you describe it once and Claude handles it on your schedule—delivering finished outputs like rep…”
   • [claimed-docs] “Claude can take on complex, multi-step tasks and execute them on your behalf.”
   • [claimed-docs] “Scheduled tasks allow you to delegate work to Claude Cowork by creating tasks that run automatically on a recurring basis, or on demand.”
   • [claimed-docs] “brings Claude Code's agentic capabilities to knowledge work beyond coding”
   • [claimed-docs] “Research transforms how Claude finds and analyzes information. Claude operates agentically, conducting multiple searches that build on each …”
   • [claimed-docs] “Claude operates agentically, conducting multiple searches that build on each other while determining exactly what to investigate next.”

   proof ↗⚑ flag

   Microsoft Copilot~partialcommunity6/10

   Microsoft's own docs describe extensive delegation features—Copilot in Word/Excel/PowerPoint/Outlook, Researcher, Analyst, Browse with Copilot performing multi-step browser actions, and Cowork handling 'bigger, multi-step tasks'—clearly positioning Copilot as a built-in assistant that can take on tasks. However, hands-on community reports contradict smooth delegation in practice (e.g., Copilot in Word 'couldn't do anything except append to the end of the document,' couldn't create tables or maintain formatting, and some users report never finding a real use case), indicating real-world task execution is often shallow or unreliable. Missing for 10: independent verification of successful complex multi-step task completion, and resolution of documented editing/execution failures in flagship apps.

   • [claimed-docs] “Prompt Copilot with the task, add and upload notes, then refine in the chat—all with Copilot in Word.”
   • [claimed-docs] “Turn raw data into clear insights with Copilot in Excel.”
   • [claimed-docs] “Go from prompt to presentation with Copilot in PowerPoint. Outline the flow, describe visuals, and generate.”
   • [claimed-docs] “With Cowork, Copilot can also help with bigger, multi-step tasks and deliver completed to-dos.”
   • [claimed-docs] “Browse with Copilot lets Copilot perform actions directly in your Microsoft Edge browser, such as clicking, typing, and navigating tabs.”
   • [claimed-docs] “A copilot can automate repetitive tasks, no coding required.”
   • [community] “I subscribed for a trial month... Oh boy! It couldn't do anything except append to the end of the document. It couldn't create tables! It co…”
   • [community] “In MacOS Outlook they have a quarter inch sized bar in the main UI with just a button to summarize. It is so bad.”
   • [community] “I use AI everyday and never found a use case for Copilot.”

   proof ↗⚑ flag

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

   weight 2 · round to Claude
   Claude✓fullcommunity9/10

   Claude's entire interface is natural-language chat/voice, and documentation shows this extends to agentic actions—generating files, browsing/clicking the web, using the computer, scheduling recurring tasks, and building artifacts—all triggered by describing the desired outcome in plain language (claude-docs-4,6,7,15,37,38,54). Community evidence corroborates real-world agentic use (claude-comm-1,10,12), though some report friction with CLI usability. Missing for 10: independent benchmark of NL command reliability across all surfaces, and no rebuttal to the CLI unresponsiveness anecdote being addressed.

   • [claimed-docs] “With Cowork, you can describe an outcome, step away, and come back to finished work—formatted documents, organized files, synthesized resear…”
   • [claimed-docs] “Claude opens sites, reads pages, clicks, types, and fills forms while you watch, with no need to switch windows.”
   • [claimed-docs] “it may navigate to your screen directly—clicking, typing, and opening apps just like you would.”
   • [claimed-docs] “Prompt Claude using natural language to generate Excel spreadsheets, PowerPoint presentations, Word documents, and PDF files that you can do…”
   • [claimed-docs] “Claude can take on complex, multi-step tasks and execute them on your behalf.”
   • [claimed-docs] “Scheduled tasks allow you to delegate work to Claude Cowork by creating tasks that run automatically on a recurring basis, or on demand.”
   • [claimed-docs] “build tools, visualizations, and experiences by simply describing what you need”
   • [community] “I've been running Opus 4.8 for agentic coding and I don't see it being significantly better than Sonnet 4.5. I find that pairing Google Gemi…”
   • [community] “Anecdotal, but it 1 shot fixed a UI bug that neither Opus 4.5/Codex 5.2-high could fix.”
   • [community] “Claude is significantly better than other models at code assistant tasks, or at least in the way I use it.”

   proof ↗⚑ flag

   Microsoft Copilot!disputedcontradicted5/10

   Docs extensively describe natural-language operation—prompting Copilot in Word/Excel/PowerPoint, natural-language file/email/calendar search, and browser action commands (copilot-docs-1,2,3,8,14,20-22,26,27). However, hands-on community evidence directly contradicts this for at least one core surface: a user reports Copilot in Word 'couldn't do anything except append to the end of the document... couldn't create tables! couldn't search and replace! couldn't maintain formatting' (copilot-comm-4), and others found the Outlook summarize feature and overall NL assistant underwhelming or unused (copilot-comm-5, copilot-comm-9). This is a concrete documented failure of the claimed NL command capability, not mere skepticism. Missing for 10: independent third-party benchmarking of NL command reliability across all Office apps, and resolution of the reported Word functional gaps.

   • [claimed-docs] “Prompt Copilot with the task, add and upload notes, then refine in the chat—all with Copilot in Word.”
   • [claimed-docs] “Find my budget spreadsheet” or “Show me the project plan from last month.”
   • [claimed-docs] “Find files quickly: "Find my budget spreadsheet" or "Show me the project plan from last month."”
   • [claimed-docs] “Find Word documents about vacation plans” or “Show me all PDFs.”
   • [claimed-docs] “Find emails: “Show me emails from Sarah about the budget” or “Find my flight confirmation email.””
   • [community] “I subscribed for a trial month... Oh boy! It couldn't do anything except append to the end of the document. It couldn't create tables! It co…”
   • [community] “In MacOS Outlook they have a quarter inch sized bar in the main UI with just a button to summarize. It is so bad.”
   • [community] “I use AI everyday and never found a use case for Copilot.”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Claude—none0/10

   The evidence pack includes explicit probes checking for a machine-readable API spec (openapi.json, swagger.json, etc.) on Claude's support domain, all returning 404, and no docs item anywhere references an OpenAPI/Swagger spec or downloadable schema for the Claude API. Nothing in the docs list an API reference format for AI-native consumption.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.claude.com/openapi.json, https://support.claude.com/swagger.json, https://support.cl…”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.claude.com/en/.md”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   No evidence of a machine-readable API spec; explicit probes for OpenAPI/swagger endpoints all returned 404, and no docs mention a public API or spec for Microsoft Copilot as an end-user product.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/copilot.md”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Claude—none0/10

   The evidence pack covers Claude's consumer features, connectors, Cowork, and MCP integrations, but contains no mention of API versioning schemes or a documented deprecation policy for any Claude/Anthropic API. Since Claude does expose developer-facing APIs (e.g., for Console, Claude Code, MCP), this axis is applicable, but no evidence supports it.

   ⚑ flag

   Microsoft Copilot—none0/10

   Microsoft Copilot is presented here as a consumer-facing AI assistant product; there is no evidence of a public versioned API, developer API reference, or documented deprecation policy for it. Probes for API/OpenAPI specs and llms.txt all return 404, confirming absence of such developer-facing documentation.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/copilot.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

Agent mode

1. power-userDelegate a multi-step task that the assistant works on autonomously in the background and returns for my review

   weight 3 · round to Claude
   Claude✓fullclaimed8/10

   Claude Cowork is documented as letting users describe a multi-step outcome, step away, and return to finished work, with scheduled/recurring tasks and background agentic execution (browser/computer use, file generation) explicitly designed for delegation and later review. Missing for 10: independent hands-on validation of Cowork's reliability/quality for complex delegated tasks and clearer detail on review/approval workflow beyond docs.

   • [claimed-docs] “With Cowork, you can describe an outcome, step away, and come back to finished work—formatted documents, organized files, synthesized resear…”
   • [claimed-docs] “Instead of starting each task from scratch, you describe it once and Claude handles it on your schedule—delivering finished outputs like rep…”
   • [claimed-docs] “Claude can take on complex, multi-step tasks and execute them on your behalf.”
   • [claimed-docs] “Scheduled tasks allow you to delegate work to Claude Cowork by creating tasks that run automatically on a recurring basis, or on demand.”
   • [claimed-docs] “you describe it once and Claude handles it on your schedule—delivering finished outputs like reports, briefings, and summaries every time”
   • [claimed-docs] “This article explains how to use Claude Cowork, which brings Claude Code's agentic capabilities to knowledge work beyond coding.”
   • [claimed-docs] “Claude opens sites, reads pages, clicks, types, and fills forms while you watch, with no need to switch windows.”
   • [claimed-docs] “it may navigate to your screen directly—clicking, typing, and opening apps just like you would.”

   proof ↗⚑ flag

   Microsoft Copilot~partialclaimed5/10

   Copilot's 'Cowork' feature is explicitly described as handling 'bigger, multi-step tasks and deliver completed to-dos,' and 'Browse with Copilot' can perform multi-step actions while pausing for user approval on sensitive steps, which aligns with delegate-and-review workflows. However, these are single thin doc mentions with no independent/hands-on validation of true background/asynchronous operation, and community feedback focuses on other Copilot surfaces (Word, Outlook) being underwhelming rather than confirming Cowork's autonomous task delivery. Missing for 10: hands-on or independent evidence of a background task actually running unattended and returning a completed result, clearer scope/limits of Cowork, and confirmation this isn't just synchronous chat-assisted editing.

   • [claimed-docs] “With Cowork, Copilot can also help with bigger, multi-step tasks and deliver completed to-dos.”
   • [claimed-docs] “Browse with Copilot lets Copilot perform actions directly in your Microsoft Edge browser, such as clicking, typing, and navigating tabs.”
   • [claimed-docs] “You can see each step in real time and take control at any time. All actions run locally in your browser, ensuring full visibility and contr…”
   • [claimed-docs] “You can see each step in real time and take control at any time.”
   • [claimed-docs] “Copilot will ask for your attention and supervision for certain actions, such as buying an item, booking a reservation, sending an email, or…”

   proof ↗⚑ flag

2. power-userHave the assistant operate a web browser on my behalf to research and complete tasks on websites

   weight 3 · round to Claude
   Claude✓fullclaimed8/10

   Claude has multiple documented browser-control capabilities: the built-in browser in Cowork that opens sites, reads pages, clicks, types, and fills forms autonomously (claude-docs-6/67), the Claude in Chrome extension that reads/clicks/navigates websites (claude-docs-63), and computer-use navigation for on-screen actions (claude-docs-7/22/59), enabling research and task completion on websites. Missing for 10: independent hands-on validation of browser-task success rates and reliability under real-world site complexity.

   • [claimed-docs] “Claude opens sites, reads pages, clicks, types, and fills forms while you watch, with no need to switch windows.”
   • [claimed-docs] “Claude opens sites, reads pages, clicks, types, and fills forms while you watch, with no need to swit”
   • [claimed-docs] “Claude in Chrome is a browser extension that allows Claude to read, click, and navigate websites alongside you.”
   • [claimed-docs] “it may navigate to your screen directly—clicking, typing, and opening apps just like you would.”
   • [claimed-docs] “When computer use is enabled and Claude doesn't have a connector or tool for what you need, it may navigate to your screen directly—clicking…”
   • [claimed-docs] “it may navigate to your screen directly—clicking, typing, and opening apps just like you would”
   • [claimed-docs] “Claude can take on complex, multi-step tasks and execute them on your behalf.”

   proof ↗⚑ flag

   Microsoft Copilot~partialclaimed6/10

   Microsoft documents a dedicated 'Browse with Copilot' capability that lets Copilot click, type, and navigate tabs in Edge to complete web tasks, with real-time visibility and required user confirmation for sensitive actions like purchases or bookings, plus a 'Cowork' mode for multi-step task completion. However, all supporting evidence is first-party docs with no independent/hands-on confirmation of browser-operation success, and community feedback in the pack focuses on Office-integrated Copilot rather than this browsing agent feature. Missing for 10: independent/hands-on validation of the browse-and-complete-task capability, more detail on reliability/success rate on real websites.

   • [claimed-docs] “Browse with Copilot lets Copilot perform actions directly in your Microsoft Edge browser, such as clicking, typing, and navigating tabs.”
   • [claimed-docs] “You can see each step in real time and take control at any time. All actions run locally in your browser, ensuring full visibility and contr…”
   • [claimed-docs] “You can see each step in real time and take control at any time.”
   • [claimed-docs] “Copilot will ask for your attention and supervision for certain actions, such as buying an item, booking a reservation, sending an email, or…”
   • [claimed-docs] “With Cowork, Copilot can also help with bigger, multi-step tasks and deliver completed to-dos.”

   proof ↗⚑ flag

3. power-userLet the assistant see and operate applications on my computer to complete work

   weight 2 · round to Claude
   Claude✓fullclaimed8/10

   Claude Cowork/computer use lets Claude navigate directly to the user's screen—clicking, typing, opening apps, filling forms—while the user watches, plus a built-in browser for opening sites and interacting with pages, directly matching the story of operating applications to complete work. Community evidence corroborates agentic coding/task use though notes mixed quality perceptions unrelated to this specific capability. Missing for 10: independent hands-on verification of computer-use reliability/accuracy and broader third-party benchmarking beyond vendor docs.

   • [claimed-docs] “it may navigate to your screen directly—clicking, typing, and opening apps just like you would.”
   • [claimed-docs] “When computer use is enabled and Claude doesn't have a connector or tool for what you need, it may navigate to your screen directly—clicking…”
   • [claimed-docs] “it may navigate to your screen directly—clicking, typing, and opening apps just like you would”
   • [claimed-docs] “Claude opens sites, reads pages, clicks, types, and fills forms while you watch, with no need to switch windows.”
   • [claimed-docs] “Claude opens sites, reads pages, clicks, types, and fills forms while you watch, with no need to swit”
   • [claimed-docs] “With Cowork, you can describe an outcome, step away, and come back to finished work—formatted documents, organized files, synthesized resear…”
   • [claimed-docs] “Claude can take on complex, multi-step tasks and execute them on your behalf.”
   • [claimed-docs] “Claude in Chrome is a browser extension that allows Claude to read, click, and navigate websites alongside you.”

   proof ↗⚑ flag

   Microsoft Copilot~partialcommunity6/10

   Microsoft documents 'Browse with Copilot' letting the assistant click, type, and navigate tabs directly in Edge, plus 'Cowork' for multi-step task completion and Vision for seeing images/screens, with human-in-the-loop confirmation for sensitive actions. However, this operating capability is scoped mainly to the browser and Office apps rather than general desktop application control, and community reports describe weak real-world execution (e.g., Copilot in Word failing at basic edits, Outlook integration being minimal), undercutting the strength of the claim. Missing for 10: broad OS-level/desktop app automation beyond Edge/Office, and independent hands-on validation that agentic actions reliably complete tasks.

   • [claimed-docs] “Browse with Copilot lets Copilot perform actions directly in your Microsoft Edge browser, such as clicking, typing, and navigating tabs.”
   • [claimed-docs] “You can see each step in real time and take control at any time. All actions run locally in your browser, ensuring full visibility and contr…”
   • [claimed-docs] “With Cowork, Copilot can also help with bigger, multi-step tasks and deliver completed to-dos.”
   • [claimed-docs] “Copilot will ask for your attention and supervision for certain actions, such as buying an item, booking a reservation, sending an email, or…”
   • [community] “I subscribed for a trial month... Oh boy! It couldn't do anything except append to the end of the document. It couldn't create tables! It co…”
   • [community] “In MacOS Outlook they have a quarter inch sized bar in the main UI with just a button to summarize. It is so bad.”

   proof ↗⚑ flag

Tasks

1. power-userSchedule recurring or one-off tasks that run automatically and come back to me with results

   weight 2 · round to Claude
   Claude✓fullclaimed8/10

   Claude Cowork explicitly supports scheduled tasks that run on a recurring or one-off basis and deliver finished outputs like reports and summaries back to the user, matching the story closely. Missing for 10: independent/hands-on validation of scheduling reliability and no detail on notification/delivery mechanisms beyond docs.

   • [claimed-docs] “Scheduled tasks allow you to delegate work to Claude Cowork by creating tasks that run automatically on a recurring basis, or on demand.”
   • [claimed-docs] “you describe it once and Claude handles it on your schedule—delivering finished outputs like reports, briefings, and summaries every time”
   • [claimed-docs] “Instead of starting each task from scratch, you describe it once and Claude handles it on your schedule—delivering finished outputs like rep…”
   • [claimed-docs] “With Cowork, you can describe an outcome, step away, and come back to finished work—formatted documents, organized files, synthesized resear…”
   • [claimed-docs] “Claude can take on complex, multi-step tasks and execute them on your behalf.”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   The evidence shows Copilot can handle multi-step tasks (Cowork) and automate repetitive work, but there is no mention of scheduling recurring or one-off tasks that run automatically and return results later. Missing for 10: any documentation of a task-scheduling feature, recurrence settings, or proactive notification of completed scheduled runs.

   • [claimed-docs] “With Cowork, Copilot can also help with bigger, multi-step tasks and deliver completed to-dos.”
   • [claimed-docs] “Hand off repetitive work so you can focus on what matters.”
   • [claimed-docs] “A copilot can automate repetitive tasks, no coding required.”

   proof ↗⚑ flag

Apps

1. power-userUse an official desktop app with OS-level shortcuts and access to what is on my screen

   weight 2 · round to Claude
   Claude~partialclaimed5/10

   Claude ships an official desktop app (Mac, Windows, Linux via apt) and a Cowork/computer-use feature that lets Claude 'navigate to your screen directly—clicking, typing, and opening apps' while the user watches, which shows real screen access. However there is no evidence of dedicated OS-level keyboard shortcuts (e.g., a global hotkey to invoke Claude with current screen context) — the screen access described is agentic task automation rather than a power-user shortcut workflow. Missing for 10: documented OS-level global shortcuts/hotkeys, and evidence that a user can quickly summon Claude to see the current screen via keypress rather than launching a Cowork/computer-use task.

   • [claimed-docs] “you can install Claude Desktop from Anthropic's apt repository rather than as a downloaded .deb file so that updates arrive through your sys…”
   • [claimed-docs] “The Claude desktop apps bring Claude's capabilities directly to your computer, allowing for seamless integration with your workflow.”
   • [claimed-docs] “it may navigate to your screen directly—clicking, typing, and opening apps just like you would.”
   • [claimed-docs] “When computer use is enabled and Claude doesn't have a connector or tool for what you need, it may navigate to your screen directly—clicking…”
   • [claimed-docs] “it may navigate to your screen directly—clicking, typing, and opening apps just like you would”
   • [claimed-docs] “This article explains how to use Claude Cowork, which brings Claude Code's agentic capabilities to knowledge work beyond coding.”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   The evidence pack covers web/Office integrations, browser automation (Edge), and mobile/iOS/Android connectors, but nowhere documents an official standalone desktop app with OS-level keyboard shortcuts or the ability to see/interact with the user's screen content outside a browser. Vision (copilot-docs-30) is limited to photo/image analysis, not live screen capture, and Browse with Copilot (copilot-docs-9, -15, -24) is scoped to actions inside Microsoft Edge, not OS-wide screen access.

   • [claimed-docs] “Browse with Copilot lets Copilot perform actions directly in your Microsoft Edge browser, such as clicking, typing, and navigating tabs.”
   • [claimed-docs] “You can see each step in real time and take control at any time. All actions run locally in your browser, ensuring full visibility and contr…”
   • [claimed-docs] “You can see each step in real time and take control at any time.”
   • [claimed-docs] “See and understand. Use Vision to analyze images, get insights from photos, and search visually.”

   proof ↗⚑ flag

2. knowledge-workerUse full-featured official mobile apps for iOS and Android

   weight 2 · round to Claude
   Claude✓fullclaimed8/10

   Official iOS and Android apps are documented (App Store install instructions, Chrome/mobile chat parity across web/iOS/Android/desktop, voice mode explicitly available on Claude Mobile), indicating full-featured mobile apps rather than a bare wrapper. Missing for 10: no independent hands-on review of mobile app feature parity/quality, and no detail on which advanced features (Cowork, computer use) are available on mobile vs desktop-only.

   • [claimed-docs] “You can install the Claude app onto your iOS device by navigating to the App Store and searching for “Claude by Anthropic””
   • [claimed-docs] “You can install the Claude app onto your iOS device by navigating to the App Store and searching for "Claude by Anthropic"”
   • [claimed-docs] “Chat on web, iOS, Android, and on your desktop ... Memory across conversations”
   • [claimed-docs] “Chat on web, iOS, Android, and on your desktop”
   • [claimed-docs] “Voice mode is a beta feature available to all plans (Free, Pro, Max, Team, and Enterprise) on Claude Mobile (iOS and Android), Claude Deskto…”

   proof ↗⚑ flag

   Microsoft Copilot~partialclaimed6/10

   Docs explicitly confirm 'Copilot connectors are currently available on Copilot.com and on Copilot Mobile (iOS and Android)', establishing official iOS/Android apps exist and support core connector/chat features. However, there's no first-party or hands-on evidence detailing mobile-specific feature parity (e.g., Word/Excel/PowerPoint copilots, Vision, voice mode) on the mobile apps, and community feedback focuses only on desktop/Office integration quality, not mobile experience. Missing for 10: mobile-specific feature parity details, hands-on mobile app reviews, and confirmation of full functionality (Vision, Voice, connectors) actually working within the mobile app UI.

   • [claimed-docs] “Copilot connectors are currently available on Copilot.com and on Copilot Mobile (iOS and Android)”
   • [claimed-docs] “Copilot can connect with the following consumer services: * Microsoft OneDrive * Microsoft Outlook.com (email, calendar, and contacts) …”
   • [claimed-docs] “If users send prompts in natural language voice within the Copilot Voice mode, they will receive audio responses.”
   • [claimed-docs] “See and understand. Use Vision to analyze images, get insights from photos, and search visually.”

   proof ↗⚑ flag

Custom bots

1. power-userBuild and share custom assistants with their own instructions and knowledge

   weight 2 · round to Claude
   Claude~partialclaimed6/10

   Claude supports Projects (self-contained workspaces with custom knowledge bases/files) and Skills (teach Claude repeatable instructions like brand guidelines), which together let a power-user build a persona-like assistant with instructions and knowledge; Projects can be shared with team members. However, there's no dedicated 'custom GPT'-style public sharing/marketplace for assistants, and no independent evidence of end-to-end sharing outside an org. missing for 10: evidence of public/marketplace sharing of custom assistants, explicit persona/system-instruction configuration UI, and independent hands-on confirmation of building and sharing such assistants.

   • [claimed-docs] “Projects allow you to create self-contained workspaces with their own chat histories and knowledge bases.”
   • [claimed-docs] “whether that's creating documents with your company's brand guidelines, analyzing data using your organization's specific workflows”
   • [claimed-docs] “Skills teach Claude how to complete specific tasks in a repeatable way, whether that's creating documents with your company's brand guidelin…”
   • [claimed-docs] “Files can be uploaded to individual chats or uploaded to a project's Files section for persistent reference across conversations.”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   No evidence describes creating custom Copilot agents/assistants with custom instructions and knowledge base (like Copilot Studio agents or GPT-builder equivalents) nor sharing them with others; evidence only covers built-in Office integrations, connectors, and memory features. Missing for 10: any mention of an agent/assistant builder, custom instructions, custom knowledge upload, and sharing/publishing mechanism for user-built assistants.

   ⚑ flag

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

   weight 2 · round to Microsoft Copilot
   Claude—none0/10

   The evidence pack documents agentic task automation (Cowork, scheduled tasks, Research) and single-document file handling, but no feature is described for processing or acting on many items at once (e.g., batch file processing, bulk edit across records, or a batch API). Automation-depth stories like this are plausible for Claude given its agentic tooling, but nothing in the pack shows bulk/multi-item operation support.

   ⚑ flag

   Microsoft Copilot~partialcommunity3/10

   Docs mention general automation of 'repetitive tasks' and multi-step task completion via Cowork, but there's no concrete evidence of bulk operations across many items (e.g., batch-editing many files, mass email actions, or large-scale spreadsheet manipulation). Community feedback (copilot-comm-4) reports Copilot in Word failing at basic single-document tasks like search-and-replace, casting doubt on any claim of robust bulk-item processing. missing for 10: explicit bulk/batch operation examples (e.g., mass-processing many files/rows/emails at once), independent hands-on evidence of successful bulk actions, and confirmation that Cowork or Analyst can operate at scale across many items reliably.

   • [claimed-docs] “With Cowork, Copilot can also help with bigger, multi-step tasks and deliver completed to-dos.”
   • [claimed-docs] “Hand off repetitive work so you can focus on what matters.”
   • [claimed-docs] “A copilot can automate repetitive tasks, no coding required.”
   • [community] “I subscribed for a trial month... Oh boy! It couldn't do anything except append to the end of the document. It couldn't create tables! It co…”

   proof ↗⚑ flag

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

   weight 3 · round to Claude
   Claude~partialclaimed4/10

   Claude Cowork supports scheduled/recurring tasks that run automatically on a time-based schedule or on demand (claude-docs-38, claude-docs-58), which is a form of automation, but there's no evidence of user-defined rules triggered by external events (e.g., 'when an email arrives' or 'when a file changes, do X') as opposed to calendar/time-based scheduling. missing for 10: event-driven trigger conditions (webhooks, connector-based event listeners), a rules engine for conditional automation, and any documentation of non-time-based triggers.

   • [claimed-docs] “Scheduled tasks allow you to delegate work to Claude Cowork by creating tasks that run automatically on a recurring basis, or on demand.”
   • [claimed-docs] “you describe it once and Claude handles it on your schedule—delivering finished outputs like reports, briefings, and summaries every time”
   • [claimed-docs] “Instead of starting each task from scratch, you describe it once and Claude handles it on your schedule—delivering finished outputs like rep…”
   • [claimed-docs] “Claude can take on complex, multi-step tasks and execute them on your behalf.”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   The evidence describes Copilot responding to prompts, browsing, summarizing, and connecting to services, but there is no mention of user-defined rules or triggers that fire actions automatically on events (e.g., 'when email arrives, do X' style automation). No scheduling, event-trigger, or workflow-builder capability is documented.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Claude
   Claude✓fullclaimed8/10

   Claude Cowork explicitly supports scheduled recurring tasks, letting users describe a workflow once and have Claude execute it automatically on a recurring or on-demand basis, delivering outputs like reports and briefings — this directly matches the story. Missing for 10: independent/hands-on verification of scheduling reliability and details on scheduling granularity/limits beyond vendor docs.

   • [claimed-docs] “Instead of starting each task from scratch, you describe it once and Claude handles it on your schedule—delivering finished outputs like rep…”
   • [claimed-docs] “Scheduled tasks allow you to delegate work to Claude Cowork by creating tasks that run automatically on a recurring basis, or on demand.”
   • [claimed-docs] “you describe it once and Claude handles it on your schedule—delivering finished outputs like reports, briefings, and summaries every time”
   • [claimed-docs] “With Cowork, you can describe an outcome, step away, and come back to finished work—formatted documents, organized files, synthesized resear…”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   No evidence describes scheduling recurring jobs, timers, or automated recurring workflows in Microsoft Copilot; the pack shows one-off task automation (Cowork, connectors, browse actions) but nothing about recurrence or scheduling.

   ⚑ flag

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

   weight 1 · round drawn
   Claude—none0/10

   No evidence describes versioning, reviewing, or rolling back automations like scheduled Cowork tasks or Skills; docs cover creating/scheduling tasks but not history, diffs, or rollback capability.

   ⚑ flag

   Microsoft Copilot—none0/10

   No evidence describes any versioning, history, review workflow, or rollback capability for Copilot's automations (e.g., Cowork, connectors, or agent tasks); evidence only covers connecting services, browsing, memory, and privacy controls. Missing for 10: version history UI, diff/review of automation changes, rollback/undo mechanism, any audit trail for automation edits.

   ⚑ flag

Connectors

1. power-userBrowse a directory of third-party apps and connectors and add them to the assistant

   weight 2 · round to Claude
   Claude✓fullclaimed9/10

   Claude documents a unified directory that brings skills, connectors, and plugins together in one place to find and install everything that customizes Claude, plus specific connectors like Google Workspace and remote/local MCP servers to extend the assistant. Missing for 10: no independent hands-on review confirming the browsing/discovery UX of the directory itself.

   • [claimed-docs] “Our unified directory brings skills, connectors, and plugins together in one place so you can find and install everything that customizes Cl…”
   • [claimed-docs] “Our unified directory brings skills, connectors, and plugins together in one place so you can find and install everything that customizes Cl…”
   • [claimed-docs] “Connect your Gmail, Google Calendar, and Google Drive to Claude so you can search and send emails, manage your calendar, work with documents…”
   • [claimed-docs] “Connect your Gmail, Google Calendar, and Google Drive to Claude so you can search and send emails, manage your calendar, work with documents…”
   • [claimed-docs] “installing and managing local MCP servers has become significantly easier... install local MCP servers on your computer as easily as browser…”
   • [claimed-docs] “you can now install local MCP servers on your computer as easily as browser extensions”
   • [claimed-docs] “You can: Connect Claude to existing remote MCP servers. Build your own remote MCP servers to connect with any tool.”

   proof ↗⚑ flag

   Microsoft Copilot~partialclaimed4/10

   Docs confirm Copilot supports 'connectors' to a small fixed list of services (OneDrive, Outlook.com, Google Drive, Gmail/Calendar/Contacts) and note these are available on Copilot.com/Mobile, but there is no evidence of a browsable directory/marketplace of third-party apps that power-users can explore and add beyond this short built-in list. missing for 10: evidence of a searchable app/connector marketplace, breadth of third-party (non-Microsoft/Google) integrations, and any independent confirmation of the browsing/add experience.

   • [claimed-docs] “Copilot can connect with the following consumer services: * Microsoft OneDrive * Microsoft Outlook.com (email, calendar, and contacts) …”
   • [claimed-docs] “Copilot can connect with the following consumer services: Microsoft OneDrive, Microsoft Outlook.com (email, calendar, and contacts), Google …”
   • [claimed-docs] “Copilot connectors are currently available on Copilot.com and on Copilot Mobile (iOS and Android)”
   • [claimed-docs] “Copilot can connect with the following consumer services: ... Google Drive ... Google Gmail, Calendar, Contacts”
   • [claimed-docs] “Copilot can connect with the following consumer services: Microsoft OneDrive... Google Drive... Google Gmail, Calendar, Contacts”

   proof ↗⚑ flag

2. knowledge-workerConnect my cloud drive, email, and calendar so the assistant can search and use them in answers

   weight 3 · round to Claude
   Claude✓fullclaimed9/10

   Claude has a documented Google Workspace connector letting users connect Gmail, Google Calendar, and Google Drive so Claude can search emails, manage calendar, and work with documents/files directly in conversation, plus a privacy commitment not to train on this data. This directly satisfies the story's cloud drive/email/calendar connection use case. Missing for 10: no independent hands-on report corroborating real-world reliability of these specific connectors.

   • [claimed-docs] “Connect your Gmail, Google Calendar, and Google Drive to Claude so you can search and send emails, manage your calendar, work with documents…”
   • [claimed-docs] “Connect your Gmail, Google Calendar, and Google Drive to Claude so you can search and send emails, manage your calendar, work with documents…”
   • [claimed-docs] “We do not train our models on your Gmail, Drive, or Calendar connector data, ensuring your private information remains private.”
   • [claimed-docs] “Our unified directory brings skills, connectors, and plugins together in one place so you can find and install everything that customizes Cl…”

   proof ↗⚑ flag

   Microsoft Copilot✓fullcommunity8/10

   Microsoft's documentation explicitly describes connecting Copilot to OneDrive, Outlook.com (email/calendar/contacts), Google Drive, and Google Gmail/Calendar/Contacts, with example queries for finding files, emails, and calendar events, indicating the assistant can search and use this data in answers. Community evidence corroborates that cross-document/data fetching works well in some contexts, though other complaints focus on unrelated feature quality issues (e.g., editing limitations) rather than disputing the connector capability itself. Missing for 10: independent hands-on verification specifically of the cloud-drive/email/calendar connector search feature (rather than in-app Office Copilot) and more detail on reliability/completeness of search results.

   • [claimed-docs] “Copilot can connect with the following consumer services: * Microsoft OneDrive * Microsoft Outlook.com (email, calendar, and contacts) …”
   • [claimed-docs] “Find my budget spreadsheet” or “Show me the project plan from last month.”
   • [claimed-docs] “Copilot can connect with the following consumer services: Microsoft OneDrive, Microsoft Outlook.com (email, calendar, and contacts), Google …”
   • [claimed-docs] “Find files quickly: "Find my budget spreadsheet" or "Show me the project plan from last month."”
   • [claimed-docs] “Find Word documents about vacation plans” or “Show me all PDFs.”
   • [claimed-docs] “Show me emails from Sarah about the budget” or “Find my flight confirmation email.”
   • [claimed-docs] “What's on my calendar for tomorrow?” or “When is my next dentist appointment?”
   • [claimed-docs] “Find emails: “Show me emails from Sarah about the budget” or “Find my flight confirmation email.””
   • [claimed-docs] “Check in on your calendar: “What’s on my calendar for tomorrow?” or “When is my next dentist appointment?””
   • [claimed-docs] “Copilot connectors are currently available on Copilot.com and on Copilot Mobile (iOS and Android)”
   • [community] “the way it can fetch data from across documents in 365 is really good”

   proof ↗⚑ flag

Analysis

1. power-userHave the assistant write and run code on my data to produce charts, computed answers, and downloadable files

   weight 3 · round to Claude
   Claude✓fullclaimed8/10

   Docs explicitly describe generating downloadable Excel/PowerPoint/Word/PDF files, producing reports with charts and visualizations, and using artifacts to build code-driven visualizations and interactive components from uploaded data files (CSV, XLSX, etc.). This directly matches the power-user story of writing/running code on data to produce charts, computed answers, and downloadable outputs. missing for 10: independent/hands-on community corroboration specifically validating the data-analysis/code-execution-to-chart workflow (community evidence in the pack focuses on coding agent quality, not this analysis feature).

   • [claimed-docs] “Prompt Claude using natural language to generate Excel spreadsheets, PowerPoint presentations, Word documents, and PDF files that you can do…”
   • [claimed-docs] “produce reports with charts and visualizations, and generate presentations from your documents—all without specialized software skills”
   • [claimed-docs] “Generate code and visualize data”
   • [claimed-docs] “Claude can work with the following document types: - PDF - DOCX - CSV - TXT - HTML - ODT - RTF - EPUB - JSON - XLSX”
   • [claimed-docs] “Claude can work with the following document types: PDF DOCX CSV TXT HTML ODT RTF EPUB JSON XLSX”
   • [claimed-docs] “Common examples of artifact content include: Documents (Markdown or plain text) - Code snippets ... Interactive React components”
   • [claimed-docs] “Common examples of artifact content include: - Documents (Markdown or plain text) - Code snippets - Single-page HTML websites - SVG images -…”
   • [claimed-docs] “Artifacts allow you to turn ideas into shareable apps, tools, or content—build tools, visualizations, and experiences by simply describing w…”
   • [claimed-docs] “build tools, visualizations, and experiences by simply describing what you need”
   • [claimed-docs] “Files can be uploaded to individual chats or uploaded to a project's Files section for persistent reference across conversations.”

   proof ↗⚑ flag

   Microsoft Copilot~partialclaimed6/10

   Docs explicitly state Copilot can 'run code to complete complex calculations and generate graphs' and the 'Analyst' feature 'analyzes data with ease,' plus Excel/Word integrations for working with attached data—covering charts and computed answers. However, there is no explicit documentation of producing downloadable files as an output of this code-execution flow, and no hands-on/community evidence corroborates this specific capability working well (community comments focus on other Office Copilot shortcomings, not code-execution). Missing for 10: explicit downloadable-file output evidence, independent/hands-on confirmation of the code-execution feature itself.

   • [claimed-docs] “Copilot can also run code to complete complex calculations and generate graphs.”
   • [claimed-docs] “Go from raw numbers to real insight—use Analyst to help analyze data with ease.”
   • [claimed-docs] “Turn raw data into clear insights with Copilot in Excel. Detail your task, attach data, and tweak via chat.”
   • [claimed-docs] “Turn raw data into clear insights with Copilot in Excel.”

   proof ↗⚑ flag

Artifacts

1. knowledge-workerHave the assistant create and iteratively edit documents, presentations, and other files I can export

   weight 2 · round to Claude
   Claude✓fullclaimed9/10

   Docs explicitly describe generating and editing Excel, PowerPoint, Word, and PDF files via natural-language prompts, plus Artifacts for documents/code/interactive content that can be iteratively refined and downloaded, and uploading/persisting files in Projects for ongoing editing. Missing for 10: independent hands-on review confirming export fidelity/iteration quality across file types.

   • [claimed-docs] “Prompt Claude using natural language to generate Excel spreadsheets, PowerPoint presentations, Word documents, and PDF files that you can do…”
   • [claimed-docs] “produce reports with charts and visualizations, and generate presentations from your documents—all without specialized software skills”
   • [claimed-docs] “Common examples of artifact content include: Documents (Markdown or plain text) - Code snippets ... Interactive React components”
   • [claimed-docs] “Common examples of artifact content include: - Documents (Markdown or plain text) - Code snippets - Single-page HTML websites - SVG images -…”
   • [claimed-docs] “Files can be uploaded to individual chats or uploaded to a project's Files section for persistent reference across conversations.”
   • [claimed-docs] “Claude can work with the following document types: - PDF - DOCX - CSV - TXT - HTML - ODT - RTF - EPUB - JSON - XLSX”

   proof ↗⚑ flag

   Microsoft Copilot!disputedcontradicted4/10

   Microsoft's own docs claim Copilot in Word/Excel/PowerPoint can create and iteratively refine documents, spreadsheets, and presentations via chat (copilot-docs-1,2,3,16), which would let users export finished files. However, a hands-on community report directly contradicts this for Word, stating Copilot 'couldn't do anything except append to the end of the document,' couldn't create tables, search/replace, or maintain formatting (copilot-comm-4), and another user calls Outlook's summarize feature 'so bad' (copilot-comm-5). This is a concrete documented capability failure, not mere skepticism. Missing for 10: independent corroboration of successful iterative multi-turn editing, PowerPoint/Excel hands-on validation, and confirmation of clean export/formatting fidelity.

   • [claimed-docs] “Prompt Copilot with the task, add and upload notes, then refine in the chat—all with Copilot in Word.”
   • [claimed-docs] “Turn raw data into clear insights with Copilot in Excel.”
   • [claimed-docs] “Go from prompt to presentation with Copilot in PowerPoint. Outline the flow, describe visuals, and generate.”
   • [claimed-docs] “Turn raw data into clear insights with Copilot in Excel. Detail your task, attach data, and tweak via chat.”
   • [community] “I subscribed for a trial month... Oh boy! It couldn't do anything except append to the end of the document. It couldn't create tables! It co…”
   • [community] “In MacOS Outlook they have a quarter inch sized bar in the main UI with just a button to summarize. It is so bad.”

   proof ↗⚑ flag

Files

1. knowledge-workerUpload documents, spreadsheets, and PDFs and get accurate analysis of their contents

   weight 3 · round to Claude
   Claude✓fullclaimed9/10

   Docs confirm Claude supports uploading PDFs, DOCX, CSV, XLSX, TXT, HTML, ODT, RTF, EPUB, JSON, with analysis of both text and visual elements in PDFs up to 100 pages, plus persistent Project file storage for cross-conversation reference and generation of derived documents/reports. Missing for 10: independent hands-on benchmarking of analysis accuracy across large/complex spreadsheets or long PDFs beyond the 100-page limit.

   • [claimed-docs] “Claude can work with the following document types: - PDF - DOCX - CSV - TXT - HTML - ODT - RTF - EPUB - JSON - XLSX”
   • [claimed-docs] “Claude can work with the following document types: PDF DOCX CSV TXT HTML ODT RTF EPUB JSON XLSX”
   • [claimed-docs] “Claude analyzes both text and visual elements (like images, charts, and graphics) in PDFs of 100 pages or fewer”
   • [claimed-docs] “Files can be uploaded to individual chats or uploaded to a project's Files section for persistent reference across conversations.”
   • [claimed-docs] “Prompt Claude using natural language to generate Excel spreadsheets, PowerPoint presentations, Word documents, and PDF files that you can do…”
   • [claimed-docs] “produce reports with charts and visualizations, and generate presentations from your documents—all without specialized software skills”

   proof ↗⚑ flag

   Microsoft Copilot~partialcommunity6/10

   Microsoft's own docs describe multiple file-analysis capabilities—attaching data in Excel, analyzing notes in Word, finding/searching PDFs and Office documents, an 'Analyst' tool for data insight, and code execution for calculations—giving broad first-party coverage of the story. However, hands-on community reports contradict smooth real-world usability (e.g. Word Copilot 'couldn't do anything except append text... couldn't maintain formatting' and Outlook summarization deemed 'so bad'), while another user praises cross-document data-fetching, so the accuracy/quality of analysis is mixed rather than assured. Missing for 10: independent verification of analysis accuracy on complex spreadsheets/PDFs, and resolution of the documented Word-editing/formatting failures.

   • [claimed-docs] “Prompt Copilot with the task, add and upload notes, then refine in the chat—all with Copilot in Word.”
   • [claimed-docs] “Turn raw data into clear insights with Copilot in Excel.”
   • [claimed-docs] “Go from raw numbers to real insight—use Analyst to help analyze data with ease.”
   • [claimed-docs] “Turn raw data into clear insights with Copilot in Excel. Detail your task, attach data, and tweak via chat.”
   • [claimed-docs] “Find Word documents about vacation plans” or “Show me all PDFs.”
   • [claimed-docs] “Copilot can also run code to complete complex calculations and generate graphs.”
   • [community] “I subscribed for a trial month... Oh boy! It couldn't do anything except append to the end of the document. It couldn't create tables! It co…”
   • [community] “the way it can fetch data from across documents in 365 is really good”

   proof ↗⚑ flag

Memory

1. power-userHave the assistant remember relevant context from previous chats and apply it in new conversations

   weight 3 · round to Claude
   Claude✓fullclaimed8/10

   Claude has explicit first-party memory/chat-search docs: it can search previous conversations and "remember context from your chats and carry it into new conversations and Cowork tasks," plus a dedicated article on how memory works, what's remembered, and how to review/edit it; the product page also advertises "Memory across conversations" as a core feature. This directly matches the story of remembering context across chats and applying it in new ones. Missing for 10: independent/hands-on corroboration of memory quality or limitations in practice beyond vendor docs.

   • [claimed-docs] “You can prompt Claude to search through your previous conversations to find and reference relevant information in new chats.”
   • [claimed-docs] “Chat on web, iOS, Android, and on your desktop ... Memory across conversations”
   • [claimed-docs] “This article explains how chat search and memory work, what Claude does and doesn’t remember, how to review and edit what’s saved, and how t…”
   • [claimed-docs] “Claude can also remember context from your chats and carry it into new conversations and Cowork tasks.”

   proof ↗⚑ flag

   Microsoft Copilot~partialclaimed6/10

   First-party docs confirm a memory feature: Copilot can store facts users ask it to remember and use that context in future responses, and can proactively surface suggestions based on past queries and memory (copilot-docs-32, copilot-docs-33). However, this is opt-in/explicit fact storage rather than full automatic context carry-over, and there is no independent/hands-on evidence confirming it works reliably across conversations. missing for 10: independent verification of cross-conversation recall, detail on scope/limits of automatic memory use, and confirmation it isn't just facts explicitly asked to be remembered.

   • [claimed-docs] “Copilot can store specific facts users request it to remember, allowing it to generate more relevant responses and suggestions based on that…”
   • [claimed-docs] “Copilot may proactively generate personalized research suggestions for users based on things like past research queries and Copilot memory.”
   • [claimed-docs] “you can delete individual conversations or your entire conversation history at any time”

   proof ↗⚑ flag

2. power-userSet persistent custom instructions and preferences that shape every response

   weight 1 · round to Claude
   Claude~partialclaimed6/10

   Claude supports persistent memory/context (chat search and memory, Projects with knowledge bases, custom instructions implied via Skills and Projects) that carries into new conversations, but there is no explicit documented feature for setting global 'custom instructions' that shape every response the way ChatGPT's system prompt does. missing for 10: dedicated persistent custom-instructions/preferences UI applying to all chats, independent/hands-on verification that memory reliably shapes every response, and clarity on scope/limits of what's remembered.

   • [claimed-docs] “You can prompt Claude to search through your previous conversations to find and reference relevant information in new chats.”
   • [claimed-docs] “This article explains how chat search and memory work, what Claude does and doesn’t remember, how to review and edit what’s saved, and how t…”
   • [claimed-docs] “Claude can also remember context from your chats and carry it into new conversations and Cowork tasks.”
   • [claimed-docs] “Projects allow you to create self-contained workspaces with their own chat histories and knowledge bases.”
   • [claimed-docs] “Skills teach Claude how to complete specific tasks in a repeatable way, whether that's creating documents with your company's brand guidelin…”

   proof ↗⚑ flag

   Microsoft Copilot~partialclaimed5/10

   Docs confirm a memory feature where Copilot can store facts users ask it to remember and use them to personalize future responses and suggestions, plus controls to view/delete memory (copilot-docs-32, copilot-docs-33, copilot-docs-38). However there is no dedicated 'custom instructions' setting described (unlike explicit persona/tone controls), and no independent/hands-on evidence confirming these stored facts consistently shape *every* response. Missing for 10: explicit custom-instructions UI documentation, hands-on confirmation that memory reliably influences all responses, and community corroboration of the feature's effectiveness.

   • [claimed-docs] “Copilot can store specific facts users request it to remember, allowing it to generate more relevant responses and suggestions based on that…”
   • [claimed-docs] “Copilot may proactively generate personalized research suggestions for users based on things like past research queries and Copilot memory.”
   • [claimed-docs] “you can delete individual conversations or your entire conversation history at any time”
   • [claimed-docs] “opt out of use of your conversation activity for model training”

   proof ↗⚑ flag

Projects

1. knowledge-workerOrganize related chats and files into a project or space that shares context and instructions

   weight 2 · round to Claude
   Claude✓fullclaimed8/10

   Projects docs confirm self-contained workspaces with shared chat histories and knowledge bases, persistent file uploads scoped to a project for cross-conversation reference, and memory/chat search to build on prior context. missing for 10: no evidence of custom instructions/system prompt configuration per project beyond files, and no independent/hands-on corroboration of the project workflow in practice.

   • [claimed-docs] “Projects allow you to create self-contained workspaces with their own chat histories and knowledge bases.”
   • [claimed-docs] “Files can be uploaded to individual chats or uploaded to a project's Files section for persistent reference across conversations.”
   • [claimed-docs] “This article explains how chat search and memory work, what Claude does and doesn’t remember, how to review and edit what’s saved, and how t…”
   • [claimed-docs] “Chat on web, iOS, Android, and on your desktop ... Memory across conversations”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   The evidence pack shows Copilot memory (storing facts), connectors to files/email/calendar, and per-app integrations, but nowhere describes a 'project' or 'space' concept that lets a user group related chats and files together with shared instructions/context, unlike competitors' project/space features. Community feedback focuses on integration quality issues, not on organizational/workspace features. Missing for 10: any documented 'project', 'space', 'workspace', or chat-grouping feature with shared custom instructions and file scoping.

   • [claimed-docs] “Copilot can store specific facts users request it to remember, allowing it to generate more relevant responses and suggestions based on that…”
   • [claimed-docs] “Copilot may proactively generate personalized research suggestions for users based on things like past research queries and Copilot memory.”
   • [claimed-docs] “Copilot can connect with the following consumer services: * Microsoft OneDrive * Microsoft Outlook.com (email, calendar, and contacts) …”

   proof ↗⚑ flag

Images

1. knowledge-workerGenerate and edit images from natural-language prompts

   weight 2 · round to Claude
   Claude~partialclaimed4/10

   Claude can understand and analyze uploaded/pasted images (JPEG, PNG, GIF, WebP) and can produce SVG images, diagrams, and flowcharts as artifacts from natural-language descriptions, but there is no evidence of true raster image generation or photo-editing capability comparable to dedicated image models. Editing of generated visual artifacts is possible via iterative prompting, but this is limited to code-rendered graphics rather than general image generation/editing. Missing for 10: dedicated raster image-generation model, photo editing/inpainting features, and any independent confirmation of image-generation quality.

   • [claimed-docs] “Common examples of artifact content include: - Documents (Markdown or plain text) - Code snippets - Single-page HTML websites - SVG images -…”
   • [claimed-docs] “Claude analyzes both text and visual elements (like images, charts, and graphics) in PDFs of 100 pages or fewer”
   • [claimed-docs] “Claude supports the following image formats: - JPEG - PNG - GIF - WebP”
   • [claimed-docs] “You can also copy images and paste them from your clipboard into Claude”
   • [claimed-docs] “build tools, visualizations, and experiences by simply describing what you need”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   The evidence pack only shows Copilot's 'Vision' feature for analyzing and understanding images (copilot-docs-30), not generating or editing images from text prompts; no docs, community, or probe evidence mentions an image-generation or image-editing capability (e.g., a Designer/DALL·E-style feature).

   • [claimed-docs] “See and understand. Use Vision to analyze images, get insights from photos, and search visually.”

   proof ↗⚑ flag

2. knowledge-workerShare screenshots and photos and have the assistant accurately interpret what is in them

   weight 2 · round to Claude
   Claude✓fullclaimed7/10

   Claude's docs confirm native image upload/paste support (JPEG, PNG, GIF, WebP) and clipboard paste, plus PDF analysis that includes visual elements like images and charts, directly supporting screenshot/photo interpretation for knowledge workers. Missing for 10: independent/hands-on evidence validating accuracy of image interpretation, and no explicit mention of screenshot-specific use cases (e.g., UI screenshots, photos of documents) beyond general image/PDF support.

   • [claimed-docs] “Claude analyzes both text and visual elements (like images, charts, and graphics) in PDFs of 100 pages or fewer”
   • [claimed-docs] “Claude supports the following image formats: - JPEG - PNG - GIF - WebP”
   • [claimed-docs] “You can also copy images and paste them from your clipboard into Claude”
   • [claimed-docs] “Claude can work with the following document types: - PDF - DOCX - CSV - TXT - HTML - ODT - RTF - EPUB - JSON - XLSX”

   proof ↗⚑ flag

   Microsoft Copilot~partialclaimed5/10

   Docs confirm Copilot has a 'Vision' capability to analyze images and photos ([copilot-docs-30]), directly supporting the story, but this is a single first-party mention with no elaboration on screenshot-specific use cases or accuracy, and no independent/hands-on evidence corroborates real-world interpretation quality. Missing for 10: detailed documentation on screenshot vs photo handling, accuracy benchmarks, and independent/community verification of correct image interpretation.

   • [claimed-docs] “See and understand. Use Vision to analyze images, get insights from photos, and search visually.”

   proof ↗⚑ flag

Voice

1. knowledge-workerHave a natural, real-time voice conversation with the assistant

   weight 2 · round to Claude
   Claude✓fullclaimed8/10

   Claude ships an explicit Voice mode enabling complete spoken conversations, available across web, desktop, iOS and Android, positioned to work best on phone. Missing for 10: independent hands-on reviews of voice latency/naturalness and confirmation it's out of beta.

   • [claimed-docs] “Voice mode allows you to have complete spoken conversations with Claude.”
   • [claimed-docs] “Voice mode is a beta feature available to all plans (Free, Pro, Max, Team, and Enterprise) on Claude Mobile (iOS and Android), Claude Deskto…”

   proof ↗⚑ flag

   Microsoft Copilot✓fullclaimed6/10

   Microsoft's transparency docs explicitly describe Copilot Voice mode: users send natural-language voice prompts and receive audio responses, with citations shown in conversation transcripts, confirming real-time spoken interaction. Missing for 10: independent/hands-on corroboration of voice mode's real-time quality, latency, or interruption handling, and no community evidence specifically validates or disputes the voice experience.

   • [claimed-docs] “If users send prompts in natural language voice within the Copilot Voice mode, they will receive audio responses.”
   • [claimed-docs] “This means that Copilot centers its response on high-ranking content from the web and provides hyperlinked citations following generated tex…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Claude—none0/10

   The evidence pack details many UI-exclusive Claude.ai features (Cowork, voice mode, computer use, memory/chat search, artifacts, browser extension, scheduled tasks) but contains no documentation that these capabilities are exposed through the Claude API, nor any statement of API/UI feature parity. Enterprise API mentions are limited to a Compliance API for logs, not general feature parity.

   • [claimed-docs] “With Cowork, you can describe an outcome, step away, and come back to finished work—formatted documents, organized files, synthesized resear…”
   • [claimed-docs] “Voice mode allows you to have complete spoken conversations with Claude.”
   • [claimed-docs] “Claude opens sites, reads pages, clicks, types, and fills forms while you watch, with no need to switch windows.”
   • [claimed-docs] “it may navigate to your screen directly—clicking, typing, and opening apps just like you would.”
   • [claimed-docs] “Audit logs: capture key information about user actions, system events, and data access. ... Compliance API: programmatically access Claude u…”
   • [claimed-docs] “Projects allow you to create self-contained workspaces with their own chat histories and knowledge bases.”
   • [claimed-docs] “This article explains how chat search and memory work, what Claude does and doesn’t remember, how to review and edit what’s saved, and how t…”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   No evidence of a public API exposing Copilot's UI capabilities (chat, connectors, Word/Excel/PowerPoint copilots) programmatically; probes for OpenAPI/docs endpoints returned 404s, and all evidence describes UI/chat-only functionality. Missing for 10: any documented API/SDK, endpoint parity documentation, or third-party confirmation of programmatic access to Copilot features.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/copilot.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”
   • [claimed-docs] “Prompt Copilot with the task, add and upload notes, then refine in the chat—all with Copilot in Word.”
   • [claimed-docs] “Browse with Copilot lets Copilot perform actions directly in your Microsoft Edge browser, such as clicking, typing, and navigating tabs.”

   proof ↗⚑ flag

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

   weight 3 · round to Claude
   Claude~partialclaimed6/10

   Claude documents a data-export feature covering conversation and account data, letting users take their data with them ([claude-docs-12], [claude-docs-40]). However, there is no evidence specifying the export format is an open/standard one (e.g., JSON/portable), nor documentation of easy migration/interoperability with other tools, so the 'open format' and full portability aspects of the story are unconfirmed. missing for 10: explicit statement of open/standard export format, evidence of full interoperability/reuse elsewhere, and independent confirmation of export completeness.

   • [claimed-docs] “Individual Claude users can export user information and chat history from Settings > Privacy”
   • [claimed-docs] “Data exports include conversation data and the user data for your account.”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   No evidence of a data export/portability feature or open-format export mechanism; docs only mention deleting conversation history, not exporting it, and probes for machine-readable docs/APIs 404. There is nothing showing users can export chats, memory, or generated content in open formats to leave the platform.

   • [claimed-docs] “you can delete individual conversations or your entire conversation history at any time”
   • [claimed-docs] “opt out of use of your conversation activity for model training”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/copilot.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Claude—none0/10

   Claude is closed-source; there is no evidence of an open-license source release for the model or app, and community evidence even criticizes it as closed/opaque compared to FOSS alternatives like Codex CLI (claude-comm-6).

   • [community] “Codex CLI is FOSS, unlike Claude Code, so Codex is less likely to do things like that, and it's one more reason to avoid Claude Code and Cla…”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   Microsoft Copilot is closed-source proprietary software; no evidence indicates any open-license source availability, and probes for docs/API artifacts returned 404s. This is an applicable axis (a product could conceivably be open-sourced) but no evidence supports it, so verdict is none rather than na.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/copilot.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Claude—none0/10

   No evidence in the pack mentions data residency, regional storage options, or geographic controls for where account/chat data is stored; the closest items concern export, audit logs, and training opt-outs, none of which address residency choice.

   ⚑ flag

   Microsoft Copilot—none0/10

   No evidence in the pack mentions data residency, regional storage controls, or any user-facing setting to choose where data is stored; the docs cover features, connectors, and privacy opt-outs but not geographic data residency choices.

   ⚑ flag

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

   weight 3 · round to Claude
   Claude✓fullclaimed8/10

   Claude documents explicit user controls to prevent training use: incognito chats are never used to improve Claude even with Model Improvement enabled, users can toggle the 'Model Improvement' privacy setting, and connector data (Gmail/Drive/Calendar) is explicitly excluded from training. This directly satisfies the ai-native privacy-posture story of preventing data from being used for model training. Missing for 10: independent/third-party verification of these claims and explicit default policy for Enterprise/Team plans beyond connectors.

   • [claimed-docs] “Your incognito chats are not used to improve Claude, even if you have enabled Model Improvement in your privacy settings.”
   • [claimed-docs] “When you allow us to use your chats or coding sessions to help improve Claude, we implement several layers of protection for your privacy.”
   • [claimed-docs] “We do not train our models on your Gmail, Drive, or Calendar connector data, ensuring your private information remains private.”

   proof ↗⚑ flag

   Microsoft Copilot~partialcommunity6/10

   Microsoft's privacy FAQ explicitly states users can opt out of having conversation activity used for model training and can delete conversation history (copilot-docs-35, copilot-docs-36, copilot-docs-38), giving a documented mechanism to prevent training use. However, community reports (copilot-comm-6, copilot-comm-1) show real confusion about scope — a user working in Word had no clear indication whether their document content was being fed to training, and commenters note the opt-out/behavior differs between standalone Copilot chat and 365-integrated Copilot, undermining confidence that the control is comprehensive or transparent across all surfaces. missing for 10: independent verification that opt-out actually blocks training across all integrated products (Word/Excel/Outlook), clearer UI-level opt-out controls inside Office apps, and confirmation the toggle covers enterprise/connector data sources.

   • [claimed-docs] “opt out of use of your conversation activity for model training”
   • [claimed-docs] “Train our generative AI models to create a better experience for you and others.”
   • [claimed-docs] “you can delete individual conversations or your entire conversation history at any time”
   • [community] “When CoPilot showed up in my Word, I was writing a pitch doc... It made me realize I didn't know whether this doc was getting auto-pushed to…”
   • [community] “To be clear this is only for the standalone Copilot chat or app and website; not for the 'Copilot' services integrated into Office 365 etc.”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Claude
   Claude✓fullclaimed8/10

   Claude provides explicit user-facing data controls: exporting chat history/user data (claude-docs-12, 40), reviewing/editing/turning off memory (claude-docs-45), incognito chats excluded from training (claude-docs-46), and enterprise audit logs plus a compliance API for data governance (claude-docs-11, 44). Missing for 10: explicit self-service account/data deletion flow documentation and independent verification that deletion requests are honored.

   • [claimed-docs] “Individual Claude users can export user information and chat history from Settings > Privacy”
   • [claimed-docs] “Data exports include conversation data and the user data for your account.”
   • [claimed-docs] “This article explains how chat search and memory work, what Claude does and doesn’t remember, how to review and edit what’s saved, and how t…”
   • [claimed-docs] “Your incognito chats are not used to improve Claude, even if you have enabled Model Improvement in your privacy settings.”
   • [claimed-docs] “When you allow us to use your chats or coding sessions to help improve Claude, we implement several layers of protection for your privacy.”
   • [claimed-docs] “Audit logs: capture key information about user actions, system events, and data access. ... Compliance API: programmatically access Claude u…”
   • [claimed-docs] “Enterprise includes everything in the Team plan, plus the following: - Security features to ensure the safety and compliance of your organiz…”

   proof ↗⚑ flag

   Microsoft Copilot~partialcommunity6/10

   Docs confirm users can delete individual conversations or entire history and opt out of conversation data being used for model training, giving basic retention/deletion control for the standalone Copilot chat experience (copilot-docs-35, copilot-docs-38). However, community evidence notes this applies only to the standalone Copilot app/site, not to Copilot embedded in Office apps like Word, where a user reported uncertainty about whether their document was being auto-pushed for training with no visible deletion controls (copilot-comm-1, copilot-comm-6). Missing for 10: enterprise/Office-integrated retention controls, clarity on data retention duration before deletion, and independent verification that deletion actually removes data from training pipelines.

   • [claimed-docs] “opt out of use of your conversation activity for model training”
   • [claimed-docs] “you can delete individual conversations or your entire conversation history at any time”
   • [community] “To be clear this is only for the standalone Copilot chat or app and website; not for the 'Copilot' services integrated into Office 365 etc.”
   • [community] “When CoPilot showed up in my Word, I was writing a pitch doc... It made me realize I didn't know whether this doc was getting auto-pushed to…”

   proof ↗⚑ flag

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

   weight 2 · round to Claude
   Claude~partialclaimed6/10

   Claude documents a 'Model Improvement' privacy setting that can be toggled off and 'incognito chats' that are excluded from training even if Model Improvement is enabled, giving users control over whether their conversations are used to improve the model (claude-docs-46, claude-docs-47). This addresses opt-out of usage-for-training, and data export/deletion options exist (claude-docs-12, claude-docs-40), but there is no explicit documentation of a broader telemetry/analytics opt-out (e.g., product usage metrics, crash reporting) beyond model-training data use. missing for 10: explicit telemetry/analytics tracking opt-out settings, independent confirmation that toggling actually stops all usage tracking, documentation of what non-training telemetry data is collected.

   • [claimed-docs] “Your incognito chats are not used to improve Claude, even if you have enabled Model Improvement in your privacy settings.”
   • [claimed-docs] “When you allow us to use your chats or coding sessions to help improve Claude, we implement several layers of protection for your privacy.”
   • [claimed-docs] “Individual Claude users can export user information and chat history from Settings > Privacy”
   • [claimed-docs] “Data exports include conversation data and the user data for your account.”

   proof ↗⚑ flag

   Microsoft Copilot!disputedcontradicted5/10

   Microsoft's own privacy FAQ states users can opt out of having conversation activity used for model training and can delete individual or entire conversation history (copilot-docs-35, copilot-docs-38), which is a real opt-out mechanism for the standalone Copilot chat. However, community reports directly contradict this for Copilot as embedded in Office apps: a Word for Mac user reports 'no way of turning it off' and 'no opt-out mechanism' (copilot-comm-3), and another user reports uncertainty over whether their document was being auto-pushed to Copilot for training with no visible control (copilot-comm-6) — and copilot-comm-1 clarifies the training opt-out only applies to the standalone chat app, not the Office-integrated Copilot surfaces. Missing for 10: a unified, product-wide opt-out control covering all Copilot surfaces (Office, Edge, Windows), independent verification that the training opt-out actually stops data use, and clarity on telemetry beyond training data.

   • [claimed-docs] “opt out of use of your conversation activity for model training”
   • [claimed-docs] “you can delete individual conversations or your entire conversation history at any time”
   • [community] “To be clear this is only for the standalone Copilot chat or app and website; not for the 'Copilot' services integrated into Office 365 etc.”
   • [community] “Hate that if you use Word for Mac, you now have Copilot next to your cursor with no way of turning it off. I just want to use Word... Now th…”
   • [community] “When CoPilot showed up in my Word, I was writing a pitch doc... It made me realize I didn't know whether this doc was getting auto-pushed to…”

   proof ↗⚑ flag

Research

1. knowledge-workerLaunch a deep research run that autonomously searches many sources and returns a cited report

   weight 3 · round to Claude
   Claude✓fullcommunity8/10

   Claude's Research feature is well documented: it operates agentically running multiple searches that build on each other, determines what to investigate next, and delivers thorough answers in minutes with easy-to-check citations. Community evidence is mixed on research depth (some say it lags ChatGPT/Gemini), which caps quality but the core capability is clearly delivered. Missing for 10: independent hands-on benchmark showing citation accuracy/report quality, and clearer detail on breadth of sources searched.

   • [claimed-docs] “With research, Claude delivers thorough answers in minutes, complete with easy-to-check citations so you can trust Claude's findings.”
   • [claimed-docs] “Research transforms how Claude finds and analyzes information. Claude operates agentically, conducting multiple searches that build on each …”
   • [claimed-docs] “Claude operates agentically, conducting multiple searches that build on each other while determining exactly what to investigate next.”
   • [claimed-docs] “Claude delivers thorough answers in minutes, complete with easy-to-check citations so you can trust Claude's findings.”
   • [community] “Meanwhile, Claude's general use cases are... fine. For generic research topics, I find that ChatGPT and Gemini run circles around it: in the…”
   • [community] “Works pretty nicely for research still, not seeing a substantial qualitative improvement over Opus 4.5.”

   proof ↗⚑ flag

   Microsoft Copilot~partialclaimed5/10

   Copilot's 'Researcher' agent is documented as designed to 'find, synthesize, and understand information faster' and Copilot's web-grounded answers include hyperlinked citations, which maps to the deep-research/cited-report story, but there is no detail on autonomous multi-source search depth, report format, or any hands-on/independent validation of report quality. Missing for 10: documentation of the autonomous multi-step search process, description of report output structure, and independent corroboration of research depth/accuracy.

   • [claimed-docs] “Find, synthesize, and understand information faster with Researcher.”
   • [claimed-docs] “This means that Copilot centers its response on high-ranking content from the web and provides hyperlinked citations following generated tex…”
   • [claimed-docs] “Copilot may proactively generate personalized research suggestions for users based on things like past research queries and Copilot memory.”

   proof ↗⚑ flag

2. knowledge-workerGet answers grounded in current web results with citations back to the sources

   weight 2 · round to Microsoft Copilot
   Claude~partialcommunity7/10

   Claude's Research feature is documented to perform agentic multi-step web searches and deliver answers with 'easy-to-check citations' (claude-docs-20, 27, 39, 68), directly matching the story. However, independent community feedback suggests mixed real-world quality—commenters say Claude's general research 'is fine' but that ChatGPT and Gemini 'run circles around it' in depth and presentation (claude-comm-8, claude-comm-9), tempering confidence in how well-grounded/comprehensive the citations truly are. missing for 10: independent hands-on verification of citation accuracy/source quality, and confirmation research draws from live/current web data versus stale index.

   • [claimed-docs] “With research, Claude delivers thorough answers in minutes, complete with easy-to-check citations so you can trust Claude's findings.”
   • [claimed-docs] “Research transforms how Claude finds and analyzes information. Claude operates agentically, conducting multiple searches that build on each …”
   • [claimed-docs] “Claude operates agentically, conducting multiple searches that build on each other while determining exactly what to investigate next.”
   • [claimed-docs] “Claude delivers thorough answers in minutes, complete with easy-to-check citations so you can trust Claude's findings.”
   • [community] “Meanwhile, Claude's general use cases are... fine. For generic research topics, I find that ChatGPT and Gemini run circles around it: in the…”
   • [community] “Works pretty nicely for research still, not seeing a substantial qualitative improvement over Opus 4.5.”

   proof ↗⚑ flag

   Microsoft Copilot✓fullclaimed8/10

   Docs explicitly state Copilot grounds responses in high-ranking web content and provides hyperlinked citations after generated responses, directly matching the story; this is corroborated by broader documentation on research/answer features (Researcher, ask questions and get answers fast). Missing for 10: independent hands-on verification of citation accuracy/quality and no community evidence specifically testing web-grounded citation behavior.

   • [claimed-docs] “This means that Copilot centers its response on high-ranking content from the web and provides hyperlinked citations following generated tex…”
   • [claimed-docs] “Ask questions and get answers fast.”
   • [claimed-docs] “Find, synthesize, and understand information faster with Researcher.”

   proof ↗⚑ flag

Admin

1. team-adminManage members, permissions, and data policies for my organization's workspace

   weight 2 · round to Claude
   Claude~partialclaimed4/10

   Evidence confirms Enterprise plan admin/security features like audit logs and a Compliance API for programmatic access to usage data, implying some org-level governance, but there is no documentation of member management, role/permission assignment, or granular data policy controls for team admins. missing for 10: member invitation/removal workflows, role-based permission management, workspace-level data retention/policy settings, and independent corroboration of admin console functionality.

   • [claimed-docs] “Audit logs: capture key information about user actions, system events, and data access. ... Compliance API: programmatically access Claude u…”
   • [claimed-docs] “Audit logs: capture key information about user actions, system events, and data access.”
   • [claimed-docs] “Enterprise includes everything in the Team plan, plus the following: - Security features to ensure the safety and compliance of your organiz…”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   The evidence pack covers only individual/consumer Copilot features (writing, spreadsheets, browsing, memory, privacy opt-outs for personal conversations) with no mention of team/workspace admin controls such as member management, role-based permissions, or organizational data policies. Missing for 10: admin console documentation, member/role management, org-wide data governance policies, and any evidence of a team-admin experience.

   ⚑ flag

Data controls

1. knowledge-workerExport my complete chat history and account data

   weight 1 · round to Claude
   Claude✓fullclaimed9/10

   Claude's docs explicitly state individual users can export user information and chat history from Settings > Privacy, and that exports include both conversation data and account/user data; Enterprise adds a Compliance API for programmatic access to chat histories and file content. Missing for 10: independent/hands-on confirmation of export completeness or format details beyond first-party docs.

   • [claimed-docs] “Individual Claude users can export user information and chat history from Settings > Privacy”
   • [claimed-docs] “Data exports include conversation data and the user data for your account.”
   • [claimed-docs] “Audit logs: capture key information about user actions, system events, and data access. ... Compliance API: programmatically access Claude u…”

   proof ↗⚑ flag

   Microsoft Copilot—none0/10

   Evidence shows users can delete individual conversations or entire history (copilot-docs-38) and opt out of training use (copilot-docs-35), but there is no mention of an export/download feature for complete chat history or account data as required by the story.

   • [claimed-docs] “you can delete individual conversations or your entire conversation history at any time”
   • [claimed-docs] “opt out of use of your conversation activity for model training”

   proof ↗⚑ flag

2. knowledge-workerControl whether my conversations are used to train models

   weight 3 · round to Claude
   Claude✓fullclaimed8/10

   Claude provides explicit privacy controls: incognito chats are excluded from model training even with Model Improvement enabled, a 'Model Improvement' opt-in/out toggle exists, and connector data (Gmail/Drive/Calendar) is explicitly excluded from training. Missing for 10: independent/hands-on verification that the training opt-out is actually honored in practice, and clearer documentation of the toggle's exact location/scope for all plan tiers.

   • [claimed-docs] “Your incognito chats are not used to improve Claude, even if you have enabled Model Improvement in your privacy settings.”
   • [claimed-docs] “When you allow us to use your chats or coding sessions to help improve Claude, we implement several layers of protection for your privacy.”
   • [claimed-docs] “We do not train our models on your Gmail, Drive, or Calendar connector data, ensuring your private information remains private.”

   proof ↗⚑ flag

   Microsoft Copilot~partialcommunity6/10

   Microsoft's own docs confirm a control exists: users can opt out of conversation activity being used for model training and can delete conversation history (copilot-docs-35, copilot-docs-36, copilot-docs-38). However, community evidence indicates confusion about scope—one commenter notes the opt-out applies to standalone Copilot chat/app, not to Copilot embedded in Office apps like Word (copilot-comm-1), and another user reports genuine uncertainty whether their Word document was being used for training with no clear indication (copilot-comm-6). Missing for 10: clear unified documentation covering training-data opt-out scope across all Copilot surfaces (Office-integrated vs standalone), and independent verification that the opt-out setting functions as described.

   • [claimed-docs] “opt out of use of your conversation activity for model training”
   • [claimed-docs] “Train our generative AI models to create a better experience for you and others.”
   • [claimed-docs] “you can delete individual conversations or your entire conversation history at any time”
   • [community] “To be clear this is only for the standalone Copilot chat or app and website; not for the 'Copilot' services integrated into Office 365 etc.”
   • [community] “When CoPilot showed up in my Word, I was writing a pitch doc... It made me realize I didn't know whether this doc was getting auto-pushed to…”

   proof ↗⚑ flag