Microsoft Teams vs Buzz
Microsoft Teams wins · 17–13 (20 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnMicrosoft Teamsnone0/10Probes explicitly show no llms.txt (404), no markdown-accessible docs endpoint, and no OpenAPI spec at Microsoft Learn — there's no agent-oriented documentation surface for an AI agent to point at. All other evidence is standard human-readable docs, not agent-consumable formats.
- [probe] “PROBE llms.txt: HTTP 404 at https://learn.microsoft.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://learn.microsoft.com/en-us/microsoftteams/platform/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://learn.microsoft.com/openapi.json, https://learn.microsoft.com/swagger.json, https://learn.mi…”
Buzznone0/10A direct probe found no llms.txt at buzz.xyz (404), and no evidence pack item references agent-oriented documentation formats or discoverability files; only an MCP server and CLI are documented, which don't satisfy this specific story. Missing for 10: an llms.txt or equivalent agent-readable docs endpoint, any mention of agent-oriented documentation standards.
- [probe] “PROBE llms.txt: HTTP 404 at https://buzz.xyz/llms.txt”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnMicrosoft Teams platform is automatable via the Microsoft 365 Agents Toolkit CLI (create, provision, deploy, package, and publish agents entirely from the command line) and via Microsoft Graph APIs that let external services 'run outside the Microsoft Teams user experience' to automate Teams scenarios like messaging, team/channel creation, and exports. This supports CI-style scripted automation of app/agent lifecycle and messaging, but there is no explicit documentation of running the Teams client itself headlessly or wiring these tools into a CI pipeline end-to-end. Missing for 10: explicit headless/CI runbook or GitHub Actions example, confirmation of non-interactive auth flows for CI, and independent evidence of real-world CI usage.
- [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions.”
- [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
- [claimed-docs] “Agent/Application Creation: Generate a new agent or app using available templates and samples.”
- [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
- [claimed-docs] “Validation, Packaging, and Publishing: Validate, package, and publish your agent or application using CLI commands.”
- [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions... Agent/Application Creation: Generate a new agent or app using available…”
- [probe] “official CLI documented at https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/microsoft-365-agents-toolkit-cli”
Buzz ships a CLI (buzz-cli) with scriptable commands for channels, workflows, repos, etc. (buzz-docs-5/7/8), which implies it can be driven non-interactively/automated, and agents have their own keys/audit trails (buzz-gh-4) suggesting programmatic access. However, there is no explicit documentation of a headless mode, CI pipeline integration, or CI-specific examples for Buzz itself. Missing for 10: explicit headless/CI-mode documentation, CI pipeline examples, and independent confirmation of running Buzz unattended in automation.
- [claimed-docs] “buzz channels create --name "my-channel" --type stream --visibility open”
- [claimed-docs] “buzz repos protect set --id my-repo --ref refs/heads/main --push admin --no-force-push --no-delete”
- [claimed-docs] “buzz workflows trigger --workflow buzz workflows approve --token”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round to BuzzMicrosoft Teamsnone0/10No evidence that Microsoft Teams (or its agent/bot platform) supports plugging in MCP servers as tool providers; docs cover bots, message extensions, connectors, webhooks, and Copilot/Graph integration but never mention MCP. Missing for 10: any documentation of MCP server connection, tool registration via MCP, or first-party MCP client support in Teams agents.
- [claimed-docs] “Quickstart: Create an agent and chat with it in Teams”
- [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions.”
- [claimed-docs] “Securely interact with Copilot using web data and work data ([Microsoft Graph](/en-us/graph/overview-major-services) and [Work IQ]”
The only evidence is a documented file titled MCP_DRIVEN_HOOKS.md, suggesting Buzz supports MCP-driven hook integration, but no actual content, examples, or independent confirmation of plugging in third-party MCP servers is provided. Missing for 10: detailed docs on configuring/adding MCP servers, examples of tool usage via MCP, and community or hands-on validation.
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
ai-native userConnect an agent via an official MCP server
weight 3 · round to BuzzMicrosoft Teamsnone0/10The evidence pack covers Teams' bot/agent SDK, Graph API, webhooks, and Agents Toolkit CLI, but nowhere mentions an official MCP (Model Context Protocol) server or endpoint that would let external AI agents connect to Teams. As a SaaS collaboration platform, this axis is a fair question, but no evidence shows it is delivered.
Buzz is a chat/collaboration platform (not itself an agent), so shipping an MCP server axis applies; probe evidence confirms an official MCP-related doc (MCP_DRIVEN_HOOKS.md) exists in the repo, and the product's core design explicitly gives agents their own keys, channel memberships, and audit trails for connecting to the platform. However, the evidence pack lacks detailed documentation of the MCP server's setup, tool surface, or independent confirmation it works as described, and community commentary raises real concerns about the permission/auth model's real-world robustness. Missing for 10: full MCP server documentation/spec, independent hands-on verification of connecting an agent via MCP, and resolution of the permission-model critiques.
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [community] “Commenter says Buzz uses channel-based scoping like humans would, but criticizes that it invented its own auth/permission protocol instead o…”
- [community] “Critique of Buzz's group permission model: "These kinds of rules never survive real world tests. For example if I create a private group jus…”
ai-native userUse an official CLI
weight 2 · round drawnMicrosoft ships an official Microsoft 365 Agents Toolkit CLI, documented as offering the same features as the IDE extensions—agent/app creation from templates, resource provisioning/deployment to Azure, validation/packaging/publishing, and preview—directly supporting AI-native agentic workflows for Teams apps/agents. missing for 10: independent/hands-on verification of CLI usage and no evidence of scripting/automation depth (e.g., CI/CD examples) beyond first-party docs.
- [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions.”
- [claimed-docs] “Agent/Application Creation: Generate a new agent or app using available templates and samples.”
- [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
- [claimed-docs] “Validation, Packaging, and Publishing: Validate, package, and publish your agent or application using CLI commands.”
- [claimed-docs] “Upload and preview your agent or app in Teams, Outlook, and the Microsoft 365 app.”
- [probe] “official CLI documented at https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/microsoft-365-agents-toolkit-cli”
Buzz ships an official CLI (buzz-cli crate) with documented commands spanning channels, repos, workflows, and GIF search, confirming it's a first-class part of the product for agentic/scripted workflows. missing for 10: independent hands-on verification of the CLI beyond vendor docs, and no evidence of broader AI-native conveniences like an llms.txt or shell completions.
- [claimed-docs] “buzz channels create --name "my-channel" --type stream --visibility open”
- [claimed-docs] “buzz gifs search # trending GIFs”
- [claimed-docs] “buzz repos protect set --id my-repo --ref refs/heads/main --push admin --no-force-push --no-delete”
- [claimed-docs] “buzz workflows trigger --workflow buzz workflows approve --token”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
ai-native userDrive the product through a documented public API
weight 3 · round to Microsoft TeamsMicrosoft Teams exposes extensive, well-documented public APIs (Microsoft Graph Teams API, Bot Framework, webhooks/connectors, Teams platform APIs) enabling programmatic control of chats, channels, teams, and messages, plus a CLI (Agents Toolkit CLI) for automating agent/app creation, provisioning, and publishing. This is corroborated by community complaints acknowledging the API exists but noting it requires the fuller Azure/Graph stack rather than simple webhooks. Missing for 10: a discoverable OpenAPI/llms.txt spec (probes returned 404s) and stronger independent hands-on validation of API robustness beyond docs and one critical community note.
- [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
- [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
- [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
- [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions.”
- [claimed-docs] “Agent/Application Creation: Generate a new agent or app using available templates and samples.”
- [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
- [claimed-docs] “Validation, Packaging, and Publishing: Validate, package, and publish your agent or application using CLI commands.”
- [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”
- [probe] “official CLI documented at https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/microsoft-365-agents-toolkit-cli”
Buzz ships a documented CLI (buzz-cli commands for channels, repos, workflows, gifs) and an official MCP server for agent-driven hooks, plus agents get their own API keys/audit trails — all enabling AI-native programmatic control. However, probes show no formal public REST API docs (openapi.json/swagger 404, llms.txt 404), so there's no single canonical 'documented public API' surface, only CLI/MCP tooling. Missing for 10: a published OpenAPI/REST spec or llms.txt, and independent confirmation that agents actually use these interfaces successfully in production.
- [claimed-docs] “buzz channels create --name "my-channel" --type stream --visibility open”
- [claimed-docs] “buzz repos protect set --id my-repo --ref refs/heads/main --push admin --no-force-push --no-delete”
- [claimed-docs] “buzz workflows trigger --workflow buzz workflows approve --token”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
- [probe] “PROBE llms.txt: HTTP 404 at https://buzz.xyz/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://buzz.xyz/openapi.json, https://buzz.xyz/swagger.json, https://buzz.xyz/api/openapi.json, htt…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to BuzzMicrosoft Teamsnone0/10While Teams' Graph API and Agents Toolkit are documented for building agents/apps, none of the evidence describes issuing scoped or least-privilege API credentials specifically for an agent (e.g., granular OAuth scopes, permission consent flows tied to agent identity). The docs mention Azure resource provisioning and Graph API access broadly but not credential scoping mechanics.
- [claimed-docs] “Securely interact with Copilot using web data and work data ([Microsoft Graph](/en-us/graph/overview-major-services) and [Work IQ]”
- [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
- [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
Buzz documents that each agent gets 'their own keys, their own channel memberships, and their own audit trail' (buzz-gh-4), implying some per-agent credential isolation, and CLI commands like `repos protect` show coarse-grained permission levels (buzz-docs-7). However there is no first-party documentation of a formal least-privilege API credential/scoping mechanism (e.g., issuing a key with defined capability sets), and community commentary raises concrete doubts about whether the permission model handles real-world scoping correctly (buzz-comm-3, buzz-comm-5, buzz-comm-6), though this is speculative critique rather than a confirmed hands-on failure. Missing for 10: explicit docs on scoped/limited-permission key issuance, examples of restricting an agent's API access to specific resources, and independent verification that the scoping works as intended.
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [claimed-docs] “buzz repos protect set --id my-repo --ref refs/heads/main --push admin --no-force-push --no-delete”
- [community] “A Slack employee argues multiplayer agents in Buzz risk leaking private data to teammates, requiring complex rulesets about resource access,…”
- [community] “Commenter says Buzz uses channel-based scoping like humans would, but criticizes that it invented its own auth/permission protocol instead o…”
- [community] “Critique of Buzz's group permission model: "These kinds of rules never survive real world tests. For example if I create a private group jus…”
ai-native userBuild against official SDKs
weight 2 · round to Microsoft TeamsMicrosoft documents official SDKs/toolkits (Bot Framework/Teams AI SDK equivalents implied via bots, Agents Toolkit CLI, Microsoft Graph API, Copilot extensibility) for building agents, bots, tabs, and message extensions against Teams, with a dedicated CLI and IDE tooling for creation, provisioning, and publishing. missing for 10: no independent/hands-on developer corroboration of SDK quality or ergonomics, and probes show no machine-readable API spec (openapi.json 404) or llms.txt, suggesting docs aren't fully AI-native optimized.
- [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions.”
- [claimed-docs] “Agent/Application Creation: Generate a new agent or app using available templates and samples.”
- [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
- [claimed-docs] “Validation, Packaging, and Publishing: Validate, package, and publish your agent or application using CLI commands.”
- [claimed-docs] “Port a Slack Bolt app to Teams”
- [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
- [probe] “official CLI documented at https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/microsoft-365-agents-toolkit-cli”
- [probe] “PROBE llms.txt: HTTP 404 at https://learn.microsoft.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://learn.microsoft.com/openapi.json, https://learn.microsoft.com/swagger.json, https://learn.mi…”
Buzz ships a documented CLI (buzz-cli) and an MCP-driven hooks system that agents can call, and evidence notes agents have their own API keys — giving AI-native users some official programmatic surface. However, there is no evidence of a dedicated SDK library (Python/JS/etc.), and probes for an OpenAPI/swagger spec and llms.txt all returned 404, suggesting no formal SDK or API spec is published. Missing for 10: an actual SDK package/library, published API reference (OpenAPI/swagger), and independent confirmation of SDK usage by developers.
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [probe] “PROBE llms.txt: HTTP 404 at https://buzz.xyz/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://buzz.xyz/openapi.json, https://buzz.xyz/swagger.json, https://buzz.xyz/api/openapi.json, htt…”
ai-native userSubscribe to events via webhooks
weight 2 · round to Microsoft TeamsTeams documents Incoming and Outgoing Webhooks and Connectors that let external services subscribe to and post messages/events to Teams channels (ms-teams-docs-12, ms-teams-docs-30, ms-teams-docs-36, ms-teams-docs-44), which is a real webhook subscription mechanism. However the evidence doesn't show Microsoft Graph's richer change-notification/subscription API for broader event types (message edits, membership changes, etc.), nor any AI-agent-specific webhook workflow. Missing for 10: explicit Graph webhook/subscription API documentation for arbitrary event types, and independent confirmation of reliability for programmatic/AI-native use cases.
- [claimed-docs] “With Outgoing Webhooks, you can send text messages from a channel to a web service.”
- [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
- [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
- [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”
Buzznone0/10No evidence of a webhook subscription mechanism; Buzz's architecture is built around Nostr-based signed events, CLI commands, and an MCP-driven hooks system, but nothing in the evidence pack mentions webhooks specifically for external event subscription. Missing for 10: any documentation of a webhook API, subscription endpoint, or event push mechanism.
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to Microsoft TeamsDocs confirm Copilot Chat is embedded in Teams and Outlook, drawing on Microsoft Graph and Work IQ (work data) to generate AI insights/suggestions inside the product, with prompt starters to surface suggestions to users. Missing for 10: concrete detail on specific insight types (e.g., meeting summaries, action-item extraction) and independent/hands-on validation of insight quality beyond vendor docs.
- [claimed-docs] “Securely interact with Copilot using web data and work data ([Microsoft Graph](/en-us/graph/overview-major-services) and [Work IQ]”
- [claimed-docs] “Securely interact with Copilot using web data and work data (Microsoft Graph and Work IQ)”
- [claimed-docs] “Copilot Chat in Outlook and Teams”
- [claimed-docs] “Prompt starters”
- [claimed-docs] “Message streaming ... Targeted messages ... Suggested actions ... Agent slash commands ... Emoji reactions ... Prompt starters”
Evidence shows agents can search history and 'post the threads, not vibes' and orchestrate workflows/reviews, implying some data-derived context surfacing, but there is no explicit documentation of dedicated AI-generated insights, summaries, or suggestion features surfaced to users. Missing for 10: dedicated insight/summary dashboards, proactive suggestion features, and independent confirmation that agents actually generate actionable insights rather than just retrieving raw history.
- [github] “Agents search six months of history and post the threads, not vibes.”
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [github] “Search the conversation, the patch, the workflow run, and the approval in one place”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to BuzzTeams' platform docs describe bots, webhooks/connectors, and Graph API automation that can post messages, create teams/channels, and react to external service events without direct real-time user interaction, which supports background-style automation. However, there is no clear documentation of persistent, autonomous AI-agent workflows (e.g., scheduled triggers, continuous background execution) beyond basic bot/connector integrations, and no independent verification of such automations running reliably unattended. Missing for 10: explicit scheduling/triggering mechanisms for autonomous agent runs, evidence of long-running background AI automation, and independent hands-on confirmation of this capability.
- [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
- [claimed-docs] “Post updates from external services to channels.”
- [claimed-docs] “With Outgoing Webhooks, you can send text messages from a channel to a web service.”
- [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
- [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
- [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
- [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”
Buzz's docs show agents with their own keys/channels/audit trail, workflow-trigger CLI commands, and an MCP-driven-hooks system that lets agents act on events without direct human invocation, all pointing to autonomous background automation. However there is no first-party documentation of scheduling, persistence, or long-running unattended jobs, and no independent hands-on report confirming such automations work reliably in practice. Missing for 10: explicit scheduling/trigger-on-interval docs, independent verification of autonomous background runs, and detail on failure/retry handling.
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [claimed-docs] “buzz workflows trigger --workflow buzz workflows approve --token”
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to Microsoft TeamsTeams docs confirm a built-in Copilot Chat assistant integrated directly in Teams and Outlook, capable of securely interacting with work/web data via Microsoft Graph, plus agent slash commands and prompt starters that let users delegate conversational tasks to it. Missing for 10: independent/hands-on evidence of successful task delegation (community evidence pack focuses on unrelated complaints/bugs, not Copilot capability), and more detail on the scope of tasks Copilot can autonomously execute vs. just answer.
- [claimed-docs] “Copilot Chat in Outlook and Teams”
- [claimed-docs] “Securely interact with Copilot using web data and work data ([Microsoft Graph](/en-us/graph/overview-major-services) and [Work IQ]”
- [claimed-docs] “Securely interact with Copilot using web data and work data (Microsoft Graph and Work IQ)”
- [claimed-docs] “Agent slash commands](/en-us/microsoftteams/platform/agents-in-teams/agent-slash-commands)”
- [claimed-docs] “Prompt starters”
- [claimed-docs] “Message streaming ... Targeted messages ... Suggested actions ... Agent slash commands ... Emoji reactions ... Prompt starters”
Buzz's docs/GitHub describe agents as first-class participants that can open repos, send patches, review code, run workflows, and orchestrate other agents inside the product, and it ships MCP-driven hooks for agent integration (buzz-gh-2, buzz-gh-4, buzz-probe-3). However this is framed as a multi-agent chat/dev platform where external agents join with their own keys, rather than a single dedicated 'built-in assistant' persona users delegate to by default. Missing for 10: a documented default/first-party assistant persona, evidence of a simple task-delegation UX (vs. general agent orchestration infrastructure), and independent hands-on confirmation that delegation works reliably (community threads mostly debate permissions/architecture, not task delegation itself).
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
- [github] “Agents search six months of history and post the threads, not vibes.”
ai-native userOperate the product with natural-language commands
weight 2 · round to Microsoft TeamsDocs show Teams supports natural-language interaction via Copilot Chat, agent slash commands, and prompt starters (ms-teams-docs-15, ms-teams-docs-31, ms-teams-docs-37, ms-teams-docs-6, ms-teams-docs-32), giving a documented path for AI-native users to operate the product conversationally. However, this is vendor-only documentation with no independent corroboration of real-world reliability, and one community report describes a related bot (T-Bot) as 'greyed out and unusable' (ms-teams-comm-11), casting some doubt on maturity. Missing for 10: independent/hands-on validation of Copilot Chat command reliability, broader coverage beyond slash commands/prompt starters, and resolution of the T-Bot usability complaint.
- [claimed-docs] “Securely interact with Copilot using web data and work data ([Microsoft Graph](/en-us/graph/overview-major-services) and [Work IQ]”
- [claimed-docs] “Securely interact with Copilot using web data and work data (Microsoft Graph and Work IQ)”
- [claimed-docs] “Copilot Chat in Outlook and Teams”
- [claimed-docs] “Agent slash commands](/en-us/microsoftteams/platform/agents-in-teams/agent-slash-commands)”
- [claimed-docs] “Prompt starters”
- [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”
Buzz is agent-native chat where agents interact via structured commands, channels, and an MCP/CLI interface (buzz-gh-2, buzz-probe-3, buzz-docs-5/7/8), but the CLI commands shown are structured flags/subcommands rather than natural-language input, and there's no evidence of a conversational NL interface for operating the product. missing for 10: documentation or demo of actual natural-language command parsing/interpretation (vs. structured CLI/MCP calls), independent confirmation that NL commands work in practice.
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [claimed-docs] “buzz channels create --name "my-channel" --type stream --visibility open”
- [claimed-docs] “buzz repos protect set --id my-repo --ref refs/heads/main --push admin --no-force-push --no-delete”
- [claimed-docs] “buzz workflows trigger --workflow buzz workflows approve --token”
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnMicrosoft Teamsnone0/10No evidence of an interactive API reference with runnable examples; probes show llms.txt, docs-md, and openapi.json endpoints all 404, and cited docs are static reference/tutorial pages with no mention of interactive/runnable playgrounds.
- [probe] “PROBE llms.txt: HTTP 404 at https://learn.microsoft.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://learn.microsoft.com/en-us/microsoftteams/platform/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://learn.microsoft.com/openapi.json, https://learn.microsoft.com/swagger.json, https://learn.mi…”
Buzznone0/10There is no evidence of an interactive API reference or runnable examples; the probe explicitly found no OpenAPI/Swagger spec and no llms.txt at Buzz's domain. Only a CLI and MCP hooks documentation exist, which do not constitute an interactive API reference with runnable examples. Missing for 10: any API reference site, OpenAPI/Swagger spec, or interactive/runnable example sandbox.
- [probe] “PROBE llms.txt: HTTP 404 at https://buzz.xyz/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://buzz.xyz/openapi.json, https://buzz.xyz/swagger.json, https://buzz.xyz/api/openapi.json, htt…”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnMicrosoft Teamsnone0/10Teams/Graph exposes REST APIs (e.g., channel-post-messages) so an OpenAPI-style spec is a plausible ask, but the evidence pack shows explicit probe failures (404s) for openapi.json/swagger.json and no documentation page offering a downloadable machine-readable spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://learn.microsoft.com/openapi.json, https://learn.microsoft.com/swagger.json, https://learn.mi…”
- [probe] “PROBE llms.txt: HTTP 404 at https://learn.microsoft.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://learn.microsoft.com/en-us/microsoftteams/platform/.md”
Buzznone0/10Direct probes for OpenAPI/swagger specs and llms.txt all returned 404, and no evidence pack item mentions a downloadable API spec; only a CLI and MCP hooks are documented.
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnMicrosoft Teamsnone0/10No evidence describes a sandbox/test environment isolated from production data for Teams; docs cover agent creation, toolkit CLI, provisioning, and publishing but never mention a dedicated sandbox mode or test tenant separate from live data. missing for 10: dedicated sandbox/test-tenant environment, documentation on data isolation from production, any first-party or community confirmation of safe testing without touching real data.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnMicrosoft Teamsnone0/10While Graph API endpoints are referenced (e.g., graph-rest-1.0 versioning), no evidence pack item documents an explicit API versioning scheme or deprecation policy for Teams/Graph APIs; probes for OpenAPI specs and machine-readable docs also returned 404s. Missing for 10: documented API version lifecycle, deprecation timelines, and changelog/versioning policy pages.
- [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
- [claimed-docs] “Send a new chatMessage in the specified channel.”
- [probe] “PROBE openapi: all candidate paths 404 (https://learn.microsoft.com/openapi.json, https://learn.microsoft.com/swagger.json, https://learn.mi…”
Buzznone0/10No evidence of API versioning or a documented deprecation policy; openapi probes returned 404 and no changelog/versioning docs are cited. Missing for 10: versioned API docs, deprecation policy documentation, changelog or stability guarantees.
- [probe] “PROBE openapi: all candidate paths 404 (https://buzz.xyz/openapi.json, https://buzz.xyz/swagger.json, https://buzz.xyz/api/openapi.json, htt…”
App platform — stories about app platform in this arenaApp platform
Stories about app platform in this arena
Apps
team-adminInstall prebuilt integrations from an app directory or marketplace
weight 3 · round to Microsoft TeamsTeams docs mention publishing agents/apps to Teams (ms-teams-docs-7) and built-in Connectors that let users subscribe to notifications from external web services (ms-teams-docs-30, ms-teams-docs-36, ms-teams-docs-44), implying a gallery of prebuilt integrations, but the evidence never explicitly describes a team-admin-facing app directory/marketplace (e.g., Teams Admin Center app catalog or AppSource) or an admin installation workflow. Missing for 10: explicit documentation of the Teams Admin Center app catalog/AppSource marketplace, admin approval/installation flow for prebuilt third-party apps, and independent corroboration of ease of use for admins.
- [claimed-docs] “Publish your agents or apps in Teams”
- [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
- [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
- [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”
- [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
Buzznone0/10No evidence of an app directory or marketplace for prebuilt integrations that a team-admin could browse and install; Buzz's evidence covers CLI commands, agent orchestration, MCP hooks, and chat/dev workflows but nothing about an installable integrations marketplace. Missing for 10: any mention of an app directory, marketplace listing, or one-click integration install flow.
developerRegister custom slash commands that users invoke from the message box
weight 2 · round to Microsoft TeamsMicrosoft's official developer docs explicitly document 'Agent slash commands' as a supported bot/agent capability for Teams apps, allowing developers to register custom commands invoked from the message compose box. Missing for 10: no detailed first-party walkthrough content beyond the title/reference, and no independent/hands-on developer corroboration of the feature in practice.
- [claimed-docs] “Agent slash commands](/en-us/microsoftteams/platform/agents-in-teams/agent-slash-commands)”
- [claimed-docs] “Agent slash commands”
- [claimed-docs] “Message streaming ... Targeted messages ... Suggested actions ... Agent slash commands ... Emoji reactions ... Prompt starters”
Buzznone0/10No evidence of a slash-command registration API or SDK for developers to add custom commands invoked from the message box; evidence only covers CLI usage, channels, workflows, and MCP hooks. missing for 10: slash command registration API/SDK, documentation of command syntax, examples of third-party commands appearing in the message box.
developerBuild apps with rich interactive UI inside chat — modals, buttons, and structured message layouts
weight 2 · round to Microsoft TeamsDocs confirm Teams platform supports rich in-chat UI building blocks — tabs, message extensions, message streaming, suggested actions, and bots — which are the primitives used to build modals, buttons, and structured layouts in Teams chat. However, the evidence never explicitly names 'Adaptive Cards' or 'task modules/dialogs' (the actual modal/button mechanism), and there is no independent developer corroboration of building such rich UI. Missing for 10: explicit Adaptive Cards/dialog (modal) documentation citation, hands-on developer testimony confirming ease of building interactive card UI.
- [claimed-docs] “Tab apps](/en-us/microsoftteams/platform/tabs/what-are-tabs)”
- [claimed-docs] “Message extensions](/en-us/microsoftteams/platform/messaging-extensions/what-are-messaging-extensions)”
- [claimed-docs] “Message streaming](/en-us/microsoftteams/platform/bots/streaming-ux)”
- [claimed-docs] “Message streaming ... Targeted messages ... Suggested actions ... Agent slash commands ... Emoji reactions ... Prompt starters”
- [claimed-docs] “Tab apps”
- [claimed-docs] “Message extensions”
- [claimed-docs] “Message streaming”
Buzznone0/10Evidence shows Buzz as a chat/collaboration platform with channels, canvases, CLI, and agent integration, but there is no mention of a developer-facing SDK or API for building interactive UI elements like modals, buttons, or structured message layouts inside chat — this is a distinct app-platform capability (like Slack's Block Kit) that is not documented anywhere in the pack. Missing for 10: any API/SDK for interactive components, modal/button primitives, message-layout builder documentation.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnMicrosoft Teamsnone0/10The evidence describes individual Graph API calls (single channel message send, single team/channel creation, export APIs) and CLI commands for single agent/app packaging, but nothing documents bulk or batch operations across many items at once (e.g., batch message send, bulk channel creation, bulk data export in one call). Missing for 10: batch API support, bulk create/update endpoints, CLI bulk commands, or any documented example of operating on multiple items simultaneously.
- [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
- [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
- [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
- [claimed-docs] “Use Microsoft Graph to create a new virtual team when a new business issue arises, add the right people to the team, and configure the team …”
- [claimed-docs] “Use Microsoft Graph to create a new virtual team ... add the right people ... configure the team with channels, tabs, and apps.”
Buzznone0/10Evidence shows CLI/agent commands operating on single items (one channel, one repo, one workflow) but no documented bulk/batch operations across many items at once; no evidence of scripting loops, batch APIs, or multi-item commands.
- [claimed-docs] “buzz channels create --name "my-channel" --type stream --visibility open”
- [claimed-docs] “buzz repos protect set --id my-repo --ref refs/heads/main --push admin --no-force-push --no-delete”
- [claimed-docs] “buzz workflows trigger --workflow buzz workflows approve --token”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to BuzzTeams offers webhooks/connectors and Graph API triggers (incoming/outgoing webhooks, channel message posting) that could be wired into external automation like Power Automate, but there's no native user-facing rule engine within Teams itself for defining 'if event X then action Y' automations. missing for 10: a documented native automation/rules builder (e.g., Power Automate integration specifics), evidence of trigger-condition-action configuration UI, and independent confirmation of reliability.
- [claimed-docs] “With Outgoing Webhooks, you can send text messages from a channel to a web service.”
- [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
- [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
- [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”
- [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
- [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
Buzz documents workflow triggers (buzz-docs-8) and a dedicated 'MCP-driven hooks' doc (buzz-probe-3) implying event-based automation tied to agent actions, but there is no detailed spec of rule syntax, supported event types, or conditions, and no independent confirmation of reliability. missing for 10: full rule-definition schema/docs, breadth of triggerable events, hands-on/independent verification that hooks fire reliably.
- [claimed-docs] “buzz workflows trigger --workflow buzz workflows approve --token”
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnMicrosoft Teamsnone0/10No evidence in the pack shows Teams supporting scheduled or recurring jobs/workflows (e.g., no mention of Power Automate/Workflows integration, cron-like triggers, or recurring automation setup) — the docs cover bots, tabs, message extensions, webhooks, and CLI tooling but nothing about recurring/scheduled automation. Missing for 10: any documentation of recurring/scheduled workflow triggers, workflow automation platform integration, or CLI/API support for scheduling jobs.
Buzznone0/10No evidence of any scheduling/cron/recurring-trigger capability in Buzz — workflows can be triggered manually or via CLI/MCP hooks, but nothing documents recurring or time-based scheduling. Missing for 10: any docs/CLI command for cron-style or recurring job scheduling, evidence of scheduled workflow runs.
ai-native userVersion, review, and roll back my automations
weight 1 · round to BuzzMicrosoft Teamsnone0/10No evidence of any versioning, review, or rollback capability for automations/workflows in Teams; the Agents Toolkit CLI docs cover creation, provisioning, and publishing but nothing about version history, diffing, review workflows, or reverting a deployed agent/automation to a prior state.
Buzz's core model treats automations as git-style patches with review and merge decisions baked into the channel (buzz-gh-1, buzz-gh-5), and the CLI exposes workflow trigger/approve commands (buzz-docs-8) plus repo protection rules (buzz-docs-7), giving some versioning and review capability for automation-like workflows. However, there is no explicit evidence of a 'rollback' mechanism for workflows/automations specifically, nor of automation-specific version history beyond generic git patch review. Missing for 10: explicit rollback/undo functionality for workflows, and dedicated versioning UI/CLI for automations distinct from general code patches.
- [github] “Turn a feature branch into a room where patches, CI, review, and the merge decision live together — so the channel becomes the record of why…”
- [github] “Search the conversation, the patch, the workflow run, and the approval in one place”
- [claimed-docs] “buzz repos protect set --id my-repo --ref refs/heads/main --push admin --no-force-push --no-delete”
- [claimed-docs] “buzz workflows trigger --workflow buzz workflows approve --token”
Bots integrations — stories about bots integrations in this arenaBots integrations
Stories about bots integrations in this arena
Ai agents
ai-native userAdd an AI agent as a member of a channel that participates in conversations when mentioned
weight 3 · round drawnDocs confirm Teams supports bots/agents that can be added to Teams and 'initiate and participate in conversations' within channels, with quickstart guidance to 'create an agent and chat with it,' plus supporting features like slash commands and message streaming that are used for triggering agent responses in conversations. Missing for 10: explicit documentation of the @mention trigger mechanism specifically and independent/hands-on confirmation that agents behave as first-class channel members when mentioned.
- [claimed-docs] “Quickstart: Create an agent and chat with it in Teams”
- [claimed-docs] “Create Microsoft Teams apps with bots that can initiate and partici”
- [claimed-docs] “Agent slash commands](/en-us/microsoftteams/platform/agents-in-teams/agent-slash-commands)”
- [claimed-docs] “Message streaming](/en-us/microsoftteams/platform/bots/streaming-ux)”
- [claimed-docs] “Help users get tasks done in conversations.”
Buzz's core design explicitly gives agents their own channel memberships, keys, and audit trail, and describes agents participating in channel conversations (searching history, posting threads, orchestrating other agents) — directly matching the story of adding an AI agent as a channel member that engages when mentioned. However, there's no explicit documentation of an '@mention triggers agent response' mechanism, and community commentary treats it simply as 'bots in chat rooms' without confirming mention-based triggering specifics. Missing for 10: explicit documentation of mention-triggered activation, independent hands-on confirmation of this exact UX flow.
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [github] “Agents search six months of history and post the threads, not vibes.”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [community] “"Marketing bullshit aside, this is just bots in chat rooms, right? Am I the crazy one?"”
ai-native userHave an agent read and post channel messages through the official API using scoped tokens
weight 3 · round to Microsoft TeamsMicrosoft Graph API documentation confirms an app/agent can post a chatMessage to a channel (ms-teams-docs-11/21) and Teams bots/agents can participate in conversations and automate channel/team actions (ms-teams-docs-8,9,19,20,35), and export APIs allow reading channel messages (ms-teams-docs-13). This is inherently permission-scoped via Azure AD app registrations, consistent with an 'official API with scoped tokens' model. Missing for 10: explicit documentation naming OAuth scope/permission types (e.g., ChannelMessage.Send/Read.All) for this exact read+post flow, and independent hands-on confirmation that an AI agent can freely read arbitrary channel messages (community notes Graph/Azure API setup is heavier than Slack's webhooks, ms-teams-comm-11).
- [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
- [claimed-docs] “Send a new chatMessage in the specified channel.”
- [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
- [claimed-docs] “Help users get tasks done in conversations.”
- [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
- [claimed-docs] “Create Microsoft Teams apps with bots that can initiate and partici”
- [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
- [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”
Buzz is explicitly agent-first: agents have their own keys, channel memberships, and audit trails, can search history and post threads, and there's a documented CLI and MCP server for programmatic interaction. However, no OpenAPI/API spec was found (404s on all probed endpoints), and no explicit documentation of 'scoped tokens' for API access was cited, so the 'official API with scoped tokens' framing is only partially evidenced. missing for 10: explicit scoped-token/auth-scope documentation, a discoverable official REST/HTTP API spec (openapi.json returned 404).
- [github] “Agents search six months of history and post the threads, not vibes.”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [claimed-docs] “buzz channels create --name "my-channel" --type stream --visibility open”
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
- [probe] “PROBE openapi: all candidate paths 404 (https://buzz.xyz/openapi.json, https://buzz.xyz/swagger.json, https://buzz.xyz/api/openapi.json, htt…”
Bot api
developerPost a message into a channel with a simple incoming webhook URL
weight 2 · round to Microsoft TeamsMicrosoft Teamsdisputedcontradicted5/10Docs clearly describe Incoming Webhooks as a way to post messages from external apps to a Teams channel via a webhook URL (ms-teams-docs-36, ms-teams-docs-12, ms-teams-docs-44, ms-teams-docs-30), matching the story's ask. However, hands-on community feedback contradicts the 'simple' framing, stating that real API integration with Teams 'requires the full Azure/Graph API stack unlike Slack's simple webhooks' (ms-teams-comm-11), indicating the webhook path is not as frictionless as documented. Missing for 10: independent corroboration that incoming webhook setup is as simple in practice as the docs claim, and clarity on whether legacy Incoming Webhooks/connectors remain fully supported going forward.
- [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
- [claimed-docs] “With Outgoing Webhooks, you can send text messages from a channel to a web service.”
- [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”
- [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
- [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”
Buzznone0/10No evidence of a simple incoming webhook URL feature for posting messages; Buzz's integration surface described is CLI commands, agent keys/channel membership, and MCP hooks, not a plug-and-play webhook URL. Missing for 10: any documentation of a webhook endpoint, webhook URL generation, or simple HTTP POST-to-channel mechanism.
- [claimed-docs] “buzz channels create --name "my-channel" --type stream --visibility open”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
developerBuild a bot that receives messages and events in real time through an events API or gateway connection
weight 3 · round to Microsoft TeamsTeams supports building bots that receive messages/events, with docs covering bot creation, message streaming, slash commands, and porting Slack Bolt apps (implying event-driven bot architecture), plus webhooks/connectors for real-time notifications to channels. However, evidence never explicitly describes a dedicated 'events API' or gateway/WebSocket connection mechanism (like Slack's Events API or Socket Mode) — the Bot Framework's underlying real-time messaging endpoint mechanics aren't detailed, and one community comment notes API integration requires the full Azure/Graph stack rather than simple webhooks, adding friction. Missing for 10: explicit documentation of the real-time events/gateway protocol (e.g., Bot Framework messaging endpoint or streaming API mechanics), independent/hands-on validation of real-time event delivery reliability.
- [claimed-docs] “Quickstart: Create an agent and chat with it in Teams”
- [claimed-docs] “Port a Slack Bolt app to Teams”
- [claimed-docs] “Message streaming](/en-us/microsoftteams/platform/bots/streaming-ux)”
- [claimed-docs] “Agent slash commands](/en-us/microsoftteams/platform/agents-in-teams/agent-slash-commands)”
- [claimed-docs] “With Outgoing Webhooks, you can send text messages from a channel to a web service.”
- [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
- [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
- [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”
Buzz's architecture gives agents their own keys, channel memberships, and audit trails, and documents MCP-driven hooks for agent integration, implying some event-driven mechanism for bots to react to chat activity. However, there is no explicit documentation of a formal events API, WebSocket/gateway protocol, or real-time subscription model comparable to Slack's Events API, and probes for openapi/llms.txt returned 404s. Missing for 10: explicit gateway/WebSocket protocol docs, formal events API reference, and independent confirmation that bots receive events in real time.
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [probe] “official MCP server documented at https://raw.githubusercontent.com/block/buzz/main/docs/MCP_DRIVEN_HOOKS.md”
- [probe] “PROBE llms.txt: HTTP 404 at https://buzz.xyz/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://buzz.xyz/openapi.json, https://buzz.xyz/swagger.json, https://buzz.xyz/api/openapi.json, htt…”
Calls huddles — stories about calls huddles in this arenaCalls huddles
Stories about calls huddles in this arena
Ai notes
ai-native userGet AI-generated notes and recaps from meetings and huddles I attended or missed
weight 2 · round drawnMicrosoft Teamsnone0/10The evidence pack contains no mention of Copilot meeting recap, AI-generated notes, or transcript summarization features for Teams meetings/huddles; it only covers bot/app platform docs, Graph APIs, webhooks, and unrelated community complaints. Missing for 10: any documentation of Copilot meeting recap/notes generation, evidence of summarizing missed meetings, or hands-on confirmation of this capability.
Buzznone0/10Buzz's evidence covers voice huddles, channels, agent search of history, and repo/workflow features, but there is no mention of AI-generated meeting notes, recaps, or summaries for huddles attended or missed. Missing for 10: any documentation of automatic meeting/huddle transcription or summary generation, evidence of a recap feature for missed huddles.
Calls
team-adminStart an audio or video call directly from a channel or DM without leaving the app
weight 3 · round drawnDocs confirm Teams delivers integrated 'calling' alongside chat and meetings (ms-teams-docs-18), and community reports reference an in-app 'join call UI' and audio/video controls during calls (ms-teams-comm-10), implying calls happen without leaving the client. However, there is no specific documentation describing the exact one-click call button from a channel or DM, nor confirmation it works reliably. Missing for 10: explicit product docs on the channel/DM call-start UI, and reliable hands-on confirmation (the only firsthand account cites bugs with call UI being broken/missing).
- [claimed-docs] “Microsoft Teams delivers chat-based collaboration, meetings, calling, and enterprise voice features.”
- [community] “'I've had many critical bugs, including the video on/off & audio mute button failing during calls, the join call UI being broken/missing, jo…”
Evidence mentions 'drop into voice huddles' as a feature (buzz-gh-2), suggesting audio/video calling exists within the app, but there is no documentation on how to initiate a call from a channel/DM, no UI walkthrough, and no independent confirmation it works as described. Missing for 10: dedicated call-initiation documentation, admin-specific controls, video call evidence beyond a single passing mention, and hands-on/community confirmation of the feature working.
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
team-adminShare my screen during a call for live collaboration
weight 2 · round to Microsoft TeamsTeams docs only vaguely reference 'meetings and calling' features without a specific citation of screen-sharing, while community hands-on reports confirm the capability exists (screen share + annotation) but describe it as slow to enable ('a good 30 seconds') and annotation mode 'gets stuck', undermining the smooth live-collaboration promise. Missing for 10: explicit first-party documentation of the screen-share feature, admin/policy controls for screen sharing, and reliability corroboration beyond the negative anecdotes.
- [claimed-docs] “Microsoft Teams delivers chat-based collaboration, meetings, calling, and enterprise voice features.”
- [community] “'We use zoom but are switching to teams... To my horror it was the epitome of bloat. It essentially takes a screenshot of the presenters des…”
- [community] “Complaint list: no ability to link to conversations, inconsistent UI between channels and direct chats (no threading/code blocks in DMs), no…”
Buzznone0/10Buzz documents voice huddles (buzz-gh-2) and video-with-comments features (buzz-docs-3), but no evidence anywhere describes screen sharing during a call. Missing for 10: any mention of screen-share functionality, UI, or CLI command for sharing a screen in a huddle.
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [claimed-docs] “A video playing in Buzz with frame-anchored comments in a side panel”
Channels threads — stories about channels threads in this arenaChannels threads
Stories about channels threads in this arena
External collaboration
team-adminCollaborate with external partners through guest accounts or shared channels with limited access
weight 2 · round drawnMicrosoft Teamsnone0/10The evidence pack contains no mention of guest accounts, external access controls, or shared channels for cross-organization collaboration — it focuses entirely on bots, agents, APIs, webhooks, and app development. Missing for 10: any documentation of guest account provisioning, external user permissions, shared/B2B channels, or admin controls governing external partner access.
Buzznone0/10Evidence covers channel creation, visibility settings, and agent-specific permissions, but nothing describes guest accounts for external partners or a limited-access sharing model for outside collaborators. Missing for 10: guest account mechanism, external-partner access controls, documentation of restricted/limited-access collaboration for non-org members.
Messaging model
team-adminOrganize conversations into public and private channels with membership controls
weight 3 · round to BuzzEvidence confirms Teams channels exist and can be created/configured via Graph API (ms-teams-docs-8, ms-teams-docs-35, ms-teams-docs-43), implying channel-based organization, but nothing explicitly documents public vs. private channel types or membership/access controls for admins. Missing for 10: explicit documentation of public/private channel distinction, membership management APIs or admin UI, and any independent confirmation of these controls working as described.
- [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
- [claimed-docs] “Use Microsoft Graph to create a new virtual team when a new business issue arises, add the right people to the team, and configure the team …”
- [claimed-docs] “Use Microsoft Graph to create a new virtual team ... add the right people ... configure the team with channels, tabs, and apps.”
Buzz supports creating channels/rooms with a visibility flag ('make it private', CLI --visibility open) and per-agent/user channel memberships, indicating basic public/private organization with membership. However, evidence for granular admin membership controls (e.g., invite management, role-based permissions, moderation) is thin, and community critique raises concrete doubts about the robustness of its custom permission model in real-world edge cases (e.g., auto-invite conflicts). missing for 10: detailed admin UI/CLI for managing membership/invites, documented role-based access control, independent verification that private channels reliably restrict access.
- [claimed-docs] “Spin up a room in seconds. Name it, describe it, make it private.”
- [claimed-docs] “buzz channels create --name "my-channel" --type stream --visibility open”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [community] “Commenter says Buzz uses channel-based scoping like humans would, but criticizes that it invented its own auth/permission protocol instead o…”
- [community] “Critique of Buzz's group permission model: "These kinds of rules never survive real world tests. For example if I create a private group jus…”
team-adminReply in threads so side discussions stay attached to the original message
weight 3 · round to Microsoft TeamsTeams channels do support conversation threads (implied by generic docs about conversations and channel messaging, e.g. ms-teams-docs-9, ms-teams-docs-11), but the evidence pack lacks any first-party documentation specifically describing 'reply in thread' functionality, and multiple community reports call out threading as confusing or poorly implemented ('the biggest issue was the threading; it truly beggars belief', 'no threading... inconsistent UI', 'took me long to realise... to follow along the threads'). Missing for 10: explicit product docs/UI walkthrough of thread-reply feature, and independent confirmation that threading works smoothly rather than being a pain point.
- [claimed-docs] “Help users get tasks done in conversations.”
- [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
- [community] “Complaint list: no ability to link to conversations, inconsistent UI between channels and direct chats (no threading/code blocks in DMs), no…”
- [community] “'Teams is horribly unintuitive to use. The UI is much worse than Slack. Took me long to realise I was looking at the chat window and to foll…”
- [community] “'My team hated it, I tolerated it... The biggest issue was the threading; it truly beggars belief... Moving (and paying) for Slack was the b…”
Buzznone0/10The evidence pack describes channels, search across conversations, and agent chat rooms, but no documentation or feature mentions threaded replies to keep side discussions attached to an original message. missing for 10: any mention of a reply/thread UI or API, docs on thread creation, or community confirmation of threading behavior.
team-adminCatch up on busy channels efficiently because every conversation is organized under a named topic or thread
weight 2 · round to BuzzMicrosoft Teamsdisputedcontradicted3/10Docs confirm Teams channels exist and can be organized with channels/tabs (ms-teams-docs-8, ms-teams-docs-35, ms-teams-docs-43), implying topic-based organization, but hands-on community reports directly contradict effective thread/topic organization: 'The biggest issue was the threading; it truly beggars belief' and no ability to link to conversations, with 'inconsistent UI between channels and direct chats (no threading/code blocks in DMs)' and users confused distinguishing chat vs threads. Missing for 10: first-party documentation specifically describing named-topic thread organization, and any hands-on evidence that threading actually helps admins catch up efficiently.
- [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
- [claimed-docs] “Use Microsoft Graph to create a new virtual team when a new business issue arises, add the right people to the team, and configure the team …”
- [claimed-docs] “Use Microsoft Graph to create a new virtual team ... add the right people ... configure the team with channels, tabs, and apps.”
- [community] “'My team hated it, I tolerated it... The biggest issue was the threading; it truly beggars belief... Moving (and paying) for Slack was the b…”
- [community] “Complaint list: no ability to link to conversations, inconsistent UI between channels and direct chats (no threading/code blocks in DMs), no…”
- [community] “'Teams is horribly unintuitive to use. The UI is much worse than Slack. Took me long to realise I was looking at the chat window and to foll…”
Buzz documents named rooms/channels created per feature or topic (buzz-docs-4, buzz-docs-5) and shows agents searching and posting 'threads, not vibes' with unified search across conversation, patch, workflow and approval (buzz-gh-3, buzz-gh-5), supporting organized, catch-up-friendly channels. However there's no explicit catch-up/unread-summary tooling or independent hands-on evidence that this actually makes busy-channel triage efficient for a human admin. missing for 10: explicit catch-up/digest feature, independent/hands-on validation of thread organization reducing admin overhead.
- [claimed-docs] “Spin up a room in seconds. Name it, describe it, make it private.”
- [claimed-docs] “buzz channels create --name "my-channel" --type stream --visibility open”
- [github] “Agents search six months of history and post the threads, not vibes.”
- [github] “Search the conversation, the patch, the workflow run, and the approval in one place”
Notifications
team-adminTune notifications per channel, keyword, and schedule so only what matters interrupts me
weight 2 · round drawnMicrosoft Teamsnone0/10No evidence in the pack documents per-channel, keyword, or schedule-based notification tuning; the only related community evidence explicitly says users 'can't seem to unsubscribe' and that muting notifications is 'impossible' even with settings turned off. missing for 10: any docs on channel-level notification settings, keyword alerts, or scheduled quiet hours.
- [community] “'MS have not implemented muting as a feature... you can't unsubscribe yourself... Unavoidable alerts that any idiot on any channel can annoy…”
- [community] “'My biggest grief with Teams is that it's impossible to shut off notifications. With pretty much everything turned off... it still blinks th…”
Buzznone0/10No evidence of notification tuning by channel, keyword, or schedule anywhere in the docs, CLI reference, or README; the CLI examples cover channels, repos, workflows, and GIFs but nothing about notification preferences or muting/alerting rules. Missing for 10: any mention of notification settings, keyword alerts, schedule/quiet-hours controls, or per-channel notification toggles.
Compliance exports — stories about compliance exports in this arenaCompliance exports
Stories about compliance exports in this arena
Compliance
platform-engineerReview audit logs of admin and user actions across the workspace
weight 2 · round to BuzzMicrosoft Teamsnone0/10The evidence pack includes Teams Export APIs for exporting chat/channel messages, but nothing documents an audit log of admin and user actions across the workspace (e.g., admin center audit trail, sign-in/action logs). This is an applicable enterprise-compliance axis for a SaaS collaboration platform, but no evidence demonstrates it. Missing for 10: any documentation of an audit log feature, admin action tracking, or audit log search/export API distinct from content export.
- [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
- [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”
The only relevant evidence is a passing mention that agents have 'their own audit trail' alongside keys and channel memberships, which hints at some logging of agent actions but says nothing about a queryable/reviewable log covering both admin and human user actions across the workspace, nor any export/compliance tooling. Missing for 10: documented audit log viewer or export, coverage of admin actions and human user actions (not just agent actions), retention/compliance controls, and any independent corroboration.
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
platform-engineerEnforce message retention policies and legal holds for compliance and eDiscovery
weight 2 · round to Microsoft TeamsThe evidence only covers Teams Export APIs for retrieving 1:1, group, meeting, and channel messages (including deleted messages up to 21 days) for eDiscovery-style export, but there is no documentation of retention policy configuration, legal hold mechanisms, or Purview-based compliance controls referenced in this pack. Missing for 10: retention policy documentation, legal hold configuration/enforcement details, and independent/hands-on confirmation of compliance workflows.
- [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
- [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”
Buzznone0/10No evidence of retention policy configuration, legal hold mechanisms, or eDiscovery/compliance export tooling in Buzz's docs or CLI; the product focuses on chat/agent collaboration and repo protection, not compliance retention. missing for 10: retention policy controls, legal hold feature, eDiscovery export capability, compliance documentation.
Exports
team-adminExport the full message history of my workspace in machine-readable formats, including private conversations where policy allows
weight 3 · round to Microsoft TeamsMicrosoft documents Teams Export APIs that allow admins to export 1:1, group chat, meeting chats, and channel messages, including recovering deletions within 21 days, which directly supports machine-readable compliance exports. However, evidence does not confirm formats, full scope of 'all private conversations where policy allows', eDiscovery integration details, or independent/hands-on verification. Missing for 10: documentation of specific export file formats/schema, confirmation of full coverage of private chats beyond examples, independent or hands-on validation of the export process, and details on policy-based access controls governing what admins can export.
- [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
- [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”
Buzznone0/10No evidence of any export/compliance feature for full workspace message history in machine-readable formats; evidence covers CLI for channels, workflows, repos, but nothing about admin data export or e-discovery. missing for 10: export/download tooling, machine-readable format documentation, admin controls over private conversation export, compliance/legal-hold features.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to BuzzMicrosoft Graph and the Bot/Agents Toolkit expose substantial programmatic control—creating teams/channels, posting messages, managing webhooks, exporting chats, and building agents/bots/tabs—but this is a broad SDK/app-extension surface, not a documented 1:1 API mirror of every UI action (e.g., meetings/calls, reactions, threading UI). A community report also notes API integration requires the full Azure/Graph stack, unlike simpler alternatives, indicating friction rather than seamless UI-API parity. Missing for 10: explicit API coverage for meeting/calling controls and other real-time UI actions, and independent verification that all UI capabilities are exposed via API.
- [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
- [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
- [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
- [claimed-docs] “Use Microsoft Graph to create a new virtual team when a new business issue arises, add the right people to the team, and configure the team …”
- [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”
- [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”
Buzz's CLI (buzz-cli) and agent capabilities (buzz-gh-2, buzz-docs-5/7/8) show many UI actions—creating channels, protecting repos, triggering/approving workflows—are exposed programmatically, and agents are described as having full access to open repos, review code, run workflows, and join channels (buzz-gh-2, buzz-gh-4). However, there's no documented OpenAPI/REST spec (buzz-probe-2 shows 404s) confirming full API parity, and some UI-only features like video comments or huddles are not shown as CLI/API accessible. missing for 10: a public API/OpenAPI reference proving complete UI-API parity, evidence that video/canvas/huddle features are scriptable via API.
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [github] “Agents have their own keys, their own channel memberships, and their own audit trail.”
- [claimed-docs] “buzz channels create --name "my-channel" --type stream --visibility open”
- [claimed-docs] “buzz repos protect set --id my-repo --ref refs/heads/main --push admin --no-force-push --no-delete”
- [claimed-docs] “buzz workflows trigger --workflow buzz workflows approve --token”
- [probe] “PROBE openapi: all candidate paths 404 (https://buzz.xyz/openapi.json, https://buzz.xyz/swagger.json, https://buzz.xyz/api/openapi.json, htt…”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnMicrosoft documents Teams Export APIs that let (typically admin/compliance) users export 1:1, group, meeting, and channel chat content, including recently deleted messages — showing some data portability exists. However, this is framed as a compliance/eDiscovery tool rather than a self-service 'export everything and leave' flow, and no evidence specifies open, non-proprietary formats or a full account/data export including files, calendar, and settings. Missing for 10: explicit open-format guarantee (e.g., JSON/CSV/mbox), self-service full account export for ordinary end-users, and confirmation of completeness (files, contacts, calendar) beyond chat messages.
- [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
- [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”
Buzz's open-source, self-hostable design and Nostr-based signed-event architecture imply data ownership and portability ('the project lives in one place, and that place is yours'; run your own relay), but no CLI command or documented feature explicitly exports data in an open format for a user to leave with. Missing for 10: an explicit export/backup command, documentation of the open data format schema, and independent confirmation that self-hosted data can be fully extracted and reused elsewhere.
- [claimed-docs] “No GitHub. No Discord. No stitching five services together. The project lives in one place, and that place is yours.”
- [claimed-docs] “Run your own relay for one community, or let an operator host thousands on shared infrastructure — same OSS codebase, same URL-is-your-works…”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
ai-native userRead the product's source under an open license
weight 2 · round to BuzzMicrosoft Teamsnone0/10Microsoft Teams is closed-source proprietary software; no evidence in the pack indicates any open-license source availability, and the axis clearly applies since the story concerns openness of source code.
Buzz's source is hosted publicly on GitHub (block/buzz) with docs, CLI code, and README all visible, and community discussion confirms it's treated as an open-source project ('decentralized, self-sovereign, and open source'). However, the evidence pack never explicitly states or cites a specific OSI license file/name. Missing for 10: explicit citation of the license type (e.g., Apache/MIT) confirming open-license terms, independent verification of license terms.
- [github] “Turn a feature branch into a room where patches, CI, review, and the merge decision live together — so the channel becomes the record of why…”
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [claimed-docs] “No GitHub. No Discord. No stitching five services together. The project lives in one place, and that place is yours.”
- [community] “"Excited for 'decentralized, self-sovereign, and open source.' Indifferent to 'groupchat for agents'."”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
ai-native userSelf-host the core product
weight 3 · round to BuzzMicrosoft Teamsnone0/10Microsoft Teams is a proprietary SaaS cloud service with no evidence of a self-hostable core product; all evidence describes cloud-hosted collaboration, extensibility via bots/tabs/connectors, and Azure-hosted app deployment, not self-hosting the Teams service itself.
- [claimed-docs] “Microsoft Teams delivers chat-based collaboration, meetings, calling, and enterprise voice features.”
- [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
Buzz is explicitly open source and self-hostable: docs state 'Run your own relay for one community... same OSS codebase' and 'The project lives in one place, and that place is yours,' with a public GitHub repo and CLI for setup. Missing for 10: no independent/hands-on report confirming a successful self-hosted deployment, and community comments raise skepticism about maturity/reliability rather than confirming self-hosting works in practice.
- [claimed-docs] “No GitHub. No Discord. No stitching five services together. The project lives in one place, and that place is yours.”
- [claimed-docs] “Run your own relay for one community, or let an operator host thousands on shared infrastructure — same OSS codebase, same URL-is-your-works…”
- [github] “Turn a feature branch into a room where patches, CI, review, and the merge decision live together — so the channel becomes the record of why…”
- [probe] “official CLI documented at https://github.com/block/buzz/tree/main/crates/buzz-cli”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnMicrosoft Teamsnone0/10No evidence in the pack addresses data residency, regional storage options, or geo-controls for Teams data; all evidence concerns app development, messaging features, or unrelated reliability/security complaints.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnMicrosoft Teamsnone0/10No evidence in the pack addresses opt-out or controls for AI/model-training use of Teams data; docs cover bots, agents, webhooks, and Copilot features but nothing about training-data exclusion or privacy controls for AI training.
ai-native userControl data retention and deletion
weight 2 · round to Microsoft TeamsTeams' Graph docs mention export APIs and note that user-deleted messages remain recoverable for 21 days, showing some retention/deletion behavior exists, but there is no evidence of AI-native controls (e.g., agent-specific data retention settings, deletion APIs for AI interactions, or admin policies tailored to AI usage). Missing for 10: explicit AI/agent data retention controls, user-facing deletion tools, and documentation on how AI interaction data (e.g., Copilot logs) is retained or purged.
- [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
- [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnMicrosoft Teamsnone0/10No evidence in the pack addresses telemetry opt-out or usage-tracking controls for AI-native users; the documentation excerpts cover app/agent building, messaging, webhooks, and CLI tooling, with no mention of privacy/telemetry settings. Missing for 10: any documentation of a telemetry opt-out mechanism, admin controls for usage tracking, or AI-specific data collection settings.
Search knowledge — stories about search knowledge in this arenaSearch knowledge
Stories about search knowledge in this arena
Ai catchup
ai-native userGet AI-generated summaries and recaps of channels and threads I missed
weight 2 · round drawnMicrosoft Teamsnone0/10The evidence pack contains only general platform/bot/webhook/API docs and community complaints, with no mention of AI-generated channel/thread summaries or 'catch-up' recap features (e.g., Copilot's recap capability is not cited here); nothing ties Copilot or any feature to summarizing missed conversations. Missing for 10: any documentation of a summarization/recap feature for channels or threads, independent verification of its use.
Buzznone0/10Buzz evidence focuses on agents searching history and pulling up relevant threads (buzz-gh-3, buzz-gh-5) but there's no documentation of an AI-generated summary/recap feature for channels or threads a user missed; the CLI and docs list channel creation, repo management, and workflow triggers with no summarization command or feature mentioned.
Search
team-adminSearch the full message history with filters like sender, channel, and date
weight 3 · round to BuzzMicrosoft Teamsnone0/10The evidence pack contains no vendor documentation of an admin-facing search feature with sender/channel/date filters — only generic Export APIs for compliance extraction (ms-teams-docs-13,14), which do not describe search/filter UI. Community reports explicitly complain that Teams search cannot filter Files by type or search within a channel and results can't be sorted (ms-teams-comm-11) and that 'search is abysmal' (ms-teams-comm-8), reinforcing the lack of evidence for this capability.
- [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
- [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”
- [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”
- [community] “Detailed complaint: search is abysmal, messages go missing in 1:1 chats, images fail to display, notifications get lost, and the app window …”
Buzz claims agents can 'search six months of history' and 'search the conversation, patch, workflow run, and approval in one place,' implying a search capability across history, but no evidence describes structured filters like sender, channel, or date, nor a team-admin-specific search UI or command. missing for 10: documented filter parameters (sender/channel/date), admin-facing search tool or CLI command, independent confirmation of filter functionality.
Workflow automation — stories about workflow automation in this arenaWorkflow automation
Stories about workflow automation in this arena
Workflow builder
team-adminBuild no-code workflows triggered by events, schedules, or form submissions inside the chat tool
weight 3 · round drawnMicrosoft Teamsnone0/10Evidence pack covers developer-oriented bots, connectors, webhooks, and the Agents Toolkit CLI, all of which require coding/deployment rather than a no-code, admin-facing workflow builder triggered by events/schedules/forms; there is no mention of a no-code automation surface (e.g., Power Automate/Workflows app) inside Teams chat.
Buzznone0/10Evidence shows Buzz has developer-oriented 'workflows' tied to CI/CD and code review (e.g., 'buzz workflows trigger/approve' CLI commands, 'run workflows' in agent capabilities) but nothing describing a no-code workflow builder for team-admins with triggers from events, schedules, or form submissions. This is a CLI/agent-driven automation surface, not a no-code admin tool.
- [github] “open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels”
- [claimed-docs] “buzz workflows trigger --workflow buzz workflows approve --token”
Not comparable on these axes
team-adminKeep my team on a free tier without losing access to older message history
weight 2 · not comparableMicrosoft Teamsnone0/10No evidence in the pack addresses free-tier message history retention policies, retention limits, or admin controls for preserving history without upgrading; the pack covers bots, agents, APIs, webhooks, and general complaints, none of which touch pricing-tier history retention.
Buzzn/aBuzz is an open-source, self-hosted team chat/dev platform with no evidence of a tiered pricing model, free/paid plans, or message-history retention limits tied to subscription tier — this pricing-limits axis is a category error for a self-hosted OSS project rather than a SaaS product with plan tiers.