GitHub Copilot vs Slate

Agent access

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

   weight 2 · round to Slate
   GitHub Copilot~partialprobed6/10

   Probes confirm docs.github.com serves an llms.txt file and a .md-formatted docs page, meaning an agent pointed at docs.github.com could consume agent-oriented docs directly; GitHub also documents MCP server usage for structured context. However, there's no evidence Copilot itself is documented to consume llms.txt as part of its own context-gathering workflow, nor first-party guidance recommending llms.txt for agent use. missing for 10: explicit product documentation instructing users/agents to point Copilot at llms.txt, and independent confirmation this integration is actually used in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.github.com/llms.txt # GitHub Docs > GitHub is a developer platform for building, shipping, and mai…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.github.com/copilot.md # GitHub Copilot documentation You can use GitHub Copilot to enhance your pro…”
   • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
   • [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”

   proof ↗⚑ flag

   Slate✓fullprobed8/10

   A probe confirms Slate's docs site serves a valid llms.txt at the root with links to actual docs pages, directly satisfying the ability to point an agent at agent-oriented docs. Missing for 10: no independent/community confirmation that agents successfully consume this llms.txt in practice, and no broader agent-oriented doc format beyond the single file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.randomlabs.ai/llms.txt # Slate ## Docs - [Introduction](https://docs.randomlabs.ai/en/getting-sta…”

   proof ↗⚑ flag

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

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialprobed7/10

   GitHub Copilot ships a CLI for terminal/headless use and a 'cloud agent' with 'automations' that can run on a schedule or in response to repo events (e.g., issue opened), plus isolated cloud/local sandboxes for execution — all of which enable non-interactive, CI-like automation. However, evidence doesn't show explicit CI pipeline (e.g., GitHub Actions) integration steps or a documented non-interactive/scriptable flag set for true headless scripting. Missing for 10: documented CI/Actions integration examples, explicit non-interactive/headless CLI flags, and independent hands-on confirmation of automation running unattended in CI.

   • [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [probe] “official CLI documented at https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli”

   proof ↗⚑ flag

   Slate—none0/10

   The docs describe Slate as an interactive terminal agent (onboarding, slash commands, hotkeys, subagent cards) with a permission-bypass flag (--dangerously-skip-permissions/--yolo), but there is no mention of a headless mode, non-interactive CLI flags, exit-code/scriptable output, or CI integration examples. Missing for 10: documented headless/non-interactive invocation, CI pipeline examples, scriptable output format, and any evidence of automation use outside the interactive TUI.

   • [claimed-docs] “We support `--dangerously-skip-permissions` (alias: `--yolo`) to bypass permission prompts.”
   • [claimed-docs] “npm i -g @randomlabs/slate”
   • [claimed-docs] “Use `/sessions` to switch between existing sessions”

   proof ↗⚑ flag

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

   weight 3 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed9/10

   GitHub Copilot documents direct MCP server integration: connecting MCP servers to Copilot Chat to extend context/tools, creating custom MCP servers, using the official GitHub MCP server, and admin controls (allow lists) for which MCP servers developers can access. This is well-documented first-party capability across IDE and chat surfaces. missing for 10: independent hands-on community verification of MCP tool usage in practice (community evidence pack is mostly about code suggestion quality/licensing, not MCP specifically).

   • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
   • [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
   • [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
   • [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
   • [claimed-docs] “Copilot works where you do—in GitHub, your IDE, the CLI, project tools, chat apps, and custom MCP servers.”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence in the pack mentions MCP servers or integrating external tool providers into Slate; the docs cover skills, permissions, orchestration, and CLI usage but never MCP support. Missing for 10: any documentation or claim about connecting/plugging in MCP servers, configuring MCP tool sources, or using MCP-provided tools.

   ⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   GitHub Copilot✓fullprobed8/10

   GitHub Copilot ships an official CLI documented at docs.github.com, letting users invoke Copilot directly from the terminal with prompt/voice input, corroborated by a dedicated install guide probe. missing for 10: independent hands-on community review of the CLI itself (community evidence only covers older chat/agent features, not the CLI), and no detail on CLI feature parity with IDE agent mode.

   • [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
   • [claimed-docs] “As an alternative to typing, you can speak your prompt.”
   • [probe] “official CLI documented at https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli”
   • [claimed-docs] “GitHub Copilot is also supported in terminals through GitHub CLI and as a chat integration in Windows Terminal Canary.”

   proof ↗⚑ flag

   Slate✓fullprobed8/10

   Slate is delivered as an official CLI (npm-installed, terminal-based) with rich first-party docs covering install, sessions, hotkeys, shell execution, and configuration — squarely matching the 'official CLI' story for an AI-native user. Missing for 10: independent/hands-on corroboration of the CLI experience itself (community evidence found only relates to unrelated porting-quality claims, not CLI usage).

   • [claimed-docs] “npm i -g @randomlabs/slate”
   • [claimed-docs] “Use `/sessions` to switch between existing sessions”
   • [claimed-docs] “Press Tab to queue the current message so it runs after the current turn finishes.”
   • [claimed-docs] “Execute shell commands directly with `!`”
   • [claimed-docs] “Ctrl+X then N New session”
   • [probe] “official CLI documented at https://docs.randomlabs.ai/en/getting-started/quickstart”

   proof ↗⚑ flag

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

   weight 3 · round to GitHub Copilot
   GitHub Copilot~partialprobed3/10

   GitHub Copilot ships a documented CLI (docs-26, probe-4) that lets scripts/agents invoke Copilot from a terminal, and Copilot Chat can be extended via MCP servers (docs-20/21/25), giving some programmatic hooks. However, an explicit probe for a standard OpenAPI/public API spec returned 404s (probe-3), and no REST/GraphQL API for driving Copilot itself is documented in the evidence. Missing for 10: a dedicated, versioned public API (REST/GraphQL/OpenAPI) for programmatically controlling Copilot beyond CLI/MCP, and independent confirmation of its stability/coverage.

   • [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
   • [probe] “official CLI documented at https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli”
   • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
   • [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”

   proof ↗⚑ flag

   Slate—none0/10

   Slate is documented as a CLI/terminal agent with configuration, skills, and hotkeys, but there is no evidence of a documented public API for programmatic/agentic access—the OpenAPI probe returned 404 across all candidate paths and no SDK or REST/API docs are mentioned anywhere in the pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.randomlabs.ai/openapi.json, https://docs.randomlabs.ai/swagger.json, https://docs.rando…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.randomlabs.ai/llms.txt # Slate ## Docs - [Introduction](https://docs.randomlabs.ai/en/getting-sta…”

   proof ↗⚑ flag

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

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialclaimed3/10

   Evidence shows governance-adjacent controls like MCP server allow lists and a central control plane with audit logs for managing agents (docs-10, docs-23), but there is no explicit documentation of issuing scoped or least-privilege API credentials/tokens specifically for an agent's actions. Missing for 10: explicit scoped API credential/token issuance mechanism for agents, fine-grained permission scoping documentation, and independent verification that these controls limit agent API access at a credential level rather than just access-list level.

   • [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
   • [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”

   proof ↗⚑ flag

   Slate—none0/10

   Slate is a coding-agent CLI; its evidence only covers permission settings (allow/ask/deny) for tool actions, not issuance of scoped/least-privilege API credentials or tokens for agents. No mention of credential/token scoping, API key generation, or IAM-style access control.

   • [claimed-docs] “Each permission key maps to an action ("allow", "ask", or "deny"), or a pattern object for fine-grained control.”
   • [claimed-docs] “We support `--dangerously-skip-permissions` (alias: `--yolo`) to bypass permission prompts.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialclaimed4/10

   Evidence shows extensibility surfaces (MCP server integration, custom agents, partner 'agent apps') that let developers build on top of Copilot, but there is no dedicated official SDK (e.g., language client libraries or API SDK docs) described in the pack. missing for 10: explicit official SDK/client-library docs, code samples for building third-party apps against a Copilot API, independent developer confirmation of SDK usage.

   • [claimed-docs] “Agent apps let you use partner-built agents directly in your workflows on GitHub, powered by your Copilot subscription.”
   • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
   • [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
   • [claimed-docs] “Custom agents allow you to tailor Copilot's expertise for specific tasks.”

   proof ↗⚑ flag

   Slate—none0/10

   The evidence pack covers Slate's CLI, skills, configuration, and orchestration features but contains no mention of an official SDK (Python/TypeScript/etc.) for building applications on top of Slate, and the OpenAPI probe returned 404s across all candidate paths. Missing for 10: any documented SDK package, API reference, or programmatic interface for building against Slate.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.randomlabs.ai/openapi.json, https://docs.randomlabs.ai/swagger.json, https://docs.rando…”
   • [claimed-docs] “npm i -g @randomlabs/slate”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to GitHub Copilot
   GitHub Copilot✓fullcommunity8/10

   Copilot generates AI insights/suggestions from the user's own code and repository data via code completion, chat with repo/doc context, code review with severity-labeled comments, and Autofix vulnerability suggestions, and can pull context from GitHub issues/PRs/docs via MCP. Community anecdotes (comm-1, comm-6, comm-7) corroborate real productivity gains from these suggestions, though some criticize suggestion quality on edge cases (comm-2, comm-10). Missing for 10: independent benchmark data quantifying insight accuracy/usefulness and no first-party analytics-style 'insights dashboard' beyond code review/Autofix.

   • [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”
   • [claimed-docs] “GitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code”
   • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
   • [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
   • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
   • [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
   • [community] “I've been using the alpha for the past 2 weeks, and I'm blown away. Copilot guesses the exact code I want about one in ten times... when it …”
   • [community] “I have absolutely loved copilot so far. I especially love how fast it handles indexing complex n-dimensional arrays... I'd estimate a 10% ve…”
   • [community] “Yesterday, Copilot could not write a program with SymPy... Today it uses SymPy as well as it uses NumPy (occasional mistakes, but overall it…”

   proof ↗⚑ flag

   Slate~partialcommunity4/10

   Slate is a coding-agent CLI whose evidence shows it can analyze a codebase and produce suggestions (e.g., generating an ARCH.md with improvement ideas), which maps loosely to 'AI-generated insights from data' but only in the narrow sense of source code, not general data analysis. Community evidence also raises skepticism about the real quality of generated output (e.g., criticism of a ported-code example as low quality/unverified). Missing for 10: evidence of insights/suggestions over non-code datasets, dashboards or analytics-style outputs, and independent validation of suggestion quality.

   • [claimed-docs] “Please review the architecture of my entire codebase creating an ARCH.md and then give me ways I can improve it.”
   • [community] “Blog post claimed porting a library with one sentence, but critic noted it was JS->TS (trivial rename) not Python->TS, excluded tests/exampl…”
   • [community] “"Why trumpet code that is so ready for the garbage that you wouldn't even bother to publish it" - skepticism about the quality/usefulness of…”

   proof ↗⚑ flag

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

   weight 2 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   GitHub Copilot's cloud agent explicitly supports background automation: docs describe running Copilot 'automatically, on a schedule or in response to events in a repository' and working 'independently in the background to complete tasks, just like a human developer,' with a control plane to track multiple agent sessions. This directly matches the story of autonomous background automations for an AI-native user. Missing for 10: independent/community hands-on validation specifically of the scheduled/event-triggered automation feature (most community evidence is about code completion quality, not the cloud-agent automation flow).

   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”

   proof ↗⚑ flag

   Slate~partialclaimed5/10

   Slate supports background subagents, parallel task orchestration, and built-in workflows like goal/deep-research that run while the user keeps interacting, which shows some autonomous background execution. However, this is task-level parallelism within an active session, not scheduled or trigger-based automations that run independently of user presence. missing for 10: evidence of scheduled/cron-like automations, persistent background jobs surviving session end, or trigger-based (event-driven) autonomous runs without an active user session.

   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “`goal` and `deep-research` are built-in programs. They are user-visible workflows, not something you need to author before using Slate.”

   proof ↗⚑ flag

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

   weight 3 · round to GitHub Copilot
   GitHub Copilot✓fullcommunity9/10

   GitHub Copilot ships extensive built-in agentic capabilities: agent mode in editors, cloud/background agents that plan-explore-execute autonomously, @copilot mentions on PRs, automations, custom agents, and a CLI, all documented first-party. Community evidence corroborates hands-on usage of the assistant delivering real productivity gains, supporting the delegation story. Missing for 10: independent hands-on validation specifically of the newer autonomous cloud-agent/background task delegation (most community evidence predates these agentic features).

   • [claimed-docs] “Edit files in your workspace in agent mode”
   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [community] “I have absolutely loved copilot so far. I especially love how fast it handles indexing complex n-dimensional arrays... I'd estimate a 10% ve…”
   • [community] “Yesterday, Copilot could not write a program with SymPy... Today it uses SymPy as well as it uses NumPy (occasional mistakes, but overall it…”

   proof ↗⚑ flag

   Slate✓fullcommunity7/10

   Slate is a CLI-based AI assistant where users delegate whole tasks (e.g., 'review architecture and write ARCH.md') and it spins up parallel subagents, orchestration programs like goal/deep-research, and long multi-hour sessions per first-party docs. Community evidence (comm-1/2/3) raises skepticism about output quality/novelty but does not contradict the core delegation mechanism itself. Missing for 10: independent hands-on validation that delegated multi-agent tasks reliably complete as advertised.

   • [claimed-docs] “Parallelize working and orchestration of many tasks at once.”
   • [claimed-docs] “Please review the architecture of my entire codebase creating an ARCH.md and then give me ways I can improve it.”
   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “`goal` and `deep-research` are built-in programs. They are user-visible workflows, not something you need to author before using Slate.”
   • [community] “"Why trumpet code that is so ready for the garbage that you wouldn't even bother to publish it" - skepticism about the quality/usefulness of…”

   proof ↗⚑ flag

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

   weight 2 · round to GitHub Copilot
   GitHub Copilot✓fullcommunity8/10

   GitHub Copilot offers natural-language interaction across chat, agent mode, CLI, and even voice input, letting users direct edits, reviews, and autonomous tasks conversationally (docs-2, docs-22, docs-26, docs-27). Community evidence corroborates real usage of chat/agent workflows, though some report chat availability limited to specific IDEs and mixed quality of autonomous 'fix the bug' style commands. Missing for 10: independent hands-on validation of natural-language command robustness across all surfaces (mobile, terminal) and no rigorous benchmark of command success rate.

   • [claimed-docs] “Edit files in your workspace in agent mode”
   • [claimed-docs] “chat functionality is currently available only in Visual Studio Code, JetBrains, and Visual Studio”
   • [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
   • [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
   • [claimed-docs] “As an alternative to typing, you can speak your prompt.”
   • [community] “The first video in this post is a perfect example of the problems I see in this space. First the programmer asks the AI to nebulously 'fix t…”

   proof ↗⚑ flag

   Slate✓fullclaimed7/10

   Docs show Slate is driven primarily via natural-language prompts (e.g. the quickstart example 'Please review the architecture of my entire codebase...') alongside slash-commands, shell escapes, and file references, indicating natural-language is the core interaction mode for an AI-native agent CLI. Missing for 10: independent/hands-on confirmation that complex natural-language commands are reliably parsed and executed as intended (community evidence only discusses code-porting quality, not NL command usage itself).

   • [claimed-docs] “Please review the architecture of my entire codebase creating an ARCH.md and then give me ways I can improve it.”
   • [claimed-docs] “Execute shell commands directly with `!`”
   • [claimed-docs] “Use `@filename` references”
   • [claimed-docs] “Use `/sessions` to switch between existing sessions”
   • [claimed-docs] “`goal` and `deep-research` are built-in programs. They are user-visible workflows, not something you need to author before using Slate.”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   GitHub Copilot—none0/10

   The evidence pack shows explicit probe attempts to find an OpenAPI/machine-readable spec for GitHub Copilot's docs (openapi.json, swagger.json, etc.) all returning 404, and no other citation mentions a downloadable API spec for Copilot. No documentation or community evidence confirms a machine-readable spec exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”

   proof ↗⚑ flag

   Slate—none0/10

   Slate's docs site was directly probed for an OpenAPI/swagger spec at standard locations and all returned 404, and no documentation anywhere mentions a machine-readable API spec for AI-native consumption.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.randomlabs.ai/openapi.json, https://docs.randomlabs.ai/swagger.json, https://docs.rando…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   GitHub Copilot—none0/10

   The evidence pack contains no documentation of a versioned API or deprecation policy for GitHub Copilot; the OpenAPI probe explicitly found all candidate spec paths returning 404, and no other citation addresses API versioning/deprecation commitments.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”

   proof ↗⚑ flag

   Slate—none0/10

   Slate is a CLI coding agent product; no evidence of any versioned public API, API reference, or deprecation policy documentation exists—openapi probes returned 404 and no docs mention API versioning or deprecation. Absence of evidence for this applicable axis (a product could plausibly document API stability) yields 'none'.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.randomlabs.ai/openapi.json, https://docs.randomlabs.ai/swagger.json, https://docs.rando…”

   proof ↗⚑ flag

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

   weight 2 · round to Slate
   GitHub Copilot~partialclaimed5/10

   Docs show Copilot can run multiple background cloud-agent sessions in parallel, track them from one control page, and trigger automations on repo events/schedules (docs-8, docs-14, docs-15, docs-33), which supports scaling to many tasks, but there's no explicit evidence of a single bulk command/batch operation (e.g., 'review 50 PRs at once' or 'fix all issues matching X') as a discrete feature. Missing for 10: an explicit bulk-action UI/API (e.g., batch PR review, batch issue triage) and independent confirmation that many items can be processed in one invocation rather than via separate parallel agent sessions.

   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”

   proof ↗⚑ flag

   Slate~partialclaimed6/10

   Docs describe running many agents in parallel and orchestrating multiple tasks simultaneously (grid of subagent cards, spinning up more agents to parallelize work), which supports bulk-style operations across many items. However, there's no independent corroboration of this working at scale and no detail on failure handling, limits, or item-level bulk operations (e.g., bulk file edits/refactors) beyond task orchestration. Missing for 10: independent/hands-on verification of large-scale parallel task execution, concrete examples of bulk item processing (files/records), and failure/error handling details at scale.

   • [claimed-docs] “Parallelize working and orchestration of many tasks at once.”
   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “`goal` and `deep-research` are built-in programs. They are user-visible workflows, not something you need to author before using Slate.”

   proof ↗⚑ flag

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

   weight 3 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   GitHub Copilot documents event/schedule-triggered automations for its cloud agent ('run Copilot cloud agent automatically, on a schedule or in response to events in a repository', 'in response to events such as an issue being opened'), plus @mention-triggered PR actions, matching the story's rule-based automatic action pattern. Missing for 10: no independent/hands-on validation of the automation reliability or examples of complex rule chains beyond schedule/issue triggers.

   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”

   proof ↗⚑ flag

   Slate—none0/10

   Slate's docs describe agent rules for permissions/behavior ordering (docs-15, docs-20) and orchestration of parallel agents (docs-12, docs-13), but there is no evidence of user-defined rules that trigger actions automatically on external events (e.g., file changes, webhooks, schedule, git events). This is a plausible axis for a coding agent (many support hooks/triggers), so absence of evidence yields none rather than na.

   • [claimed-docs] “Slate by default respects agent rules in the following order”
   • [claimed-docs] “Each permission key maps to an action ("allow", "ask", or "deny"), or a pattern object for fine-grained control.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed7/10

   GitHub Copilot docs explicitly describe 'Automations' that run the cloud agent on a schedule or in response to repository events, allowing recurring/scheduled agent workflows, plus a control page to track multiple scheduled agent sessions. This directly matches the story of scheduling recurring jobs/workflows. Missing for 10: independent/hands-on corroboration of scheduling reliability, and more detail on cron-like configuration options or failure handling.

   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”

   proof ↗⚑ flag

   Slate—none0/10

   Slate is a coding-agent CLI with orchestration/parallel-agent features and sessions, but nothing in the evidence describes scheduling recurring jobs or workflows (e.g., cron-like triggers, timed recurring runs). Orchestration docs cover on-demand parallelization, not recurrence.

   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “`goal` and `deep-research` are built-in programs. They are user-visible workflows, not something you need to author before using Slate.”

   proof ↗⚑ flag

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

   weight 1 · round to GitHub Copilot
   GitHub Copilot~partialclaimed5/10

   Copilot's cloud-agent automations produce PRs that can be reviewed (code review feature, docs-28/29) and tracked via audit logs and a central control plane (docs-23), and since output flows through Git, changes are inherently versioned and revertible via standard PR/commit mechanics. However, there is no direct evidence of a dedicated versioning or rollback mechanism for the automation definitions/schedules themselves (e.g., automation history, revert-to-previous-config). missing for 10: explicit versioning/rollback UI for automation configs, evidence of rolling back an automation run itself (not just its code output), independent confirmation of this workflow in practice.

   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
   • [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”

   proof ↗⚑ flag

   Slate—none0/10

   Evidence shows session management (/sessions, /workspace) and built-in 'programs' like goal/deep-research, but nothing about versioning automations, reviewing history of changes, or rolling back to prior states of an automation/workflow. Missing for 10: any documentation of version history, diffing, or rollback mechanisms for automations/workflows.

   • [claimed-docs] “Use `/sessions` to switch between existing sessions”
   • [claimed-docs] “Use `/workspace` to open the workspace manager, where you can review and remove workspace directories.”
   • [claimed-docs] “`goal` and `deep-research` are built-in programs. They are user-visible workflows, not something you need to author before using Slate.”

   proof ↗⚑ flag

Background execution

1. ai-native userHave a cloud agent build, test, and demo a feature end-to-end for my review

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialclaimed7/10

   Docs describe a genuine cloud agent that works independently in the background (assign tasks, plan/explore/execute), runs in isolated cloud sandboxes to interact with code/tools/filesystem, and produces PRs for review with automated code review and severity-labeled feedback — covering build, execute, and review end-to-end. However, 'testing' and 'demo' are only implied (sandbox execution, PR review) rather than explicitly documented as a testing/demo step, and there is no independent/hands-on corroboration of the cloud agent specifically completing a full feature end-to-end (community evidence predates/doesn't cover the cloud agent feature). Missing for 10: explicit test-running/verification evidence, a documented demo/preview mechanism, and independent hands-on validation of cloud agent outcomes.

   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “Access to Cloud agent and code review”
   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
   • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
   • [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”

   proof ↗⚑ flag

   Slate!disputedcontradicted4/10

   Slate's docs claim orchestration of parallel background subagents and being 'one of the few agents capable of performing integration tests manually,' suggesting it could build and test a feature autonomously, but no docs mention a 'demo' output or cloud-hosted execution environment. Community hands-on critique of an actual Slate-produced port directly contradicts the build/test claim: reviewers found the work excluded tests/examples and provided no verifiable repo, undermining confidence that Slate reliably builds+tests end-to-end for review. Missing for 10: evidence of cloud/remote execution infra, an explicit demo-generation feature, and independent confirmation that test suites are actually run and pass.

   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “Slate is one of the few agents capable of performing integration tests manually.”
   • [community] “Blog post claimed porting a library with one sentence, but critic noted it was JS->TS (trivial rename) not Python->TS, excluded tests/exampl…”
   • [community] “"Why trumpet code that is so ready for the garbage that you wouldn't even bother to publish it" - skepticism about the quality/usefulness of…”

   proof ↗⚑ flag

2. developerDelegate longer-running coding tasks to run in the background in an isolated cloud environment

   weight 3 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   Copilot cloud agent is well documented as delegating tasks to run autonomously in an isolated cloud sandbox, working independently in the background like a human developer, with scheduling/automations, a control page to track multiple sessions, and audit logs for governance. missing for 10: independent hands-on community verification of cloud agent reliability/performance (community evidence pack predates cloud agent feature and doesn't corroborate this specific capability).

   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “Access to Cloud agent and code review”
   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”

   proof ↗⚑ flag

   Slate—none0/10

   Slate's docs describe subagents running 'in the background' locally while you keep chatting and orchestration/parallelization of tasks, but there is no mention of an isolated cloud environment, remote execution sandbox, or delegation to a hosted service — everything described appears to run within the local CLI session. This axis is applicable to coding agent tools generally, but no evidence supports a cloud-isolated background execution capability for Slate.

   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “Slate works with you across long, multi-hour sessions.”
   • [claimed-docs] “Parallelize working and orchestration of many tasks at once.”

   proof ↗⚑ flag

3. developerConfigure a reproducible cloud environment with the dependencies and setup steps my repository needs

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialclaimed4/10

   Docs mention 'Cloud and local sandboxes provide isolated execution environments' for Copilot cloud agent and background task automation, implying some environment abstraction, but there is no explicit evidence of a mechanism (e.g., a setup-steps config, devcontainer, or dependency manifest) for developers to define reproducible cloud environment setup steps. Missing for 10: explicit documentation of a configuration file/workflow for specifying dependencies/setup steps, independent confirmation of reproducibility across runs.

   • [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”

   proof ↗⚑ flag

   Slate—none0/10

   Slate's docs describe a local CLI agent (npm install, terminal sessions, permissions, skills, orchestration) but contain no mention of provisioning or configuring a reproducible cloud environment, dependency setup, or devcontainer-style configuration for a repository. This is a fair capability to ask of an autonomous coding agent, but no evidence shows Slate supports it.

   • [claimed-docs] “npm i -g @randomlabs/slate”
   • [claimed-docs] “Slate by default respects agent rules in the following order”
   • [claimed-docs] “Each permission key maps to an action ("allow", "ask", or "deny"), or a pattern object for fine-grained control.”

   proof ↗⚑ flag

Parallel agents

1. ai-native userLaunch fleets of autonomous agents that work in parallel on different tasks for hours or days

   weight 2 · round to Slate
   GitHub Copilot~partialclaimed6/10

   GitHub Copilot's cloud agent supports background autonomous work, scheduled/event-triggered automations, and a control page to track and manage multiple agent sessions in parallel (docs-8, docs-14, docs-15, docs-31, docs-33), which covers the 'fleets working in parallel' concept. However, evidence doesn't confirm true multi-hour/multi-day persistent autonomous runs at scale or independent hands-on validation of large fleets; most evidence is vendor docs rather than field reports. missing for 10: independent/hands-on confirmation of long-running (hours/days) parallel agent fleets, concrete scale limits or examples of many simultaneous agents, and community verification of duration/reliability at scale.

   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”

   proof ↗⚑ flag

   Slate~partialcommunity7/10

   Docs describe genuine parallel agent orchestration (grid of subagent cards, spinning up more agents while others run in background) and explicitly support multi-hour sessions, matching much of the story. However, evidence only confirms 'multi-hour' not multi-day autonomy, and community commentary raises skepticism about output quality/novelty without directly refuting the parallel-agent mechanics themselves. Missing for 10: confirmation of multi-day unattended runs, independent hands-on validation of fleet-scale parallel task completion.

   • [claimed-docs] “Slate works with you across long, multi-hour sessions.”
   • [claimed-docs] “Parallelize working and orchestration of many tasks at once.”
   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [community] “Commenter compared the approach to 'Ralph as a service' referencing an existing agentic coding technique (ghuntley.com/ralph), suggesting Sl…”

   proof ↗⚑ flag

2. developerRun several task attempts in parallel and compare results before choosing one

   weight 1 · round to Slate
   GitHub Copilot~partialclaimed5/10

   Copilot's cloud/background agents support launching and tracking multiple agent sessions in parallel from a single control page and desktop workspace (docs-8, docs-14, docs-31), which enables running concurrent tasks. However, there's no explicit documentation of running multiple attempts of the *same* task and comparing outputs before selecting one—the evidence describes managing distinct tasks/agents, not competing solutions to a single task. Missing for 10: explicit multi-attempt-per-task workflow, UI for side-by-side comparison of alternative solutions, and any hands-on/community confirmation of this specific parallel-attempt-and-choose pattern.

   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”

   proof ↗⚑ flag

   Slate~partialclaimed6/10

   Slate's orchestration docs show multiple subagents running in parallel as a grid of cards while the user keeps working, directly supporting parallel task execution (docs-12, docs-13). However, there's no explicit documentation of a compare/diff view or a 'choose winning attempt' workflow for reconciling multiple parallel results into one choice. Missing for 10: explicit comparison/selection UI or workflow for multiple attempts of the same task, and independent/hands-on confirmation of this specific use case.

   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “`goal` and `deep-research` are built-in programs. They are user-visible workflows, not something you need to author before using Slate.”

   proof ↗⚑ flag

Scheduled automation

1. ai-native userSet up always-on agents that run on schedules or triggers to maintain and fix my software autonomously

   weight 2 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   GitHub Copilot explicitly documents scheduled/event-triggered cloud agents ('Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository') that work independently in the background, plus a control plane to track/manage multiple agent sessions and sandboxed execution environments. This directly matches the always-on, autonomous, schedule/trigger-driven maintenance story. Missing for 10: independent/hands-on verification of scheduled agent runs actually fixing software autonomously in production, and more detail on trigger types beyond issue-opened examples.

   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”

   proof ↗⚑ flag

   Slate—none0/10

   Slate's docs describe parallel subagent orchestration within a live session (background agents you keep talking to, spin up more agents to parallelize tasks) but there is no evidence of scheduling, event/webhook triggers, or persistent always-on agents that run autonomously outside an active session to maintain/fix software over time.

   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “`goal` and `deep-research` are built-in programs. They are user-visible workflows, not something you need to author before using Slate.”

   proof ↗⚑ flag

Debugging

1. developerDebug a live running web application directly from my coding assistant

   weight 1 · round drawn
   GitHub Copilot—none0/10

   Evidence covers code completion, chat, agent mode file edits, cloud agents, code review, and MCP integrations, but nothing about attaching to or debugging a live running web application (e.g., runtime inspection, breakpoints, log/trace analysis of a running process). No evidence supports this capability.

   ⚑ flag

   Slate—none0/10

   No evidence in the pack mentions debugging live running applications, attaching to running processes, browser/runtime debugging, or any live-app inspection capability; Slate's docs focus on codebase review, shell commands, orchestration, and skills, none of which address live debugging.

   ⚑ flag

2. developerDebug issues and troubleshoot using natural-language queries

   weight 2 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed7/10

   Copilot Chat explicitly supports natural-language interaction for explaining concepts, code review with prioritized issue severity, and agent mode for autonomous exploration and fixing—core debugging/troubleshooting workflows (docs-4, docs-22, docs-28, docs-29). Autofix also provides contextual explanations for vulnerabilities (docs-13), reinforcing NL-driven troubleshooting. missing for 10: a dedicated 'debug' feature description, independent hands-on evidence specifically validating debugging accuracy/success (community evidence focuses on completion quality and licensing concerns, not debugging).

   • [claimed-docs] “chat functionality is currently available only in Visual Studio Code, JetBrains, and Visual Studio”
   • [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
   • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
   • [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
   • [claimed-docs] “GitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code”

   proof ↗⚑ flag

   Slate~partialclaimed5/10

   Slate's docs show it operates via natural-language prompts, executes shell commands (`!`), references files (`@filename`), and can run integration tests and review codebase architecture in NL form, which implies it could be used for debugging and troubleshooting queries. However there is no explicit example, workflow, or documentation section dedicated to debugging/troubleshooting via natural language, and community evidence is skeptical/unrelated to this specific capability. Missing for 10: explicit debugging-focused examples or docs, independent verification that NL-based debugging works well, dedicated troubleshooting workflow beyond generic agent capabilities.

   • [claimed-docs] “Execute shell commands directly with `!`”
   • [claimed-docs] “Use `@filename` references”
   • [claimed-docs] “Slate is one of the few agents capable of performing integration tests manually.”
   • [claimed-docs] “Please review the architecture of my entire codebase creating an ARCH.md and then give me ways I can improve it.”

   proof ↗⚑ flag

Feature implementation

1. developerTurn a tracked issue into a complete pull request end-to-end

   weight 3 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   GitHub Copilot's cloud agent can be assigned directly from an issue or via @copilot mentions, working autonomously to plan, explore, execute changes, and open a pull request, with automations to trigger this on issue events; the desktop workspace lets developers track, review, and merge the resulting PR end-to-end. missing for 10: independent hands-on verification of the full issue-to-merged-PR flow (community evidence covers earlier code-completion/chat era, not cloud agent specifically) and concrete success-rate data on autonomous PR quality.

   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”

   proof ↗⚑ flag

   Slate—none0/10

   The evidence pack covers Slate's session management, orchestration, skills, and permissions but contains no mention of issue-tracker integration (e.g., GitHub issues) or automated pull-request creation/submission. Without evidence of ingesting a tracked issue and producing a PR end-to-end, this capability is unshown.

   ⚑ flag

2. developerDescribe a feature or bug in plain language and have the agent implement or fix it across multiple files

   weight 3 · round to GitHub Copilot
   GitHub Copilot✓fullcommunity8/10

   Docs describe Copilot agent mode editing files across the workspace, cloud agents that plan/explore/execute tasks autonomously (including from plain-language issue/PR descriptions via @copilot mentions), and code review/autofix capabilities, directly matching the story of describing a feature/bug and having it implemented across multiple files. Community evidence corroborates real usage of the agent for multi-file/complex code tasks, though some hands-on reports note quality limitations on nuanced 'fix the bug' requests. Missing for 10: rigorous independent benchmarking of multi-file correctness and more first-hand accounts specifically of cross-file feature implementation success/failure rates.

   • [claimed-docs] “Edit files in your workspace in agent mode”
   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
   • [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
   • [community] “The first video in this post is a perfect example of the problems I see in this space. First the programmer asks the AI to nebulously 'fix t…”

   proof ↗⚑ flag

   Slate!disputedcontradicted5/10

   Docs imply broad multi-file code work (e.g. the quickstart example asks Slate to review an entire codebase and produce ARCH.md, plus orchestration features for parallelizing tasks across files/agents), suggesting Slate can act on plain-language requests across a codebase. However, independent community scrutiny of a specific real-world claim (a 'ported library' from one sentence) found it was actually a trivial JS->TS rename, excluded tests, lacked a verifiable repo, and drew explicit skepticism about the quality/usefulness of the generated code — concretely contradicting the marketed multi-file code-generation capability. Missing for 10: first-party documentation of a genuine multi-file bug-fix/feature-implementation workflow with verifiable before/after results, and independent hands-on confirmation that resolves the community dispute.

   • [claimed-docs] “Please review the architecture of my entire codebase creating an ARCH.md and then give me ways I can improve it.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “Parallelize working and orchestration of many tasks at once.”
   • [community] “Blog post claimed porting a library with one sentence, but critic noted it was JS->TS (trivial rename) not Python->TS, excluded tests/exampl…”
   • [community] “"Why trumpet code that is so ready for the garbage that you wouldn't even bother to publish it" - skepticism about the quality/usefulness of…”

   proof ↗⚑ flag

Maintenance automation

1. developerHave the agent write tests, fix lint errors, resolve merge conflicts, and update dependencies for me

   weight 3 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   Copilot's agent mode edits files, validates changes, and can autonomously plan/execute tasks (docs-2,3,22,31), code review with severity-labeled feedback and suggested fixes covers lint/quality issues (docs-28,29), and @copilot on PRs plus cloud agent covers merge conflict resolution and general code changes (docs-32). Dependency updates and explicit test-writing aren't separately documented as named features, so this is inferred from general-purpose agent code editing rather than a dedicated capability. missing for 10: explicit documented examples of writing tests, resolving merge conflicts, and updating dependencies as named use cases, and independent hands-on confirmation of these specific tasks.

   • [claimed-docs] “Edit files in your workspace in agent mode”
   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
   • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
   • [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”

   proof ↗⚑ flag

   Slate~partialcommunity3/10

   Slate is documented as a general-purpose coding agent with shell execution, file editing, permissioning, and orchestration of multiple sub-agents (random-labs-docs-9, random-labs-docs-13, random-labs-docs-16), which implies it could perform tasks like running tests or lint/dependency commands, but the evidence never explicitly documents test-writing, lint-fixing, merge-conflict resolution, or dependency updates as capabilities. Community commentary raises quality concerns about generated code but doesn't specifically address these tasks. Missing for 10: explicit documentation or examples of writing/fixing tests, resolving lint errors, resolving merge conflicts, and updating dependencies.

   • [claimed-docs] “Execute shell commands directly with `!`”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “Slate is one of the few agents capable of performing integration tests manually.”
   • [community] “"Why trumpet code that is so ready for the garbage that you wouldn't even bother to publish it" - skepticism about the quality/usefulness of…”

   proof ↗⚑ flag

Multimodal generation

1. ai-native userGenerate a working app from a sketch, image, or PDF design

   weight 2 · round drawn
   GitHub Copilot—none0/10

   No evidence that Copilot can take a sketch, image, or PDF design and generate a working app from it; documentation focuses on code completion, chat, agent mode, cloud agents, and MCP integration, with no mention of image/PDF-to-code or multimodal design-to-app generation.

   ⚑ flag

   Slate—none0/10

   The evidence describes Slate as a terminal-based CLI agent for coding sessions, orchestration, skills, and permissions, but nothing in the docs or community evidence mentions accepting sketches, images, or PDF designs as input to generate an app. missing for 10: any mention of image/sketch/PDF input, multimodal design-to-code capability, or UI mockup ingestion.

   • [claimed-docs] “npm i -g @randomlabs/slate”
   • [claimed-docs] “Please review the architecture of my entire codebase creating an ARCH.md and then give me ways I can improve it.”
   • [claimed-docs] “Skills are markdown instruction packages that give the agent domain-specific knowledge and behavior.”
   • [claimed-docs] “description: "Create distinctive, production-grade frontend interfaces."”

   proof ↗⚑ flag

Codebase mapping

1. developerUnderstand how a codebase fits together to find where to start making changes

   weight 3 · round drawn
   GitHub Copilot~partialclaimed5/10

   Copilot Chat in the editor is documented to explain concepts and provide context-aware help (docs-22), and enterprise features let teams build a 'shared source of truth' from docs and repos (docs-9) plus MCP integrations that pull in repo/issue/PR context (docs-20, docs-21, docs-25), all of which support exploring an unfamiliar codebase. However, there is no explicit feature description of codebase-wide indexing, dependency/architecture mapping, or a dedicated 'explain this repo' capability, and no hands-on community evidence confirming it helps developers orient in large codebases. Missing for 10: dedicated codebase-mapping/semantic search feature docs, explicit onboarding/architecture-understanding use case, and independent corroboration of effectiveness.

   • [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
   • [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”
   • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
   • [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
   • [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”

   proof ↗⚑ flag

   Slate~partialclaimed5/10

   The quickstart example explicitly shows Slate producing an ARCH.md architecture review of an entire codebase with improvement suggestions, directly supporting codebase-understanding use cases, and @filename references plus workspace management help navigate a repo. However there's no dedicated codebase-mapping/search feature (e.g., symbol index, dependency graph) documented beyond this one example, and no independent evidence confirming quality of such architecture summaries. missing for 10: dedicated code-navigation/search tooling, independent validation of architecture-summary accuracy, more than a single example of codebase-understanding workflow.

   • [claimed-docs] “Please review the architecture of my entire codebase creating an ARCH.md and then give me ways I can improve it.”
   • [claimed-docs] “Use `@filename` references”
   • [claimed-docs] “Use `/workspace` to open the workspace manager, where you can review and remove workspace directories.”

   proof ↗⚑ flag

2. developerHave the agent map and explain an entire unfamiliar codebase without manually selecting context files

   weight 3 · round to Slate
   GitHub Copilot~partialclaimed5/10

   Copilot's agent mode and cloud agent are documented to 'plan, explore, and execute work autonomously' across a repo, and 'skills' let it perform specialized tasks, implying some autonomous codebase exploration without hand-picked files, but there's no explicit doc describing a whole-codebase 'map and explain' capability. missing for 10: dedicated codebase-mapping/explanation feature docs, evidence of automatic whole-repo context gathering without manual file selection, and independent hands-on confirmation of this specific workflow.

   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”
   • [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”

   proof ↗⚑ flag

   Slate~partialcommunity6/10

   Docs show Slate's quickstart example explicitly demonstrates asking it to 'review the architecture of my entire codebase' and generate an ARCH.md without manual file selection, and it has orchestration/subagent features for broad exploration. However there's no independent/hands-on verification that this codebase-mapping actually works well on large unfamiliar repos, and community evidence raises quality skepticism about other generated outputs. missing for 10: independent hands-on validation of full-codebase mapping accuracy, evidence of handling very large/unfamiliar codebases without manual curation, detail on how context is auto-selected under the hood.

   • [claimed-docs] “Please review the architecture of my entire codebase creating an ARCH.md and then give me ways I can improve it.”
   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [community] “"Why trumpet code that is so ready for the garbage that you wouldn't even bother to publish it" - skepticism about the quality/usefulness of…”

   proof ↗⚑ flag

Context management

1. developerHave the agent build and recall memory automatically across sessions

   weight 2 · round drawn
   GitHub Copilot—none0/10

   The evidence pack describes agent mode, cloud agents, MCP context, and code review, but nothing about persistent memory that is automatically built and recalled across sessions—closest is a static 'shared source of truth' repository doc feature, not agent-built memory.

   • [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”

   proof ↗⚑ flag

   Slate—none0/10

   Docs describe session switching (/sessions), long multi-hour session support, and diagnostic context attachment, but there is no evidence of automatic cross-session memory building or recall — sessions appear to be manually selected/switched contexts, not an automatic memory system. Missing for higher verdict: any documentation of persistent memory storage, automatic recall of past codebase context, or memory summarization across sessions.

   • [claimed-docs] “Slate works with you across long, multi-hour sessions.”
   • [claimed-docs] “Use `/sessions` to switch between existing sessions”
   • [claimed-docs] “Slate automatically attaches relevant diagnostic information (OS, version, session context) to your report.”

   proof ↗⚑ flag

2. developerInclude multiple project directories in a single session for broader context

   weight 2 · round to Slate
   GitHub Copilot—none0/10

   The evidence pack describes agent mode, chat, MCP integrations, and cloud agents, but contains no mention of including multiple project directories/folders in a single Copilot session for broader context. Missing for 10: any documentation of multi-root workspace support, cross-directory indexing, or explicit multi-project context sharing in one session.

   ⚑ flag

   Slate~partialclaimed6/10

   Docs mention a `/workspace` manager for reviewing and removing 'workspace directories' (plural), implying support for multiple project directories in one session, but there's no detailed documentation on how directories are added or how context is merged across them, and no independent/hands-on confirmation. Missing for 10: explicit instructions/examples for adding multiple directories, and independent verification that broader multi-directory context actually works in practice.

   • [claimed-docs] “Use `/workspace` to open the workspace manager, where you can review and remove workspace directories.”

   proof ↗⚑ flag

3. developerAdd a project instructions file to set coding standards and conventions the agent follows

   weight 3 · round to Slate
   GitHub Copilot~partialclaimed4/10

   Docs mention 'creating a shared source of truth that includes context from your docs and repositories' to keep teams consistent (github-copilot-docs-9), which gestures at instructions/knowledge-context features, but the evidence pack never explicitly describes a project instructions file (e.g., copilot-instructions.md) or how coding standards/conventions are set and enforced. Missing for 10: explicit documentation of an instructions file mechanism, its scope/format, and confirmation the agent follows it during edits/completions.

   • [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”

   proof ↗⚑ flag

   Slate~partialclaimed6/10

   Docs confirm Slate 'respects agent rules' in a defined precedence order and supports Skills (markdown instruction packages, including Claude Code-compatible `.claude/skills/` paths), which cover project-level conventions/instructions, but there's no explicit example of a single top-level 'instructions file' analogous to AGENTS.md/CLAUDE.md being demonstrated end-to-end. missing for 10: explicit naming/format of the project instructions file, a worked example showing the agent following custom conventions from it, and independent/community confirmation it works as documented.

   • [claimed-docs] “Slate by default respects agent rules in the following order”
   • [claimed-docs] “Skills are markdown instruction packages that give the agent domain-specific knowledge and behavior.”
   • [claimed-docs] “`.claude/skills/` | Claude Code compatibility”

   proof ↗⚑ flag

Issue diagnosis

1. developerReproduce issues, narrow down root causes, and verify fixes

   weight 3 · round to GitHub Copilot
   GitHub Copilot~partialclaimed5/10

   Copilot's agent mode and chat can propose edits and 'validate files' (docs-22), Autofix explains and suggests fixes for vulnerabilities (docs-13), and code review flags issues with severity (docs-28/29), which together support parts of root-cause analysis and fix verification, but there is no explicit documentation of reproducing bugs, running/debugging tests, or a dedicated root-cause investigation workflow. missing for 10: explicit reproduction-of-issue workflow, test-execution/debugging tooling, and independent hands-on evidence of root-cause narrowing.

   • [claimed-docs] “GitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code”
   • [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
   • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
   • [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
   • [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”

   proof ↗⚑ flag

   Slate~partialclaimed4/10

   Slate documents shell execution (`!`), file references, and being 'one of the few agents capable of performing integration tests manually,' which are plausible building blocks for debugging workflows, but there's no explicit documentation of a reproduce→diagnose→verify-fix workflow. Missing for 10: explicit debugging/root-cause-analysis workflow documentation, evidence of test-driven verification loops, and independent hands-on confirmation that Slate helps developers actually reproduce and fix bugs.

   • [claimed-docs] “Slate is one of the few agents capable of performing integration tests manually.”
   • [claimed-docs] “Execute shell commands directly with `!`”
   • [claimed-docs] “Use `@filename` references”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”

   proof ↗⚑ flag

Marketplace

1. developerEquip the agent with custom skills to perform specialized tasks

   weight 1 · round to Slate
   GitHub Copilot✓fullclaimed6/10

   Docs explicitly describe a 'Skills' feature ('Skills allow Copilot to perform specialized tasks') and 'Custom agents' that let developers tailor Copilot's expertise, plus MCP server extensibility to add custom tools/context. This directly matches the story of equipping the agent with custom skills, though details are thin. Missing for 10: concrete developer walkthrough of creating a skill, independent/hands-on confirmation of using custom skills, and richer documentation depth beyond a single-line description.

   • [claimed-docs] “Skills allow Copilot to perform specialized tasks.”
   • [claimed-docs] “Custom agents allow you to tailor Copilot's expertise for specific tasks.”
   • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
   • [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”

   proof ↗⚑ flag

   Slate✓fullclaimed7/10

   Slate has a documented Skills system: markdown instruction packages that give the agent domain-specific knowledge/behavior, with example skill definitions and compatibility with Claude Code's `.claude/skills/` format, letting developers equip the agent with custom specialized capabilities. Missing for 10: independent/hands-on verification that custom skills work as documented, and more detail on skill authoring/discovery beyond the single example.

   • [claimed-docs] “Skills are markdown instruction packages that give the agent domain-specific knowledge and behavior.”
   • [claimed-docs] “description: "Create distinctive, production-grade frontend interfaces."”
   • [claimed-docs] “`.claude/skills/` | Claude Code compatibility”

   proof ↗⚑ flag

2. engineering-leadIntegrate third-party partner-built agent apps into my workflows

   weight 1 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   Docs explicitly describe 'Agent apps' that let partner-built agents be used directly in GitHub workflows powered by Copilot subscription, plus assigning tasks to third-party agents (Claude, OpenAI Codex) and MCP server integration for extending Copilot with external tools. Missing for 10: independent/hands-on verification of partner agent app integrations and detail on governance/setup friction beyond first-party docs.

   • [claimed-docs] “Agent apps let you use partner-built agents directly in your workflows on GitHub, powered by your Copilot subscription.”
   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
   • [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
   • [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”

   proof ↗⚑ flag

   Slate—none0/10

   Slate is a coding CLI agent focused on subagents, skills, sessions, and model orchestration; there is no evidence of an ecosystem for integrating third-party partner-built agent apps (e.g., a marketplace, app store, or partner integration framework). Skills compatibility with Claude Code is mentioned but that is file-format compatibility, not partner app integration.

   • [claimed-docs] “Skills are markdown instruction packages that give the agent domain-specific knowledge and behavior.”
   • [claimed-docs] “`.claude/skills/` | Claude Code compatibility”

   proof ↗⚑ flag

Team knowledge

1. engineering-leadCreate a shared workspace from my docs and repos as a common source of truth for the team

   weight 1 · round to GitHub Copilot
   GitHub Copilot~partialclaimed5/10

   Docs explicitly claim the ability to 'scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories,' directly matching the story, and related enterprise-governance features (control planes, audit logs, MCP allow-lists) support team-wide consistency. However, this is a single vendor-claimed line item with no elaboration on setup, structure, or how it functions as a 'workspace,' and no independent/hands-on evidence corroborates it. Missing for 10: independent verification, concrete workflow/UI details, and community confirmation that teams actually use this as a shared source of truth.

   • [claimed-docs] “Scale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
   • [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”

   proof ↗⚑ flag

   Slate—none0/10

   Slate is a CLI coding agent focused on individual sessions, workspaces (local directories), skills, and orchestration of subagents—there is no evidence of a shared team workspace or collaborative source-of-truth feature built from docs and repos. The 'workspace' concept here refers to local directory management (/workspace), not a shared team hub.

   • [claimed-docs] “Use `/workspace` to open the workspace manager, where you can review and remove workspace directories.”
   • [claimed-docs] “Slate by default respects agent rules in the following order”
   • [claimed-docs] “Skills are markdown instruction packages that give the agent domain-specific knowledge and behavior.”

   proof ↗⚑ flag

Tool integration

1. developerConnect the agent to workflow tools like Jira, Slack, and Google Drive to extend its context

   weight 3 · round to GitHub Copilot
   GitHub Copilot~partialclaimed5/10

   Copilot supports connecting to external tools via MCP servers (docs-10, docs-20, docs-21, docs-25, docs-35), and states it can create custom MCP servers for specific needs, which theoretically enables Jira/Slack/Google Drive integration. However, no evidence names first-party or documented connectors for Jira, Slack, or Google Drive specifically. missing for 10: named official integrations or docs referencing Jira/Slack/Google Drive, independent confirmation these connectors work in practice.

   • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”
   • [claimed-docs] “You can create a new MCP server to fulfill your specific needs, and then integrate it with Copilot Chat.”
   • [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
   • [claimed-docs] “Copilot works where you do—in GitHub, your IDE, the CLI, project tools, chat apps, and custom MCP servers.”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence anywhere in the docs pack mentions integrations with Jira, Slack, Google Drive, or any workflow tools/MCP connectors; the docs focus on CLI usage, sessions, skills, and permissions with no mention of external tool connectivity.

   ⚑ flag

2. developerKick off agent tasks directly from GitHub, GitLab, Linear, or Slack

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialclaimed4/10

   Docs clearly show agent tasks can be kicked off from GitHub itself (mentioning @copilot on a PR, automations triggered by repo events, cloud agent background execution), and Copilot is described as working across 'chat apps' generically, but no evidence specifically documents launching agent tasks from GitLab, Linear, or Slack. Missing for 10: explicit GitLab integration, explicit Linear integration, explicit Slack integration for triggering agent tasks.

   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [claimed-docs] “Copilot works where you do—in GitHub, your IDE, the CLI, project tools, chat apps, and custom MCP servers.”
   • [claimed-docs] “Agent apps let you use partner-built agents directly in your workflows on GitHub, powered by your Copilot subscription.”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence of any integration with GitHub, GitLab, Linear, or Slack for triggering agent tasks; Slate's documentation covers CLI usage, sessions, skills, and configuration but nothing about ecosystem/platform triggers.

   ⚑ flag

Cross device continuity

1. developerStart a task on one device and continue it later from another device or browser

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialclaimed7/10

   Copilot's cloud agent and control-plane features (docs-8, docs-14, docs-31-33) let a developer assign a task to an agent from GitHub or an IDE and later check progress or continue via GitHub.com's centralized control page or desktop workspace, which is inherently accessible cross-device/browser. However, this is inferred from the cloud-agent architecture rather than an explicit 'continue from another device' claim, and there's no independent/hands-on confirmation of seamless handoff. Missing for 10: explicit documentation of cross-device session continuation and independent verification that state/context truly persists and is resumable identically on a different machine or browser.

   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”

   proof ↗⚑ flag

   Slate—none0/10

   Docs show session management within Slate (e.g. `/sessions` to switch sessions, `Ctrl+X N` for new session) but only describe local session switching, not any cloud sync or cross-device/browser continuation mechanism. Slate appears to be a terminal-only CLI tool with no mention of a browser interface or account-based sync for resuming tasks elsewhere.

   • [claimed-docs] “Use `/sessions` to switch between existing sessions”
   • [claimed-docs] “Ctrl+X then N New session”
   • [claimed-docs] “npm i -g @randomlabs/slate”

   proof ↗⚑ flag

Ide integration

1. developerChat with the coding assistant directly inside my IDE for contextual help

   weight 3 · round to GitHub Copilot
   GitHub Copilot✓fullcommunity9/10

   Docs confirm Copilot Chat is built into VS Code, JetBrains, and Visual Studio for contextual in-IDE chat (explaining concepts, proposing edits, agent mode), and community feedback corroborates real usage inside the editor. Missing for 10: independent hands-on report specifically about the chat UX (most community evidence focuses on completions, not chat).

   • [claimed-docs] “chat functionality is currently available only in Visual Studio Code, JetBrains, and Visual Studio”
   • [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
   • [claimed-docs] “GitHub Copilot integrates with leading editors, including Visual Studio Code, Visual Studio, JetBrains IDEs, and Neovim, and, unlike other A…”
   • [community] “I've been using the alpha for the past 2 weeks, and I'm blown away. Copilot guesses the exact code I want about one in ten times... when it …”

   proof ↗⚑ flag

   Slate~partialclaimed6/10

   Slate is documented as a terminal-based coding agent with session management, `@filename` references, shell execution, and workspace context — providing contextual chat help that developers can run alongside their editor in a terminal. However, there is no evidence of a native IDE extension/panel (e.g., VS Code/JetBrains plugin) that embeds Slate directly inside the IDE UI itself. missing for 10: dedicated IDE extension/panel integration, evidence of in-editor chat UI beyond terminal, independent corroboration of IDE workflow usage.

   • [claimed-docs] “Use `/sessions` to switch between existing sessions”
   • [claimed-docs] “Execute shell commands directly with `!`”
   • [claimed-docs] “Use `@filename` references”
   • [claimed-docs] “Use `/workspace` to open the workspace manager, where you can review and remove workspace directories.”
   • [claimed-docs] “Ctrl+X then N New session”

   proof ↗⚑ flag

Session management

1. developerReview diffs visually and run multiple sessions side by side in a desktop app

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialclaimed4/10

   Docs mention a 'desktop workspace' for launching work, tracking multiple agent sessions, and reviewing changes (docs-8, docs-14), and a code-review feature with inline suggested changes (docs-28), suggesting some diff-review and multi-session tracking capability. However, it's unclear whether this 'desktop workspace' is a native desktop app or a web-based GitHub UI, and there's no explicit description of a visual side-by-side diff viewer or dedicated multi-pane session UI as in competing IDE tools. Missing for 10: confirmation of a true native desktop application (not browser-based), explicit visual diff-viewer description, and independent/hands-on evidence of side-by-side session usage.

   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”

   proof ↗⚑ flag

   Slate—none0/10

   Slate is documented as a terminal/CLI tool (npm install, terminal-background onboarding, hotkeys, `/sessions` switching, subagent grid) with no mention of a desktop GUI or visual diff review; session switching is terminal-based, not side-by-side desktop windows. Missing for 10: any evidence of a desktop application, a visual diff viewer, or GUI-based side-by-side session comparison.

   • [claimed-docs] “npm i -g @randomlabs/slate”
   • [claimed-docs] “Onboarding asks for your terminal background, multiline input preference, and model source: your ChatGPT/Codex subscription, SuperGrok subsc…”
   • [claimed-docs] “Use `/sessions` to switch between existing sessions”
   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “Ctrl+X then N New session”

   proof ↗⚑ flag

2. engineering-leadManage multiple agent-driven coding sessions from one unified workspace

   weight 2 · round drawn
   GitHub Copilot✓fullclaimed8/10

   Docs describe a unified control page/desktop workspace to launch, track, and manage multiple agent sessions (Copilot, Claude, Codex) with progress tracking, review, merge, and governance/audit logs from one control plane, directly matching the story. Missing for 10: independent hands-on validation of the multi-agent dashboard experience and any reported friction managing many concurrent sessions.

   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”

   proof ↗⚑ flag

   Slate✓fullclaimed8/10

   Docs describe first-class multi-session/multi-agent workspace features: `/sessions` to switch sessions, `/workspace` manager, new-session hotkey, and orchestration showing a grid of inline subagent cards while continuing to chat, queue tasks, or spin up more parallel agents — directly matching the engineering-lead's need to manage multiple concurrent agent sessions from one place. Missing for 10: independent/hands-on verification of this workspace at scale and any lead-specific team-management features beyond individual session switching.

   • [claimed-docs] “Use `/sessions` to switch between existing sessions”
   • [claimed-docs] “Use `/workspace` to open the workspace manager, where you can review and remove workspace directories.”
   • [claimed-docs] “Those agents show up as a grid of inline subagent cards, one per agent.”
   • [claimed-docs] “While one or more agents run in the background, you can keep talking with Slate: plan next steps, queue up additional tasks, or spin up more…”
   • [claimed-docs] “Ctrl+X then N New session”

   proof ↗⚑ flag

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round to Slate
   GitHub Copilot✓fullprobed7/10

   GitHub Copilot CLI is officially documented as letting developers use Copilot directly from the terminal, including voice-to-text prompting, and is confirmed installable per docs and probe evidence. missing for 10: independent hands-on validation of the CLI agent's local execution/quality, and more detail on its autonomous/agentic capabilities (vs. just chat) within the terminal.

   • [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
   • [claimed-docs] “As an alternative to typing, you can speak your prompt.”
   • [probe] “official CLI documented at https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli”
   • [claimed-docs] “GitHub Copilot is also supported in terminals through GitHub CLI and as a chat integration in Windows Terminal Canary.”

   proof ↗⚑ flag

   Slate✓fullprobed8/10

   Slate ships as a global npm CLI (`npm i -g @randomlabs/slate`) that runs interactively in the terminal, with documented terminal-native features like hotkeys, shell command execution (`!`), file references (`@filename`), session management (`/sessions`), and configuration via `slate.json` — all consistent with a locally-run terminal coding agent. Missing for 10: independent hands-on confirmation of local terminal usage (community evidence only discusses porting-quality skepticism, not terminal operation itself) and no evidence of offline/non-terminal fallback limitations.

   • [claimed-docs] “npm i -g @randomlabs/slate”
   • [claimed-docs] “Onboarding asks for your terminal background, multiline input preference, and model source: your ChatGPT/Codex subscription, SuperGrok subsc…”
   • [claimed-docs] “Use `/sessions` to switch between existing sessions”
   • [claimed-docs] “Press Tab to queue the current message so it runs after the current turn finishes.”
   • [claimed-docs] “Execute shell commands directly with `!`”
   • [claimed-docs] “Use `@filename` references”
   • [claimed-docs] “Ctrl+X then N New session”
   • [probe] “official CLI documented at https://docs.randomlabs.ai/en/getting-started/quickstart”

   proof ↗⚑ flag

2. developerRun the agent non-interactively in scripts for workflow automation

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialclaimed5/10

   Copilot CLI (docs-26) lets you invoke Copilot from a terminal, and Copilot cloud agent 'Automations' (docs-15, docs-33) can be triggered on a schedule or repository events, which supports some non-interactive workflow automation. However, there is no direct evidence of a documented headless/non-interactive CLI flag (e.g., a scripted prompt-and-exit mode with exit codes) for running Copilot CLI itself inside arbitrary scripts. missing for 10: explicit CLI non-interactive/scripting mode docs, evidence of exit-code/output-parsing support for pipelines, independent hands-on confirmation of script usage.

   • [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
   • [claimed-docs] “Automations let you run Copilot cloud agent automatically, on a schedule or in response to events in a repository.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”

   proof ↗⚑ flag

   Slate—none0/10

   The evidence shows Slate is a CLI-based interactive agent (npm install, onboarding, in-session commands like /sessions, !, @filename) but nowhere documents a non-interactive/headless mode, flags for scripted execution, or CI/automation usage; --dangerously-skip-permissions bypasses prompts but is not shown as enabling scripted/non-interactive invocation. Missing for 10: documentation of a non-interactive/print/exec mode, exit-code or piping behavior, or any CI/scripting examples.

   • [claimed-docs] “npm i -g @randomlabs/slate”
   • [claimed-docs] “We support `--dangerously-skip-permissions` (alias: `--yolo`) to bypass permission prompts.”
   • [probe] “official CLI documented at https://docs.randomlabs.ai/en/getting-started/quickstart”

   proof ↗⚑ flag

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

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialprobed3/10

   Copilot offers a CLI (docs-26, probe-4) and MCP server integration (docs-25) that give some programmatic access to Copilot/GitHub features, but there is no evidence of a comprehensive public API/OpenAPI spec covering the full range of UI capabilities (chat, agent mode, cloud agent, code review) — the openapi probe returned 404 for all candidate endpoints (probe-3). Missing for 10: a documented REST/GraphQL API exposing chat, agent-mode edits, cloud-agent orchestration, and code review equivalently to the UI, and any independent confirmation that CLI/MCP covers full feature parity.

   • [claimed-docs] “The command-line interface (CLI) for GitHub Copilot allows you to use Copilot directly from your terminal.”
   • [probe] “official CLI documented at https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli”
   • [claimed-docs] “Learn how to use the GitHub Model Context Protocol (MCP) server to interact with repositories, issues, pull requests, and other GitHub featu…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence of any public API for Slate — the openapi.json/swagger.json probes returned 404s and no docs reference programmatic endpoints; Slate is documented purely as a CLI/terminal agent with slash-commands, hotkeys, and config files, not an API-driven product with UI/API parity.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.randomlabs.ai/openapi.json, https://docs.randomlabs.ai/swagger.json, https://docs.rando…”
   • [probe] “official CLI documented at https://docs.randomlabs.ai/en/getting-started/quickstart”
   • [claimed-docs] “npm i -g @randomlabs/slate”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   GitHub Copilot—none0/10

   No evidence in the pack describes any data export feature, open-format export, or account data portability mechanism for GitHub Copilot; documentation covers coding, agents, MCP, and models but nothing about exporting user data or leaving the platform with your data intact.

   ⚑ flag

   Slate—none0/10

   No evidence in the docs or elsewhere describes any data export functionality, open-format export, or data portability mechanism for Slate. Sessions, workspace history, and configurations appear stored locally but no documented export/leave path is mentioned. Missing for 10: any documentation of export commands, data format specifications, or account/data portability guarantees.

   ⚑ flag

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

   weight 2 · round drawn
   GitHub Copilot—none0/10

   GitHub Copilot is closed-source proprietary software; no evidence in the pack shows any open-license source availability, and community discussion instead focuses on training-data/licensing concerns, not the product's own source code being open.

   ⚑ flag

   Slate—none0/10

   No evidence of an open-source license or public source repository for Slate; the CLI is distributed via npm install with no mention of source availability. missing for 10: open-source license declaration, public source repo link, license file/OSS registry evidence.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   GitHub Copilot—none0/10

   GitHub Copilot is a proprietary cloud/IDE-integrated service with no evidence of any self-hostable core model, backend, or deployment option; all documented capabilities rely on GitHub's hosted infrastructure and models. Self-hosting is a legitimate axis for AI-native openness comparisons, but nothing in the evidence pack indicates it is possible.

   ⚑ flag

   Slate—none0/10

   No evidence anywhere in the docs of Slate being open-source or offering a self-hosted deployment option; it's installed via npm as a CLI that connects to model subscriptions/credits, implying a hosted/service model rather than self-hostable core infrastructure. Missing for 10: any mention of self-hosting instructions, open-source repo, or on-prem deployment option.

   • [claimed-docs] “npm i -g @randomlabs/slate”
   • [claimed-docs] “Onboarding asks for your terminal background, multiline input preference, and model source: your ChatGPT/Codex subscription, SuperGrok subsc…”

   proof ↗⚑ flag

Authentication

1. developerAuthenticate with an API key instead of an account login

   weight 2 · round drawn
   GitHub Copilot—none0/10

   No evidence in the pack describes API-key authentication as an alternative to account login; Copilot's auth model is tied to GitHub account/subscription (IDE sign-in, CLI, etc.) with no mention of API keys for developer access.

   ⚑ flag

   Slate—none0/10

   No evidence pack mentions API key authentication as an alternative to account login; onboarding docs only describe choosing a model source (ChatGPT/Codex, SuperGrok, or Slate credits subscription), not API-key auth. No mention of an API key mechanism anywhere, and the openapi probe returned 404s, giving no indication of an API-key based auth path.

   • [claimed-docs] “Onboarding asks for your terminal background, multiline input preference, and model source: your ChatGPT/Codex subscription, SuperGrok subsc…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.randomlabs.ai/openapi.json, https://docs.randomlabs.ai/swagger.json, https://docs.rando…”

   proof ↗⚑ flag

2. engineering-leadAuthenticate through an enterprise identity or cloud platform for compliance and scalability

   weight 2 · round drawn
   GitHub Copilot—none0/10

   No evidence in the pack addresses SSO/SAML, enterprise identity providers (e.g., Okta, Azure AD), or cloud platform authentication for Copilot; docs cover agents, MCP, models, and governance features but not identity/authentication for enterprise compliance. Missing for 10: SSO/SAML integration docs, enterprise IdP support (Azure AD/Okta), any mention of authentication/compliance certifications tied to identity federation.

   ⚑ flag

   Slate—none0/10

   No evidence of SSO/SAML/OIDC enterprise identity integration or cloud-platform authentication for compliance; onboarding only mentions choosing a model source (ChatGPT/Codex, SuperGrok, or Slate credits), not enterprise identity federation.

   • [claimed-docs] “Onboarding asks for your terminal background, multiline input preference, and model source: your ChatGPT/Codex subscription, SuperGrok subsc…”

   proof ↗⚑ flag

3. developerSign in with my existing product subscription plan to use the coding agent

   weight 2 · round to Slate
   GitHub Copilot✓fullclaimed7/10

   Docs show that Copilot's cloud/coding agent features (agent mode, cloud agent, agent apps) are powered by and included in a user's existing Copilot subscription, e.g. 'Agent apps let you use partner-built agents directly in your workflows on GitHub, powered by your Copilot subscription' and 'Access to Cloud agent and code review' listed as plan features, meaning no separate sign-up is needed beyond the existing subscription/login. Missing for 10: explicit tier-by-tier sign-in flow documentation and independent user confirmation that no extra account creation is required beyond the existing GitHub/Copilot login.

   • [claimed-docs] “Agent apps let you use partner-built agents directly in your workflows on GitHub, powered by your Copilot subscription.”
   • [claimed-docs] “Access to Cloud agent and code review”
   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”

   proof ↗⚑ flag

   Slate✓fullclaimed8/10

   Docs explicitly state onboarding lets you choose your model source as your existing ChatGPT/Codex subscription or SuperGrok subscription (in addition to Slate credits), directly matching the story of signing in with an existing subscription plan to use the agent. Missing for 10: independent/hands-on confirmation that subscription sign-in actually works end-to-end and any detail on limitations of that mode vs credits.

   • [claimed-docs] “Onboarding asks for your terminal background, multiline input preference, and model source: your ChatGPT/Codex subscription, SuperGrok subsc…”

   proof ↗⚑ flag

4. developerSign in with a personal account to get free-tier access without managing API keys

   weight 1 · round to Slate
   GitHub Copilot—none0/10

   The evidence pack contains no mention of a free tier, personal GitHub account sign-in flow, or API-key-free authentication for Copilot; all docs items describe features (agent mode, MCP, code review) but never address account-based free-tier access or pricing/sign-in mechanics.

   ⚑ flag

   Slate~partialclaimed4/10

   Docs show onboarding lets users choose a model source including an existing ChatGPT/Codex or SuperGrok subscription instead of managing API keys, implying account-based auth is supported, but there's no explicit mention of a free tier or of signing in with a personal Slate account for free credits without a paid subscription. Missing for 10: explicit free-tier account sign-in flow, confirmation that 'Slate credits' option requires no payment, and any account-based (not subscription-based) login mechanism.

   • [claimed-docs] “Onboarding asks for your terminal background, multiline input preference, and model source: your ChatGPT/Codex subscription, SuperGrok subsc…”

   proof ↗⚑ flag

Model choice

1. developerLet the tool automatically pick the best model for each task

   weight 1 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed7/10

   GitHub's own docs explicitly state Copilot can 'Automatically select the best model for each task' (docs-17), alongside supporting claims about multiple models optimized for speed/accuracy/cost (docs-7, docs-30). Missing for 10: independent/hands-on verification that auto-selection actually works well in practice, and details on how/when it triggers vs manual model choice.

   • [claimed-docs] “Automatically select the best model for each task.”
   • [claimed-docs] “Choose from leading LLMs optimized for speed, accuracy, or cost.”
   • [claimed-docs] “GitHub Copilot supports multiple AI models, each with different strengths. Some prioritize speed and cost-efficiency, while others are optim…”

   proof ↗⚑ flag

   Slate~partialclaimed6/10

   Docs explicitly claim Slate 'automatically selects the right model for the job' and also allow developers to set preferred default models per slot via `/models` or `slate.json`, suggesting a hybrid automatic+manual approach relevant to pricing/limits tradeoffs. However, there's no detail on the selection logic, cost-awareness, or independent verification that auto-selection actually optimizes for task/price. Missing for 10: independent hands-on confirmation of auto-selection quality, explanation of selection criteria (cost vs capability), and evidence of pricing-limit awareness in model choice.

   • [claimed-docs] “Slate automatically selects the right model for the job.”
   • [claimed-docs] “Set preferred default models for each slot with the `/models` dialog or `slate.json` under `models`.”

   proof ↗⚑ flag

2. developerChoose which underlying AI model powers my session from multiple providers

   weight 2 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   GitHub's own docs explicitly state Copilot supports multiple AI models from different providers (e.g., Claude, OpenAI Codex) and lets users 'choose from leading LLMs optimized for speed, accuracy, or cost,' with a dedicated supported-models reference page and an auto-select option. This directly matches the story of choosing the underlying model per session. Missing for 10: independent/hands-on community confirmation of the model-picker UI in practice and details on per-session persistence of the choice.

   • [claimed-docs] “Choose from leading LLMs optimized for speed, accuracy, or cost.”
   • [claimed-docs] “GitHub Copilot supports multiple AI models, each with different strengths. Some prioritize speed and cost-efficiency, while others are optim…”
   • [claimed-docs] “Assign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the…”
   • [claimed-docs] “Automatically select the best model for each task.”

   proof ↗⚑ flag

   Slate~partialclaimed6/10

   Docs confirm model source can be chosen at onboarding (ChatGPT/Codex, SuperGrok, or Slate credits) and that default models per 'slot' can be set via `/models` or slate.json, showing multi-provider flexibility. However, this is framed around subscription/credit sources rather than a clear list of many independent model providers, and there's no independent/hands-on verification of switching providers mid-session. missing for 10: independent corroboration of provider switching, a full list of supported model providers, and confirmation this works reliably in practice.

   • [claimed-docs] “Onboarding asks for your terminal background, multiline input preference, and model source: your ChatGPT/Codex subscription, SuperGrok subsc…”
   • [claimed-docs] “Set preferred default models for each slot with the `/models` dialog or `slate.json` under `models`.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   GitHub Copilot—none0/10

   No evidence in the pack mentions data residency, region selection, or geographic storage controls for GitHub Copilot; only data-training opt-out is mentioned, which is a different concern.

   ⚑ flag

   Slate—none0/10

   Slate is a CLI coding agent tool; the evidence pack contains no mention of data residency, region selection, or storage location controls. Missing for 10: any documentation of data residency options, regional storage configuration, or compliance controls.

   ⚑ flag

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

   weight 3 · round to GitHub Copilot
   GitHub Copilot~partialcommunity6/10

   GitHub's docs explicitly state individual subscribers can opt out of having their data used for AI model training at any time (github-copilot-docs-12), directly satisfying the story's core ask. However, the evidence pack lacks detail on how opt-out is enforced, whether it covers all Copilot data flows (e.g., telemetry, code review, agents), and community commentary voices skepticism (not concrete contradiction) about whether enterprise code can truly be excluded. Missing for 10: independent verification that opt-out is honored in practice, clarity on enterprise/org-level data-use guarantees, and details on scope of what 'training' opt-out actually excludes.

   • [claimed-docs] “Individual subscribers can opt out of having their data used for AI model training at any time”
   • [community] “Well, this can impose a serious risk to companies and their cloud strategy based on GitHub. Can these enterprises really make sure that thei…”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence in the pack addresses data-training opt-out, privacy policy, or any control over model training use; the documentation covers CLI usage, orchestration, and skills but nothing about data privacy posture. Missing for 10: any privacy policy statement, opt-out settings, or data usage terms regarding AI training.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialcommunity5/10

   GitHub Copilot docs confirm individual subscribers can opt out of AI model training data use at any time, giving some control over data usage, but there is no documented self-service mechanism for deleting stored chat/history data or explicit retention period controls. Community commentary also raises unresolved skepticism about enterprise assurances that code won't be used for training. Missing for 10: explicit data-deletion tooling, documented retention windows, and enterprise-level deletion guarantees beyond opt-out.

   • [claimed-docs] “Individual subscribers can opt out of having their data used for AI model training at any time”
   • [community] “Well, this can impose a serious risk to companies and their cloud strategy based on GitHub. Can these enterprises really make sure that thei…”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence pack items mention data retention policies, deletion controls, or privacy settings for user data/sessions; docs cover workspace management and permissions but not data retention/deletion. Missing for 10: any documentation of data retention periods, deletion mechanisms, or export/erase controls.

   ⚑ flag

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

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialcommunity4/10

   Docs confirm individual subscribers can opt out of having their code data used for AI model training, but this is narrower than opting out of telemetry/usage tracking broadly, and no evidence describes a general telemetry opt-out toggle. Community commentary (comm-5) even notes agreeing to 'additional telemetry terms' during a preview with no opt-out mentioned. Missing for 10: explicit telemetry/usage-tracking opt-out setting, documentation distinguishing telemetry from training-data opt-out, and independent confirmation that opting out actually stops telemetry collection.

   • [claimed-docs] “Individual subscribers can opt out of having their data used for AI model training at any time”
   • [community] “Gigantic caveat: 'I agree to these additional telemetry terms as part of the technical preview.'”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence pack item mentions telemetry, usage tracking, analytics, or an opt-out setting anywhere in Slate's docs or community coverage; the closest item (diagnostic attachment on bug reports) doesn't address general telemetry opt-out. Missing for 10: any mention of telemetry collection, a privacy policy, or a documented opt-out flag/setting.

   • [claimed-docs] “Slate automatically attaches relevant diagnostic information (OS, version, session context) to your report.”

   proof ↗⚑ flag

Data governance

1. engineering-leadOpt out of having my code and prompts used for AI model training

   weight 1 · round to GitHub Copilot
   GitHub Copilot~partialcommunity6/10

   Docs explicitly state individual subscribers can opt out of AI model training at any time (github-copilot-docs-12), which covers a developer-level version of this story. However, evidence does not show an org-wide/enterprise admin policy control that an engineering-lead could set organization-wide, and one community comment expresses skepticism about enterprise assurance (not a concrete contradiction). Missing for 10: enterprise/org-level policy documentation, admin-console controls, and independent verification of enforcement.

   • [claimed-docs] “Individual subscribers can opt out of having their data used for AI model training at any time”
   • [community] “Well, this can impose a serious risk to companies and their cloud strategy based on GitHub. Can these enterprises really make sure that thei…”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence in the pack addresses data usage, training opt-out, or privacy policy for prompts/code submitted to Slate or its model providers.

   ⚑ flag

Pr review

1. developerHave the agent stage changes, write commit messages, create branches, and open pull requests

   weight 3 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed7/10

   GitHub Copilot's cloud/background agent is documented to work independently on tasks, make changes on existing PRs via @copilot mentions, and complete work 'just like a human developer,' which in GitHub's workflow model entails committing changes and opening/updating pull requests (docs-31, docs-32, docs-8, docs-14). However, explicit documentation of branch creation and commit-message authorship mechanics is not directly cited, and there is no independent/hands-on verification of the PR-opening workflow. Missing for 10: explicit branch-creation documentation, independent hands-on confirmation of commit/PR flow, and detail on staging-changes granularity.

   • [claimed-docs] “With Copilot cloud agent, GitHub Copilot can work independently in the background to complete tasks, just like a human developer.”
   • [claimed-docs] “Mention `@copilot` in a comment on an existing pull request to ask it to make changes.”
   • [claimed-docs] “Launch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace buil…”
   • [claimed-docs] “Use one centralized control page to jump between agent sessions, check progress, and stay in control without losing your place.”
   • [claimed-docs] “Set up an automation to run Copilot automatically, on a schedule or in response to events such as an issue being opened.”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence in the pack mentions git operations like staging, committing, branching, or opening pull requests; documentation covers sessions, orchestration, skills, permissions, and CLI setup but not any git/PR workflow. Absence of evidence for this applicable capability means the verdict is none.

   ⚑ flag

2. developerInspect diffs and run checks to catch problems before merging

   weight 3 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   Copilot provides code review with inline suggested changes and severity-labeled comments (docs-28, docs-29), integrated with PR diffs, plus Autofix for vulnerability detection (docs-13) and agent mode validation of files (docs-22). This directly supports inspecting diffs and catching problems pre-merge. Missing for 10: independent/hands-on evidence of the code-review feature's real-world accuracy and no explicit mention of running CI/test checks as part of the flow.

   • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
   • [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”
   • [claimed-docs] “GitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code”
   • [claimed-docs] “Copilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.”
   • [claimed-docs] “Access to Cloud agent and code review”

   proof ↗⚑ flag

   Slate~partialclaimed3/10

   Slate's docs mention it can perform integration tests manually (random-labs-docs-16), implying some check-running capability, but there is no evidence of diff inspection, git diff review, PR-style change summaries, or pre-merge validation workflows. missing for 10: diff/change inspection UI or command, explicit pre-merge check/test running workflow, and any corroborating hands-on evidence of catching problems before merge.

   • [claimed-docs] “Slate is one of the few agents capable of performing integration tests manually.”

   proof ↗⚑ flag

Safe execution

1. engineering-leadControl which external tools and integrations the agent is allowed to access

   weight 2 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   GitHub Copilot provides explicit admin controls to allow-list MCP servers developers can access ('Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access'), plus a centralized control plane with audit logs for governance over agents. This directly matches the engineering-lead's need to restrict external tool/integration access. Missing for 10: independent/hands-on verification of the allow-list enforcement in practice, and more granular detail on per-tool (vs per-MCP-server) restriction scope.

   • [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”
   • [claimed-docs] “Connect MCP servers to Copilot Chat to share context from other applications.”

   proof ↗⚑ flag

   Slate~partialclaimed6/10

   Slate's configuration docs describe a permission system where each permission key maps to allow/ask/deny actions or fine-grained pattern objects, which supports controlling what tools/actions the agent can perform, and a `--yolo` flag exists to bypass these prompts entirely. However there's no explicit documentation of controlling specific external integrations (e.g., MCP servers, API connectors) or org/team-level lockdown for an engineering lead specifically. Missing for 10: explicit external-integration/MCP allowlist docs, engineering-lead/team-level enforcement (vs individual config), and independent verification that permission enforcement can't be trivially bypassed.

   • [claimed-docs] “Each permission key maps to an action ("allow", "ask", or "deny"), or a pattern object for fine-grained control.”
   • [claimed-docs] “We support `--dangerously-skip-permissions` (alias: `--yolo`) to bypass permission prompts.”

   proof ↗⚑ flag

2. engineering-leadHave the agent operate inside a sandbox when interacting with code, tools, and network resources

   weight 2 · round to GitHub Copilot
   GitHub Copilot✓fullclaimed8/10

   Docs explicitly state that Cloud and local sandboxes provide isolated execution environments letting Copilot safely interact with code, tools, filesystem, and network resources, either locally or in fully isolated cloud environments, with additional governance controls like MCP server allow lists and audit logs. Missing for 10: independent/hands-on verification of sandbox isolation guarantees and no detail on sandbox escape/limits.

   • [claimed-docs] “Cloud and local sandboxes provide isolated execution environments that let Copilot safely interact with code, tools, filesystem, and network…”
   • [claimed-docs] “Control which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.”
   • [claimed-docs] “Track activity with detailed audit logs and enforce governance by managing agents from a single control plane.”

   proof ↗⚑ flag

   Slate—none0/10

   The evidence shows a permission system (allow/ask/deny actions) and a --yolo flag to bypass prompts, but there is no mention of sandboxed execution, containerization, or network isolation for the agent's code/tool interactions. missing for 10: any documentation of sandbox/container execution, network isolation controls, or filesystem confinement mechanisms.

   • [claimed-docs] “Each permission key maps to an action ("allow", "ask", or "deny"), or a pattern object for fine-grained control.”
   • [claimed-docs] “We support `--dangerously-skip-permissions` (alias: `--yolo`) to bypass permission prompts.”

   proof ↗⚑ flag

Security checks

1. engineering-leadSee license and public-code matching references for AI-suggested code

   weight 1 · round to GitHub Copilot
   GitHub Copilot~partialcommunity5/10

   GitHub Copilot documents a public-code matching feature that searches public GitHub repos for matches to a suggestion (docs-11), which is the closest evidence to the story's ask. However, the evidence pack gives no detail on how license attribution is actually surfaced to an engineering lead, and community discussion raises real concerns about verbatim/near-verbatim reproduction and licensing risk (comm-12, comm-13, comm-14, comm-16), with only partial rebuttal (comm-17) — indicating the feature's coverage and reliability for license-safety review is limited. Missing for 10: detailed docs on license display/attribution UI, audit/reporting workflow for engineering leads, and independent verification that the matching feature reliably flags copyleft/licensed snippets.

   • [claimed-docs] “This feature searches across public GitHub repositories for code that matches a Copilot suggestion.”
   • [community] “It certainly seems to be a laundering enabler. Say that you want to un-GPL-ify some famous copylefted code... you type a first innocuous cha…”
   • [community] “The potential inclusion of GPL'd code, and potentially even unlicensed code, is making me wary of using it. Fair Use doesn't exist here and …”
   • [community] “'We found that about 0.1% of the time, the suggestion may contain some snippets that are verbatim from the training set.' If it's spitting o…”
   • [community] “I just tested it myself on a random c file... it reproduced his full code verbatim from just the function header so clearly it does regurgit…”
   • [community] “It prints this code because you have it open in another editor tab. Wish people who don't know at all how it works stopped acting all outrag…”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence anywhere in the pack mentions license compliance checks, public-code/OSS matching, or provenance references for AI-suggested code; the docs cover orchestration, skills, permissions, and CLI usage but nothing about code provenance/license scanning.

   ⚑ flag

2. developerGet contextual explanations and automatic fixes for security vulnerabilities

   weight 2 · round to GitHub Copilot
   GitHub Copilot~partialclaimed6/10

   GitHub Copilot Autofix is explicitly documented to provide 'contextual explanations and code suggestions to help developers fix vulnerabilities in code' and Copilot code review adds severity-labeled feedback with suggested fixes, directly matching the story. However, this is first-party documentation only with no independent/hands-on validation of Autofix's real-world effectiveness, and no detail on scope/limitations (e.g., which languages, integration with Advanced Security). missing for 10: independent corroboration of Autofix accuracy, hands-on developer reports validating the fix quality, details on prerequisites/limitations of the feature.

   • [claimed-docs] “GitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code”
   • [claimed-docs] “GitHub Copilot can review your code and provide feedback. Where possible, Copilot's feedback includes suggested changes which you can apply …”
   • [claimed-docs] “Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their im…”

   proof ↗⚑ flag

   Slate—none0/10

   No evidence in the pack mentions security vulnerability detection, explanations, or automatic fixes; documentation covers session management, orchestration, skills, and configuration but nothing about security review or vulnerability remediation. Missing for 10: any mention of vulnerability scanning, security explanations, or auto-fix capability.

   ⚑ flag