Microsoft Copilot vs Muse

Agent access

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

   weight 3 · round drawn
   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

   Muse—none0/10

   No evidence Muse supports plugging in external MCP servers; it only describes its agent building its own tools internally, which is a different mechanism.

   • [claimed-docs] “If a task needs a tool that doesn't exist, your agent builds it for you.”
   • [claimed-docs] “Muse has its own computer, with a file system and a terminal, so it can write its own code and build the tools a task needs.”

   proof ↗⚑ flag

2. ai-native userUse an official CLI

   weight 2 · round drawn
   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

   Muse—none0/10

   No evidence of an official CLI for Muse; all evidence describes a consumer app/avatar/chat interface with an internal terminal for the agent itself, not a CLI for AI-native users to interact with Muse.

   ⚑ flag

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

   weight 3 · round drawn
   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

   Muse—none0/10

   No evidence of a documented public API for developers to programmatically drive Muse; all evidence describes end-user chat/app features and internal agent behavior, not an external API surface.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Muse—none0/10

   Evidence shows Muse has approval cards, activity logs, and permission tracking for connected accounts, but nothing about issuing scoped or least-privilege API credentials/tokens for an agent to use with external services — this is a consumer personal-agent product, not a developer credential-management tool.

   ⚑ flag

5. ai-native userBuild against official SDKs

   weight 2 · round drawn
   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

   Muse—none0/10

   No evidence of any official SDK for developers to build against; evidence only covers end-user features (avatars, goals, side chats, agent building its own tools) rather than a developer-facing SDK.

   ⚑ flag

6. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   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

   Muse—none0/10

   No evidence in the pack mentions webhooks or any event-subscription API for developers; Muse's documented features focus on agent tasks, permissions, and integrations, not outbound webhook subscriptions. missing for 10: any webhook/event API documentation, developer subscription mechanism, or third-party confirmation of webhook support.

   ⚑ flag

Agentic features

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

   weight 2 · round to Muse
   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

   Muse~partialclaimed5/10

   Muse links personal data sources (email, calendar, social, health, finances) and proactively tracks tasks/goals, implying some data-driven suggestions, but the evidence never explicitly describes AI-generated insights or recommendations derived from that data—most documentation focuses on agentic task execution and tool-building rather than analytic insight generation. missing for 10: explicit description of insight/recommendation generation from user data, independent hands-on validation of this specific capability.

   • [claimed-docs] “Link your email, calendar, Instagram, Facebook, health and fitness data, and finances.”
   • [claimed-docs] “The Goals tab is where Muse keeps track of all this for you, and you can interact directly there or talk to it about these tasks in chat.”
   • [claimed-docs] “If a task needs a tool that doesn't exist, your agent builds it for you.”

   proof ↗⚑ flag

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

   weight 2 · round to Microsoft Copilot
   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

   Muse!disputedcontradicted5/10

   Muse's Goals tab, activity log, and approval-card workflow (muse-docs-5, muse-docs-8, muse-docs-13) show first-party support for autonomous background task tracking and execution, and muse-docs-7 explicitly describes agents building tools for unattended tasks. However, an independent hands-on stress test found the agent's control plane starts timing out under load, exposing concrete failure points in its background-automation architecture (muse-comm-1), directly undercutting reliability claims for autonomous operation. missing for 10: independent confirmation that background automations run reliably at scale, more detail on scheduling/triggering mechanisms for autonomous runs.

   • [claimed-docs] “The Goals tab is where Muse keeps track of all this for you, and you can interact directly there or talk to it about these tasks in chat.”
   • [claimed-docs] “If a task needs a tool that doesn't exist, your agent builds it for you.”
   • [claimed-docs] “Tapping on your Muse avatar will show you its full activity log as well as permissions you’ve approved.”
   • [claimed-docs] “Muse shows people a complete audit trail of everything it has done and plans to do.”
   • [community] “Blog post title/finding: the author stress-tested Meta Muse until its agent control plane started timing out, exposing failure points in the…”

   proof ↗⚑ flag

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

   weight 3 · round to Muse
   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

   Muse✓fullclaimed8/10

   Muse is explicitly a built-in AI agent with its own compute, terminal, and file system to build tools and complete delegated tasks (goals, side chats, autonomous tool creation), with approval flows and activity logs for oversight. Missing for 10: independent hands-on verification of delegation quality beyond stress-test edge cases and more detail on task breadth/reliability at scale.

   • [claimed-docs] “Muse has its own computer, with a file system and a terminal, so it can write its own code and build the tools a task needs.”
   • [claimed-docs] “The Goals tab is where Muse keeps track of all this for you, and you can interact directly there or talk to it about these tasks in chat.”
   • [claimed-docs] “If a task needs a tool that doesn't exist, your agent builds it for you.”
   • [claimed-docs] “Tapping on your Muse avatar will show you its full activity log as well as permissions you’ve approved.”
   • [claimed-docs] “Muse shows people a complete audit trail of everything it has done and plans to do.”

   proof ↗⚑ flag

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

   weight 2 · round to Muse
   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

   Muse✓fullcommunity7/10

   Muse is designed around a chat interface where users talk to it in natural language to manage goals, tasks, and tool-building ('talk to it about these tasks in chat', side chats for topic-specific NL interaction). This is corroborated by first-party docs describing conversational control as the primary interface. missing for 10: independent hands-on confirmation of broad natural-language command coverage beyond goals/chat, and detail on command reliability at scale (comm-1 notes control-plane timeouts under stress).

   • [claimed-docs] “The Goals tab is where Muse keeps track of all this for you, and you can interact directly there or talk to it about these tasks in chat.”
   • [claimed-docs] “some people still wanted separate context for certain topics — which made sense as projects grew more complex. So we built side chats.”
   • [claimed-docs] “Tapping on your Muse avatar will show you its full activity log as well as permissions you’ve approved.”
   • [community] “Blog post title/finding: the author stress-tested Meta Muse until its agent control plane started timing out, exposing failure points in the…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   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

   Muse—none0/10

   No evidence Muse publishes any machine-readable API spec (OpenAPI or equivalent) for developers; all evidence concerns end-user agent features, not a documented API surface.

   ⚑ 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 Microsoft Copilot
   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

   Muse!disputedcontradicted6/10

   Muse's docs describe autonomous background task handling via the Goals tab, self-built tools, activity logs and approval cards for review — matching the delegate-and-review story [muse-docs-5][muse-docs-7][muse-docs-8][muse-docs-13][muse-docs-10]. However, an independent hands-on stress test found the agent's control plane timing out under load, exposing failure points in the very autonomous-task architecture being claimed [muse-comm-1], and another commenter notes the assistant is less capable than power-user expectations for building/using tools [muse-comm-2]. Missing for 10: reproducible evidence of reliable long-running multi-step task completion, and resolution/acknowledgment of the reported control-plane timeout issue.

   • [claimed-docs] “The Goals tab is where Muse keeps track of all this for you, and you can interact directly there or talk to it about these tasks in chat.”
   • [claimed-docs] “If a task needs a tool that doesn't exist, your agent builds it for you.”
   • [claimed-docs] “Tapping on your Muse avatar will show you its full activity log as well as permissions you’ve approved.”
   • [claimed-docs] “Muse shows people a complete audit trail of everything it has done and plans to do.”
   • [claimed-docs] “structured approval cards with clear accept/reject actions, and secure storage for your credentials.”
   • [community] “Blog post title/finding: the author stress-tested Meta Muse until its agent control plane started timing out, exposing failure points in the…”
   • [community] “"I, too, have a personal agent but my friends using Muse or Instinct approach the functionality I use mine for quite easily... a sophisticat…”

   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 Microsoft Copilot
   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

   Muse—none0/10

   Evidence describes Muse having its own computer/terminal to build tools, task tracking (Goals tab), and permissions/approval cards, but nothing in the pack mentions browser automation or web navigation on the user's behalf. Missing for 10: any mention of browser control, web research execution, or site-task completion capability.

   ⚑ flag

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

   weight 2 · round to Microsoft Copilot
   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

   Muse~partialclaimed4/10

   Muse describes having its own computer/terminal to build tools and links external accounts (email, calendar, social, health, finance) via structured approvals, which lets it act on the user's behalf across services, but the evidence never shows it seeing or directly operating applications on the user's own device (e.g., screen/GUI control) — it operates its own sandboxed environment, not the user's computer. Missing for 10: evidence of direct screen/GUI control of the user's local applications, and independent confirmation that this cross-app automation reliably works beyond linked-account integrations.

   • [claimed-docs] “Muse has its own computer, with a file system and a terminal, so it can write its own code and build the tools a task needs.”
   • [claimed-docs] “If a task needs a tool that doesn't exist, your agent builds it for you.”
   • [claimed-docs] “structured approval cards with clear accept/reject actions, and secure storage for your credentials.”
   • [claimed-docs] “Link your email, calendar, Instagram, Facebook, health and fitness data, and finances.”

   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 Muse
   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

   Muse~partialcommunity5/10

   Muse's Goals tab and activity log suggest it can track and manage ongoing tasks with an audit trail of completed/planned actions, implying some form of persistent task tracking, but there is no explicit documentation of recurring/scheduled triggers or a scheduling UI. Community evidence also shows the agent's control plane can time out under stress, raising doubts about reliability for automated recurring runs. missing for 10: explicit scheduling/recurrence configuration docs, evidence of one-off vs recurring task setup, and independent confirmation that scheduled tasks reliably complete and report back.

   • [claimed-docs] “The Goals tab is where Muse keeps track of all this for you, and you can interact directly there or talk to it about these tasks in chat.”
   • [claimed-docs] “Muse shows people a complete audit trail of everything it has done and plans to do.”
   • [claimed-docs] “If a task needs a tool that doesn't exist, your agent builds it for you.”
   • [community] “Blog post title/finding: the author stress-tested Meta Muse until its agent control plane started timing out, exposing failure points in the…”

   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 drawn
   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

   Muse—none0/10

   Evidence describes Muse as an AI agent with its own computer/file system, chat, and permission tracking, but there is no mention of an official desktop app, OS-level keyboard shortcuts, or screen access/observation capability. This appears to be a mobile/app-based assistant rather than a desktop tool with screen access.

   ⚑ flag

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

   weight 2 · round to Microsoft Copilot
   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

   Muse~partialclaimed4/10

   There is clear evidence of an iOS app (App Store reviews cited via apps.apple.com), but no evidence at all of an Android app, and no detailed description of feature parity between platforms. missing for 10: Android app existence, feature-completeness claims for either platform, independent verification of app quality.

   • [claimed-docs] “I find it more pleasant than Gemini or ChatGPT which is my default for this type of work.”
   • [claimed-docs] “I’d been curious to try OpenClaw, but didn’t want to deal with the security concerns or headache of setting it up.”

   proof ↗⚑ flag

Custom bots

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

   weight 2 · round drawn
   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

   Muse—none0/10

   Evidence shows Muse supports personal customization (avatar naming/style, side chats for separate contexts) but nothing about creating a distinct 'assistant' with its own instructions/knowledge base that can be shared with other users, which is the core of this story.

   ⚑ flag

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

   weight 2 · round to Microsoft Copilot
   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

   Muse—none0/10

   No evidence describes Muse performing bulk operations across many items; docs mention goals tracking, avatars, side chats, and tool-building, but nothing about batch/bulk processing of items. The community stress-test post even highlights the agent timing out under load rather than handling bulk tasks smoothly.

   ⚑ flag

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

   weight 3 · round drawn
   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

   Muse—none0/10

   The evidence describes Muse's goal tracking, tool-building, and approval workflows, but there is no mention of user-defined conditional rules or event-triggered automations (e.g., 'when X happens, do Y'). Missing for 10: any documentation of a rules/trigger engine, event-based automation configuration, or examples of users setting conditional actions.

   • [claimed-docs] “The Goals tab is where Muse keeps track of all this for you, and you can interact directly there or talk to it about these tasks in chat.”
   • [claimed-docs] “If a task needs a tool that doesn't exist, your agent builds it for you.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   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

   Muse—none0/10

   While Muse has a Goals tab that tracks ongoing tasks and an activity log, there is no evidence describing recurring/scheduled job execution, cron-like automation, or repeat-workflow triggers. missing for 10: explicit scheduling/recurrence feature, evidence of periodic execution, workflow automation configuration.

   ⚑ flag

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

   weight 1 · round to Muse
   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

   Muse~partialclaimed4/10

   Muse provides an activity log/audit trail and approval cards that support reviewing what the agent has done and plans to do (muse-docs-8, muse-docs-13, muse-docs-10), which covers the 'review' portion of the story. However, there is no evidence of explicit versioning of automations/skills or a rollback mechanism to revert an automation to a prior state — the 'Forget' skill only removes stored information, not automation history. missing for 10: explicit versioning of automations, a rollback/undo feature for agent actions, independent confirmation these review tools work reliably in practice.

   • [claimed-docs] “Tapping on your Muse avatar will show you its full activity log as well as permissions you’ve approved.”
   • [claimed-docs] “Muse shows people a complete audit trail of everything it has done and plans to do.”
   • [claimed-docs] “structured approval cards with clear accept/reject actions, and secure storage for your credentials.”
   • [claimed-docs] “You can also use the Forget skill to have Muse forget information about specific topics or people.”

   proof ↗⚑ flag

Connectors

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

   weight 2 · round to Microsoft Copilot
   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

   Muse~partialclaimed3/10

   Muse lets users link specific third-party data sources like email, calendar, Instagram, Facebook, health and finance data (muse-docs-11), which shows some connector-adding capability, but there is no evidence of a browsable directory or marketplace of third-party apps/connectors to explore and add. Missing for 10: an actual app/connector directory UI, discovery/browsing mechanism, and independent confirmation of a marketplace beyond ad-hoc account linking.

   • [claimed-docs] “Link your email, calendar, Instagram, Facebook, health and fitness data, and finances.”

   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 Microsoft Copilot
   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

   Muse~partialclaimed6/10

   Muse docs explicitly support linking email and calendar (and other data sources) with approval/permission controls, but no evidence mentions a cloud drive connector (e.g., Google Drive/Dropbox), and there's no hands-on confirmation that these connected sources are actually searched/used in answers beyond permission approval cards. missing for 10: explicit cloud drive integration, independent evidence of search/use in answers.

   • [claimed-docs] “Link your email, calendar, Instagram, Facebook, health and fitness data, and finances.”
   • [claimed-docs] “structured approval cards with clear accept/reject actions, and secure storage for your credentials.”
   • [claimed-docs] “Tapping on your Muse avatar will show you its full activity log as well as permissions you’ve approved.”

   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 Microsoft Copilot
   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

   Muse~partialcommunity4/10

   Muse's docs claim it 'has its own computer, with a file system and a terminal' and can 'write its own code and build the tools a task needs,' which supports general code-execution capability, but there's no explicit mention of producing charts, computed answers, or downloadable files for user data analysis. A community stress-test report also notes the agent's control plane can time out under load, raising doubts about reliability for heavier computational tasks. Missing for 10: explicit documentation or examples of chart generation, data analysis outputs, downloadable file creation, and independent verification of successful code-execution results.

   • [claimed-docs] “Muse has its own computer, with a file system and a terminal, so it can write its own code and build the tools a task needs.”
   • [claimed-docs] “If a task needs a tool that doesn't exist, your agent builds it for you.”
   • [community] “Blog post title/finding: the author stress-tested Meta Muse until its agent control plane started timing out, exposing failure points in the…”

   proof ↗⚑ flag

Artifacts

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

   weight 2 · round to Microsoft Copilot
   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

   Muse—none0/10

   Muse's evidence focuses on its file system/terminal, tool-building, goals, avatars, and privacy controls, but nothing describes creating or iteratively editing documents, presentations, or exportable files for knowledge-work tasks. missing for 10: any mention of document/presentation creation, editing UI, or export functionality.

   ⚑ flag

Files

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

   weight 3 · round to Microsoft Copilot
   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

   Muse—none0/10

   No evidence in the pack describes Muse handling document/spreadsheet/PDF uploads or analyzing their contents; the material focuses on agent features like avatars, goals, side chats, permissions, and tool-building, not file ingestion or analysis accuracy.

   ⚑ flag

Memory

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

   weight 3 · round to Microsoft Copilot
   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

   Muse~partialclaimed5/10

   Muse's docs imply persistent memory (a 'Forget skill' to remove remembered info about topics/people, plus 'side chats' for separate context threads and a Goals tab tracking ongoing tasks) suggesting it retains and reuses context across conversations, but there is no first-party or hands-on description of how memory is surfaced or applied in new chats. Missing for 10: explicit documentation of cross-chat memory recall/application, independent verification that remembered context actually surfaces in new conversations, and detail on memory scope/limits.

   • [claimed-docs] “You can also use the Forget skill to have Muse forget information about specific topics or people.”
   • [claimed-docs] “some people still wanted separate context for certain topics — which made sense as projects grew more complex. So we built side chats.”
   • [claimed-docs] “So we built side chats.”
   • [claimed-docs] “The Goals tab is where Muse keeps track of all this for you, and you can interact directly there or talk to it about these tasks in chat.”

   proof ↗⚑ flag

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

   weight 1 · round to Microsoft Copilot
   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

   Muse—none0/10

   No evidence describes a persistent custom-instructions or preference-setting feature that shapes all responses; docs mention forget skill, avatars, side chats, and permissions but nothing about setting standing instructions/preferences.

   ⚑ flag

Projects

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

   weight 2 · round to Muse
   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

   Muse~partialclaimed4/10

   Muse offers 'side chats' for separate context on topics as work grows complex and a Goals tab for tracking tasks, suggesting some contextual organization, but there is no explicit 'project/space' construct that bundles chats+files+shared instructions together. Missing for 10: explicit project/workspace container, file-attachment grouping, shared custom instructions across chats, and independent verification of how side chats share or isolate context.

   • [claimed-docs] “The Goals tab is where Muse keeps track of all this for you, and you can interact directly there or talk to it about these tasks in chat.”
   • [claimed-docs] “some people still wanted separate context for certain topics — which made sense as projects grew more complex. So we built side chats.”
   • [claimed-docs] “So we built side chats.”

   proof ↗⚑ flag

Images

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

   weight 2 · round drawn
   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

   Muse—none0/10

   The evidence pack contains no mention of image generation, editing, or any visual/multimodal content creation capability for Muse; it focuses on agent/task automation, avatars, chat organization, and privacy controls. missing for 10: any documentation of image generation from prompts, image editing tools, or multimodal output examples.

   ⚑ flag

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

   weight 2 · round to Microsoft Copilot
   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

   Muse—none0/10

   No evidence in the pack discusses image, screenshot, or photo interpretation capabilities of Muse; all citations focus on agent architecture, avatars, goals, side chats, and privacy controls. Missing for 10: any mention of image/vision input support, screenshot sharing, or accuracy of visual interpretation.

   ⚑ flag

Voice

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

   weight 2 · round to Microsoft Copilot
   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

   Muse—none0/10

   No evidence describes real-time voice conversation capability for Muse; the evidence pack focuses on agent tool-building, goals, side chats, avatar, and privacy features, with no mention of voice interaction or speech interface. Missing for 10: any documentation of voice input/output, real-time conversational voice mode, or hands-on account of speaking with Muse.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Muse—none0/10

   No evidence pack mentions a public API for Muse at all; all evidence describes UI features (avatars, Goals tab, side chats, activity log) with no mention of programmatic access. Absence of evidence for an applicable capability is 'none'.

   ⚑ flag

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

   weight 3 · round drawn
   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

   Muse—none0/10

   There is no evidence of a data export feature or open-format data portability in Muse; the pack only mentions a 'Forget' privacy skill and audit trail, not export/download of user data.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Muse—none0/10

   No evidence indicates Muse's source code is published under any open license; all evidence describes product features and community discussion, not source availability.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Microsoft Copilot—none0/10

   Microsoft Copilot is a cloud-hosted SaaS product with no evidence of any self-hosted or on-premises deployment option; all documentation describes it as a hosted service (Copilot.com, Microsoft 365 cloud integration, Edge browser actions) with no self-hosting mechanism mentioned.

   ⚑ flag

   Muse—none0/10

   No evidence anywhere in the pack indicates Muse can be self-hosted; it's described as a cloud/app-based agent product with no mention of open-source release or self-hosting options.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Muse—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls for Muse users.

   ⚑ flag

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

   weight 3 · round to Microsoft Copilot
   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

   Muse—none0/10

   The evidence pack covers Muse's agent features, permissions, forget skill, and audit trail, but contains no mention of any opt-out or control over whether user data is used to train AI models. missing for 10: explicit opt-out/consent setting for model training, any privacy policy language addressing training-data usage.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   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

   Muse~partialclaimed6/10

   Muse offers a 'Forget' skill to remove information about specific topics/people and provides an activity log/audit trail of actions, giving users some visibility and control, but there's no documentation of full account/data deletion, export, or granular retention policy settings. Missing for 10: explicit data export/deletion controls, retention period settings, and independent verification that 'Forget' fully purges underlying data rather than just suppressing recall.

   • [claimed-docs] “You can also use the Forget skill to have Muse forget information about specific topics or people.”
   • [claimed-docs] “Muse shows people a complete audit trail of everything it has done and plans to do.”
   • [claimed-docs] “Tapping on your Muse avatar will show you its full activity log as well as permissions you’ve approved.”

   proof ↗⚑ flag

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

   weight 2 · round to Microsoft Copilot
   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

   Muse—none0/10

   No evidence pack items mention a telemetry/usage-tracking opt-out setting; there is a 'Forget skill' for topic memory and privacy page references, but nothing about disabling telemetry or usage analytics collection. Missing for 10: any documentation of a telemetry/analytics opt-out toggle, privacy policy language on usage data collection, or user reports confirming such a control exists.

   • [claimed-docs] “You can also use the Forget skill to have Muse forget information about specific topics or people.”
   • [claimed-docs] “Muse shows people a complete audit trail of everything it has done and plans to do.”

   proof ↗⚑ flag

Research

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

   weight 3 · round to Microsoft Copilot
   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

   Muse—none0/10

   No evidence describes Muse performing a deep research run that autonomously searches multiple sources and returns a cited report; the pack focuses on avatar personalization, goals/side chats, permissions, and tool-building, none of which document a research/citation workflow. Missing for 10: any mention of multi-source search, report generation, or citation output.

   ⚑ flag

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

   weight 2 · round to Microsoft Copilot
   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

   Muse—none0/10

   No evidence in the pack describes Muse performing web search with cited sources for research answers; the material focuses on agent architecture, avatars, permissions, and goals rather than grounded citation-backed answers.

   ⚑ flag

Data controls

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

   weight 1 · round drawn
   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

   Muse—none0/10

   Evidence shows a 'Forget' skill and audit trail/activity log, but there is no mention of a data export or account data download feature for chat history or account data. missing for 10: export/download tool for chat history, account data export functionality, documentation of data portability process.

   • [claimed-docs] “You can also use the Forget skill to have Muse forget information about specific topics or people.”
   • [claimed-docs] “Muse shows people a complete audit trail of everything it has done and plans to do.”

   proof ↗⚑ flag

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

   weight 3 · round to Microsoft Copilot
   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

   Muse—none0/10

   The evidence pack shows privacy-adjacent features like a 'Forget skill' for memory and audit trails/permissions, but nothing addresses whether users can opt their conversations out of model training specifically. This is a fair axis for a personal AI agent product, but no evidence documents a training-data control. Missing for 10: any documentation of a training opt-out setting, data-usage policy toggle, or explicit statement about whether conversations are used for model training.

   • [claimed-docs] “You can also use the Forget skill to have Muse forget information about specific topics or people.”
   • [claimed-docs] “Muse shows people a complete audit trail of everything it has done and plans to do.”

   proof ↗⚑ flag