Cursor vs Conductor

Agent access

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

   weight 2 · round to Conductor
   Cursor—none0/10

   No evidence pack item mentions llms.txt, agent-oriented documentation ingestion, or a mechanism to point Cursor's agent at such files; only generic doc/MCP/tooling references are present. missing for 10: any mention of llms.txt support, crawling agent-oriented doc formats, or a documented feature for feeding external agent docs to Cursor's agent.

   ⚑ flag

   Conductor✓fullprobed9/10

   Direct probe confirms llms.txt is live and served at https://www.conductor.build/llms.txt with agent-oriented summary, plus a full docs.md markdown mirror for agent consumption. missing for 10: no independent/community confirmation that external agents actually consume these files successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.conductor.build/llms.txt # Conductor > Conductor is a Mac app that lets you run many coding agents …”
   • [probe] “PROBE docs-md: HTTP 200 at https://www.conductor.build/docs.md --- title: "Introduction" url: "/docs" description: "Learn what Conductor is …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor~partialprobed6/10

   Cursor ships an official CLI (cursor.com/cli, curl installer) and background/cloud agents that run 'on schedules or triggers' to build and fix software autonomously, which implies non-interactive/headless automation. However, there is no explicit documentation of CI pipeline integration, exit codes, or scripting examples for pipelines. Missing for 10: explicit CI/CD integration docs (e.g., GitHub Actions example), documented headless flags/exit-code behavior, and independent confirmation of CLI use in automated pipelines.

   • [probe] “official CLI documented at https://cursor.com/cli”
   • [claimed-docs] “curl https://cursor.com/install -fsS | bash”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor~partialprobed6/10

   Conductor supports scheduled/CI-like automation via 'routines' that run on a schedule or GitHub Action, plus a programmatic API and hosted MCP server for managing cloud workspaces headlessly, and cloud agents can run builds/tests without confirmation. However, it is fundamentally a Mac GUI app, and there's no evidence of a standalone CLI or true headless binary for arbitrary CI pipelines outside GitHub Actions. missing for 10: dedicated CLI/headless binary for generic CI systems, independent evidence of routines/GitHub Action working reliably in production, clarity on full non-interactive operation outside the Mac app.

   • [claimed-docs] “Introducing routines! You can now run your agents on a schedule or via GitHub action.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “Conductor's hosted Model Context Protocol (MCP) server lets ChatGPT, Claude, Codex, and other MCP clients manage your cloud workspaces.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [probe] “official MCP server documented at https://www.conductor.build/docs/api/mcp”

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor✓fullclaimed8/10

   Cursor's docs explicitly describe MCP support: connecting to external tools/data sources, marketplace one-click install with OAuth, custom JSON server configuration, toggling servers, and enterprise admin controls over allowed servers. This directly matches the story of plugging in MCP servers so the agent can use their tools. Missing for 10: independent hands-on verification of MCP tool usage in practice and no community corroboration of the feature's reliability.

   • [claimed-docs] “Model Context Protocol (MCP) enables Cursor to connect to external tools and data sources.”
   • [claimed-docs] “Click "Add to Cursor" on a marketplace entry to install it and authenticate with OAuth.”
   • [claimed-docs] “Configure custom MCP servers with a JSON file”
   • [claimed-docs] “Enterprise admins can control which MCP servers users may run from the Cursor dashboard.”
   • [claimed-docs] “Toggle servers on/off without removing them”

   proof ↗⚑ flag

   Conductor—none0/10

   Evidence only shows Conductor exposing its OWN hosted MCP server so external MCP clients (ChatGPT, Claude, Codex) can manage Conductor's cloud workspaces (conductor-docs-14, conductor-probe-4) — the reverse direction of what the story asks. There is no documentation or community mention of a user being able to add/configure external MCP servers inside Conductor so its hosted coding agents (Claude Code, Codex, Cursor, OpenCode) can consume their tools.

   • [claimed-docs] “Conductor's hosted Model Context Protocol (MCP) server lets ChatGPT, Claude, Codex, and other MCP clients manage your cloud workspaces.”
   • [probe] “official MCP server documented at https://www.conductor.build/docs/api/mcp”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Cursor
   Cursor✓fullprobed8/10

   Cursor documents an official CLI with an install command (curl https://cursor.com/install) and a dedicated CLI docs page (cursor.com/cli), confirming a first-party terminal tool for AI-native workflows. Missing for 10: independent/hands-on corroboration of CLI capabilities and depth of documentation beyond install instructions.

   • [claimed-docs] “curl https://cursor.com/install -fsS | bash”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [probe] “official CLI documented at https://cursor.com/cli”

   proof ↗⚑ flag

   Conductor—none0/10

   Conductor is documented as a Mac GUI app with a programmatic API and hosted MCP server, but no evidence pack item describes an official Conductor CLI tool; the only CLI mention is a user leveraging their own 'local GitHub CLI auth', which is unrelated.

   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [community] “Fixed! You can now give Conductor fine-grained GitHub repository access. Or, skip the integration and use your local GitHub CLI auth.”

   proof ↗⚑ flag

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

   weight 3 · round to Conductor
   Cursor~partialprobed3/10

   Evidence shows an official CLI (cursor.com/cli) that lets users invoke Cursor from scripts, which partially satisfies 'driving the product programmatically,' but there is no documented public REST/SDK API, authentication scheme, or endpoint reference — MCP docs describe Cursor consuming external tools, not exposing itself as an API. Missing for 10: documented REST/GraphQL API, SDK/client libraries, API authentication and rate-limit docs, independent corroboration of programmatic usage.

   • [probe] “official CLI documented at https://cursor.com/cli”
   • [claimed-docs] “curl https://cursor.com/install -fsS | bash”

   proof ↗⚑ flag

   Conductor✓fullprobed7/10

   Conductor documents a public API for programmatically managing cloud workspaces (create workspaces, send prompts, read agent replies) plus a hosted MCP server for AI clients like ChatGPT/Claude/Codex to drive it. Missing for 10: a published OpenAPI/reference spec (probe found only 404s for schema files) and independent/hands-on developer corroboration of API usage.

   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [claimed-docs] “Conductor's hosted Model Context Protocol (MCP) server lets ChatGPT, Claude, Codex, and other MCP clients manage your cloud workspaces.”
   • [probe] “official MCP server documented at https://www.conductor.build/docs/api/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.conductor.build/openapi.json, https://www.conductor.build/swagger.json, https://www.cond…”

   proof ↗⚑ flag

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

   weight 2 · round to Conductor
   Cursor—none0/10

   No evidence Cursor lets users mint scoped or least-privilege API credentials for agents; docs cover MCP server toggling and enterprise admin control of which servers can run, but nothing about issuing scoped/limited API keys or credentials specifically for agent use.

   ⚑ flag

   Conductor~partialcommunity4/10

   Community threads document that Conductor originally required full read/write GitHub access with no fine-grained scoping, which users flagged as risky; the developers later added a GitHub App integration for fine-grained repo access (or use of local GitHub CLI auth) as a fix, showing partial progress toward least-privilege credentials but not a documented, general mechanism for issuing scoped API credentials for agents beyond GitHub repo access. Missing for 10: no documentation of scoped/least-privilege credentials for the Conductor API/MCP server itself, no explicit policy on token scoping for non-GitHub integrations, and no independent verification that the new GitHub App permissions are truly minimal in practice.

   • [community] “Any way to have it not require full write access to your entire GitHub account?”
   • [community] “Full read-write access required to all your Github account's repos. Not just code. Settings, deploy keys. The works... Zero disclosure of da…”
   • [community] “I was really excited to try this but this does NOT work the way I expected. I wanted a simple git worktree manager for my existing, already-…”
   • [community] “Right now the app uses GitHub's OAuth sign in which unfortunately doesn't allow for fine-grained permissions... We're switching our sign-in …”
   • [community] “Fixed! You can now give Conductor fine-grained GitHub repository access. Or, skip the integration and use your local GitHub CLI auth.”
   • [claimed-docs] “Bring your own subscriptions and keys”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Conductor
   Cursor—none0/10

   Evidence shows Cursor offers a CLI, MCP integration, and marketplace extensions, but there is no mention of any official SDK (e.g., a documented library/API package) for developers to build against Cursor itself.

   ⚑ flag

   Conductor~partialprobed5/10

   Conductor documents an official REST-style API for managing cloud workspaces and sending/reading agent prompts, plus a hosted MCP server for AI clients, which supports building AI-native integrations. However, no dedicated client SDK packages (e.g., npm/python libraries) are evidenced, and a probe for an OpenAPI spec returned 404s, suggesting the 'SDK' is really just a raw API/MCP interface rather than a polished, language-specific SDK. missing for 10: official language SDK packages, OpenAPI/schema-based codegen support, independent hands-on confirmation of SDK usage.

   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [claimed-docs] “Conductor's hosted Model Context Protocol (MCP) server lets ChatGPT, Claude, Codex, and other MCP clients manage your cloud workspaces.”
   • [probe] “official MCP server documented at https://www.conductor.build/docs/api/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.conductor.build/openapi.json, https://www.conductor.build/swagger.json, https://www.cond…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Cursor—none0/10

   Evidence covers MCP integration, background agents, and IDE integrations, but there is no mention of a webhook subscription mechanism for external event notifications.

   ⚑ flag

   Conductor—none0/10

   The evidence pack documents a programmatic API and an MCP server for managing cloud workspaces, but nowhere mentions webhooks or any event-subscription mechanism for AI-native users to receive push notifications on workspace/task events.

   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [claimed-docs] “Conductor's hosted Model Context Protocol (MCP) server lets ChatGPT, Claude, Codex, and other MCP clients manage your cloud workspaces.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed7/10

   Cursor's core value proposition is analyzing the user's codebase to surface AI-generated insights (tracing repo structure, finding root causes, reviewing diffs) and suggestions for next actions, as documented across multiple first-party docs. Missing for 10: independent/hands-on evidence validating the accuracy or depth of these insights, and no detail on insight types beyond code-centric suggestions (e.g., data analytics or business data outside code).

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”
   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”

   proof ↗⚑ flag

   Conductor~partialclaimed4/10

   Conductor orchestrates third-party coding agents (Claude Code, Codex, Cursor) that analyze the codebase and produce diffs, suggested changes, and PR reviews, which can be seen as data-driven suggestions, but Conductor itself does not document any native analytics/insights engine — the 'insight' generation is delegated entirely to the underlying agents. Missing for 10: no first-party insight/analytics feature, no evidence of Conductor synthesizing patterns or trends from user data beyond agent chat/diff output, no independent corroboration of this specific capability.

   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”
   • [claimed-docs] “Checkpoints | Session/workspace | Revert code and chat state to an earlier turn”

   proof ↗⚑ flag

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed8/10

   Cursor explicitly documents 'always-on agents that run on schedules or triggers to build, maintain, and fix your software' and 'fleets of agents that work in parallel for hours or days,' directly matching autonomous background automation. This is first-party vendor documentation without independent hands-on corroboration of scheduling/triggers working reliably. Missing for 10: independent/community verification that scheduled/triggered background agents work reliably in practice, and more detail on trigger configuration options.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor✓fullclaimed7/10

   Conductor's "routines" feature explicitly lets users run agents on a schedule or via GitHub Action, and cloud workspaces continue running autonomously ("agents keep working after you close your laptop") without requiring step-by-step confirmation. This directly matches background, autonomous automation for an AI-native user. Missing for 10: independent/hands-on confirmation that routines work reliably in practice, and more detail on scheduling configuration options beyond the changelog mention.

   • [claimed-docs] “Introducing routines! You can now run your agents on a schedule or via GitHub action.”
   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor✓fullclaimed9/10

   Cursor's docs clearly describe delegating tasks to built-in agents that plan, code, test, and demo work end-to-end while the user focuses on review/decisions, including background/parallel agents and always-on scheduled agents. This is a core, heavily documented capability of the product, though independent hands-on validation of agent task quality is thin (only general community commentary, some critical, exists). Missing for 10: deeper independent verification of agent task success rates beyond vendor docs.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”

   proof ↗⚑ flag

   Conductor✓fullcommunity8/10

   Conductor lets users delegate coding tasks to agents (Claude Code, Codex, Cursor, OpenCode) that run inside its own workspaces, autonomously testing repos, running builds, and continuing work unattended, with checkpoints and review flow built into the product (conductor-docs-1, -17, -20, -29, -32). Community reports confirm the agent runs live inside the app during real use (conductor-comm-7, conductor-comm-15). Missing for 10: independent benchmarking of assistant quality/reliability beyond docs and mixed anecdotal UX feedback (conductor-comm-9).

   • [claimed-docs] “Conductor lets you run Claude Code, Codex, Cursor, and OpenCode in parallel.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”
   • [community] “I have been imagining something like this would be perfect for working with Claude Code... This feels like just a nice clean simple extensio…”
   • [community] “Your messages are just between you and Claude Code — it all runs on your local Claude Code installation via the SDK.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor✓fullclaimed8/10

   Cursor's core interaction model is natural-language driven agents that plan, code, test, and operate across terminal/Slack/GitHub (cursor-docs-2, cursor-docs-8, cursor-docs-9, cursor-docs-10, cursor-docs-11), consistent with an AI-native product. Missing for 10: independent hands-on evidence specifically validating natural-language command reliability/accuracy (community evidence focuses on bugginess/pricing complaints unrelated to NL command capability itself).

   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”
   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor✓fullprobed8/10

   Conductor's entire interaction model is natural-language chat with coding agents (Claude Code, Codex, Cursor, OpenCode) that can autonomously test, build, and edit without step confirmation, and it exposes a hosted MCP server so ChatGPT/Claude/Codex or other AI clients can manage workspaces via natural language, plus an API to send prompts and read agent replies. missing for 10: independent/hands-on validation of natural-language command reliability beyond vendor docs.

   • [claimed-docs] “Conductor's hosted Model Context Protocol (MCP) server lets ChatGPT, Claude, Codex, and other MCP clients manage your cloud workspaces.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”
   • [probe] “official MCP server documented at https://www.conductor.build/docs/api/mcp”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence of an interactive API reference with runnable examples for Cursor; docs entries describe product features and MCP setup but nothing about an API reference or executable code samples.

   ⚑ flag

   Conductor—none0/10

   Conductor has documented API endpoints and an MCP server, so an interactive API reference with runnable examples is a plausible feature, but the evidence pack shows no such reference exists — the docs page is static markdown and probes for OpenAPI/Swagger specs all returned 404.

   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.conductor.build/openapi.json, https://www.conductor.build/swagger.json, https://www.cond…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence of Cursor publishing a downloadable OpenAPI or equivalent machine-readable API spec; docs reference MCP config and CLI but not an API spec.

   ⚑ flag

   Conductor—none0/10

   Conductor documents a REST-like API and an MCP server, but a direct probe for machine-readable OpenAPI/Swagger specs at standard locations returned 404 on all candidate paths, and no evidence pack item links to a downloadable spec file.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.conductor.build/openapi.json, https://www.conductor.build/swagger.json, https://www.cond…”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence in the pack mentions API versioning or a deprecation policy for Cursor's APIs (CLI, extensions, or MCP config); docs cover features like MCP setup, agents, and integrations but nothing about version stability guarantees or deprecation timelines.

   ⚑ flag

   Conductor—none0/10

   There's an API and MCP server documented, but no evidence of API versioning scheme or a deprecation policy; probes show no OpenAPI spec found and no changelog/policy on version deprecation.

   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.conductor.build/openapi.json, https://www.conductor.build/swagger.json, https://www.cond…”

   proof ↗⚑ flag

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

   weight 2 · round to Conductor
   Cursor~partialclaimed5/10

   Cursor supports launching 'fleets of agents' in parallel and always-on scheduled/triggered agents, which enables some multi-item automation, but there's no direct evidence of bulk operations across many discrete items (e.g., bulk file edits, batch refactors, or multi-repo operations) as a first-class feature. missing for 10: explicit documentation or hands-on evidence of bulk/batch operations across many items (files, tickets, repos), user-facing UI for selecting many items at once, and independent corroboration of this working in practice.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”

   proof ↗⚑ flag

   Conductor~partialclaimed7/10

   Conductor supports running many coding agents in parallel across isolated workspaces, and exposes a programmatic API plus scheduled/CI-triggered 'routines' that can create workspaces and send prompts at scale — a reasonable basis for bulk, automation-driven operations across many items. However, there's no documented UI for batch-selecting and acting on many existing workspaces at once (e.g., bulk archive/merge), and no independent evidence of large-scale parallel runs in practice. Missing for 10: explicit multi-item batch actions in the UI, evidence of scale/limits on parallel agents, and third-party corroboration of bulk automation workflows via the API or routines.

   • [claimed-docs] “Conductor lets you run Claude Code, Codex, Cursor, and OpenCode in parallel.”
   • [claimed-docs] “Create a new workspace with Command + N when work should have its own branch, files, running environment, and review path.”
   • [claimed-docs] “Run multiple agents in one workspace when the work belongs on the same branch and should share the same files and context.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [claimed-docs] “Introducing routines! You can now run your agents on a schedule or via GitHub action.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor~partialclaimed6/10

   Cursor docs describe 'always-on agents that run on schedules or triggers' and a way to 'add rules' from one place, matching the idea of rule-based automation triggered by events. However the evidence pack doesn't detail how rules are authored/scoped to specific events beyond the marketing blurb, and there's no independent/hands-on confirmation of this automation working as described. Missing for 10: concrete rule-definition syntax/examples, independent verification that scheduled/triggered agents reliably fire on events, and detail on event types supported.

   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Add plugins, skills, MCPs, and rules from one place”

   proof ↗⚑ flag

   Conductor~partialclaimed5/10

   Conductor's 'routines' feature lets agents run on a schedule or via GitHub Action trigger, which is a limited form of event-driven automation, but there's no evidence of a general rules engine supporting arbitrary event types (e.g., webhooks, file changes, custom conditions) or complex trigger-action definitions. Missing for 10: broader event-type support, custom rule/condition definitions, and hands-on evidence that routines fire reliably on GitHub events.

   • [claimed-docs] “Introducing routines! You can now run your agents on a schedule or via GitHub action.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Cursor
   Cursor✓fullclaimed7/10

   Cursor documents 'always-on agents that run on schedules or triggers to build, maintain, and fix your software,' directly matching recurring scheduled workflow automation, alongside parallel agent fleets for ambitious tasks. Missing for 10: independent hands-on verification of scheduling reliability, details on trigger configuration options, and any community corroboration of this specific feature working in practice.

   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”

   proof ↗⚑ flag

   Conductor✓fullclaimed6/10

   Conductor's changelog explicitly introduces 'routines' that let agents run on a schedule or via GitHub Action, directly matching the recurring-jobs/workflows story. However, this is a single brief changelog mention with no dedicated documentation page, configuration details, or community corroboration of the feature in practice. Missing for 10: dedicated docs on routine/schedule configuration, independent/hands-on confirmation, details on failure handling or monitoring of scheduled runs.

   • [claimed-docs] “Introducing routines! You can now run your agents on a schedule or via GitHub action.”

   proof ↗⚑ flag

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

   weight 1 · round to Conductor
   Cursor—none0/10

   Evidence shows Cursor can inspect diffs and review changes before merge, but there is no documented capability to version, review, or roll back the automations themselves (e.g., scheduled/always-on agents, rules, MCP configs) as distinct artifacts with history/rollback support.

   ⚑ flag

   Conductor~partialclaimed6/10

   Conductor provides git-based versioning (separate branches/worktrees per workspace), diff review before merge/PR, and 'Checkpoints' to revert code and chat state to an earlier turn—covering version, review, and rollback at the workspace/agent-session level. However, the newer 'Routines' (scheduled/GitHub-Action automations) feature has no documented versioning, review, or rollback mechanism specific to the automation definitions themselves. Missing for 10: explicit version history/rollback for Routines/scheduled automations, independent hands-on confirmation of checkpoint reliability.

   • [claimed-docs] “Checkpoints | Session/workspace | Revert code and chat state to an earlier turn”
   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [claimed-docs] “Introducing routines! You can now run your agents on a schedule or via GitHub action.”
   • [claimed-docs] “Create a new workspace with Command + N when work should have its own branch, files, running environment, and review path.”

   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 drawn
   Cursor✓fullclaimed7/10

   Cursor's docs explicitly describe cloud/background agents that 'use their own computers to build, test, and demo features end to end for you to review,' plus the ability to launch fleets of agents working in parallel for hours/days, and always-on scheduled agents — directly matching the story. Corroboration is entirely first-party marketing/docs rather than independent hands-on verification of an actual demo workflow. Missing for 10: independent/hands-on evidence confirming the build-test-demo loop works reliably end-to-end, and detail on what 'demo' concretely produces (e.g., preview links, recordings).

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor✓fullclaimed7/10

   Conductor's cloud agents can autonomously test repos, update setup scripts, and run builds without step-by-step confirmation (conductor-docs-17, conductor-docs-32), continue working after the laptop closes (conductor-docs-20), and then help the user review the diff, open a PR, and merge (conductor-docs-21) — covering build, test, and review end-to-end for a feature. Missing for 10: no explicit 'demo' artifact (e.g., preview links/screenshots) beyond diff/PR review, and no independent/hands-on account confirming a full autonomous build-test-review cycle worked as described.

   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor✓fullclaimed8/10

   Cursor documents cloud/background agents ('Agents use their own computers to build, test, and demo features end to end', 'Launch fleets of agents that work in parallel on ambitious tasks for hours or days', and hand-off delegation while the developer focuses elsewhere), matching the isolated cloud-background-task story. Missing for 10: independent hands-on verification of the background agent's isolation/reliability and details on session duration limits or failure modes.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”

   proof ↗⚑ flag

   Conductor~partialcommunity7/10

   Docs describe a dedicated 'cloud workspace' feature where agents run in isolated sandboxes that 'spin up in seconds' and 'keep working after you close your laptop,' can test repos/run builds unattended, and continue processing PR checks while 'asleep' (conductor-docs-20, conductor-docs-17, conductor-docs-11, conductor-docs-13). However, community reports describe the core product as creating an isolated git worktree locally rather than a cloud container, contrasting it with Codex's cloud sandbox (conductor-comm-17, conductor-comm-6), suggesting the cloud-isolation capability may be a newer/optional layer rather than the default experience. Missing for 10: independent hands-on verification that background cloud tasks are fully isolated/persistent, and clarity on whether cloud workspaces are the default vs. opt-in given local-worktree-first community accounts.

   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “PR comments and failing-check logs now load while a cloud workspace is asleep.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [community] “We create an isolated git worktree locally on your machine — whereas Codex (I believe) is running a container on the cloud.”
   • [community] “I was really excited to try this but this does NOT work the way I expected. I wanted a simple git worktree manager for my existing, already-…”

   proof ↗⚑ flag

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

   weight 2 · round to Conductor
   Cursor~partialclaimed4/10

   Cursor's docs mention cloud/background agents that 'use their own computers to build, test, and demo features' and can be launched in fleets or run on schedules, implying some cloud execution environment, but there's no evidence pack detail on how a developer configures dependencies, install scripts, or a reproducible environment spec (e.g. Dockerfile/environment.json) for these agents. Missing for 10: explicit documentation of environment configuration format, dependency/setup step definition, and evidence of reproducibility across runs.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor~partialclaimed6/10

   Docs show Conductor's cloud workspaces spin up sandboxes, check for needed tools/credentials, and let agents edit install/setup scripts and run builds automatically, which supports configuring an environment with the right dependencies (conductor-docs-17, conductor-docs-20, conductor-docs-32, conductor-docs-33). However there's no explicit first-party description of a declarative, versioned environment-config file (e.g., a devcontainer-style spec) guaranteeing reproducibility across runs/teammates, and no independent confirmation that these setup scripts persist reliably across sessions. missing for 10: explicit reproducible-config artifact/spec, independent verification that environment setup is consistent across workspace recreations.

   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”
   • [claimed-docs] “When you open Conductor, it checks for the tools and credentials it needs. If anything is missing, Conductor walks you through setup.”

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

   First-party marketing/docs explicitly state the exact capability: "Launch fleets of agents that work in parallel on ambitious tasks for hours or days," plus supporting evidence of background/always-on agents and agents using their own compute to build/test/demo. No independent hands-on verification of multi-day parallel fleet execution is present, and no community corroboration confirms this specific feature works at scale. Missing for 10: independent/hands-on validation of parallel agent fleets running for hours/days, details on concurrency limits or reliability over long runs.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”

   proof ↗⚑ flag

   Conductor✓fullclaimed7/10

   Docs show Conductor explicitly designed for running multiple agents (Claude Code, Codex, Cursor, OpenCode) in parallel across isolated workspaces/worktrees, with cloud workspaces that 'keep working after you close your laptop' and 'routines' to run agents on a schedule or via GitHub Action, supporting long-running autonomous fleets. Community feedback focuses on GitHub permission/privacy concerns rather than disputing the parallel-autonomy capability itself. Missing for 10: independent/hands-on confirmation of agents actually running unattended for multi-day spans and evidence of fleet scale (e.g., dozens of simultaneous agents).

   • [claimed-docs] “Conductor lets you run Claude Code, Codex, Cursor, and OpenCode in parallel.”
   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [claimed-docs] “Introducing routines! You can now run your agents on a schedule or via GitHub action.”
   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “Create a new workspace with Command + N when work should have its own branch, files, running environment, and review path.”
   • [claimed-docs] “Run multiple agents in one workspace when the work belongs on the same branch and should share the same files and context.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”

   proof ↗⚑ flag

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

   weight 1 · round to Conductor
   Cursor~partialclaimed6/10

   Cursor's docs describe launching 'fleets of agents that work in parallel on ambitious tasks for hours or days,' directly supporting parallel task execution, and agents run in isolated environments for review before merging changes. However, there is no explicit documentation of a UI/workflow for comparing multiple parallel attempts side-by-side before choosing one, and no independent/hands-on evidence corroborating this specific comparison workflow. Missing for 10: dedicated compare/diff-across-attempts feature documentation, independent verification of parallel-agent comparison in practice.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor✓fullprobed8/10

   Conductor's core design is running multiple coding agents in parallel, each in its own isolated workspace/git worktree with its own branch, files, and diff/review path, letting a developer inspect and choose before merging (docs-2, docs-27, docs-29, docs-21, probe-1). Community hands-on comments corroborate the git-worktree-based parallel workspace model (conductor-comm-1, conductor-comm-17). missing for 10: explicit first-party description of a side-by-side comparison UI across multiple simultaneous attempts (evidence shows parallel isolated workspaces and per-workspace diff/review, but not an explicit 'compare attempts' feature or independent review confirming the comparison workflow).

   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”
   • [claimed-docs] “Create a new workspace with Command + N when work should have its own branch, files, running environment, and review path.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.conductor.build/llms.txt # Conductor > Conductor is a Mac app that lets you run many coding agents …”
   • [community] “Oh cool, I was already doing this with git worktrees but a ui for it would be handy.”
   • [community] “We create an isolated git worktree locally on your machine — whereas Codex (I believe) is running a container on the cloud.”

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

   Cursor's own site directly states the capability: "Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software," plus related background-agent features (parallel fleets, agents running on their own machines) that support this workflow. Missing for 10: independent/hands-on confirmation of scheduled/triggered agents actually running reliably in practice, and more detail on trigger types/configuration.

   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor~partialclaimed6/10

   Conductor documents 'routines' that run agents on a schedule or via GitHub Action, plus cloud agents that keep working after you close your laptop and can autonomously test, fix, and rebuild repos without step-by-step confirmation — directly supporting always-on autonomous maintenance. However, the routines feature is only briefly mentioned in a changelog entry with no deep documentation of trigger types, monitoring, or failure-handling, and no independent/hands-on evidence confirms long-running unattended reliability. Missing for 10: detailed docs on trigger configuration (webhooks, cron specifics), evidence of long-term unattended reliability, and community confirmation of the scheduling/autonomy feature working in practice.

   • [claimed-docs] “Introducing routines! You can now run your agents on a schedule or via GitHub action.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”

   proof ↗⚑ flag

Debugging

1. developerDebug issues and troubleshoot using natural-language queries

   weight 2 · round to Cursor
   Cursor~partialcommunity6/10

   cursor-docs-3 directly claims support for reproducing issues, narrowing root cause, and verifying fixes via natural-language-driven agent workflows, and docs-1 supports tracing how a repo fits together to find bug locations. However, there's no independent/hands-on evidence corroborating debugging quality, and community evidence highlights buginess and unreliability concerns (cursor-comm-2, cursor-comm-8) that add caveats without directly contradicting the specific debugging workflow claim. Missing for 10: independent verification of debugging accuracy, concrete examples of NL-driven troubleshooting sessions, and resolution of buggy-product complaints.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [community] “"Cursor is weird. They have a basically unused GitHub with a thousand unanswered Issues. It's so buggy in ways that VSCode isn't. I hate it.…”
   • [community] “"That's a lot of money for a buggy product that is at best slightly better than its competitors."”

   proof ↗⚑ flag

   Conductor~partialclaimed5/10

   Conductor orchestrates coding agents (Claude Code, Codex, Cursor) that support natural-language chat, and each workspace has its own terminal, diff, and chat interface, implying a developer could ask an agent to debug/troubleshoot via NL queries. However, there's no Conductor-specific documentation describing a dedicated debugging/troubleshooting NL workflow, error-log analysis, or diagnostic features beyond generic agent chat and build/test execution. Missing for 10: explicit docs on NL-driven debugging workflows, log/error analysis features, or examples of troubleshooting via chat distinct from general coding tasks.

   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”
   • [claimed-docs] “Checkpoints | Session/workspace | Revert code and chat state to an earlier turn”

   proof ↗⚑ flag

Feature implementation

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

   weight 3 · round to Conductor
   Cursor~partialclaimed7/10

   Cursor's docs describe agents that trace repos, plan changes, reproduce issues, inspect diffs/run checks, and integrate with issue trackers (GitHub, Linear) and PR review, which together support a full issue-to-PR workflow (cursor-docs-1 through cursor-docs-4, cursor-docs-6, cursor-docs-8–cursor-docs-12). However, there's no explicit first-party or independent case study showing a single tracked issue being turned into a merged PR end-to-end without manual intervention, and community evidence focuses on unrelated bugs/pricing complaints rather than this workflow. Missing for 10: a concrete end-to-end example/case study of issue→PR automation and independent verification that the full pipeline works reliably.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”
   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”
   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor✓fullclaimed7/10

   Docs show workspaces can be created directly from a GitHub issue (conductor-docs-12), agents run autonomously to implement, test, and build (conductor-docs-17, conductor-docs-20), and Conductor then helps review the diff, open a PR, merge, and archive the workspace (conductor-docs-21) — covering the full issue-to-PR loop. Missing for 10: independent/hands-on confirmation of the complete issue→PR flow (community evidence covers worktree/permissions concerns but not this specific workflow), and no example of a merged PR originating from an issue.

   • [claimed-docs] “Use Command + Shift + N or the `...` button next to `New workspace` to create a workspace from a branch, pull request, GitHub issue, or Line…”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”

   proof ↗⚑ 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 Cursor
   Cursor✓fullcommunity8/10

   Cursor's docs describe an agent that traces repo structure, plans and scopes multi-file changes, implements features/fixes end-to-end, runs checks, and produces diffs for review — directly matching plain-language feature/bug requests across multiple files. Community evidence corroborates the product is used daily for this purpose (albeit with complaints about bugginess), without disputing the core multi-file agentic editing capability. Missing for 10: independent hands-on benchmarks showing successful multi-file fixes, and no first-party demo/case study detailing a concrete before/after example.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”
   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [community] “"Cursor is weird. They have a basically unused GitHub with a thousand unanswered Issues. It's so buggy in ways that VSCode isn't. I hate it.…”
   • [community] “"That's a lot of money for a buggy product that is at best slightly better than its competitors."”

   proof ↗⚑ flag

   Conductor~partialcommunity6/10

   Conductor orchestrates underlying coding agents (Claude Code, Codex, Cursor, OpenCode) that implement plain-language feature requests across files, with workspaces, diffs, and PR flows supporting this, and community feedback confirms it works as a Claude Code-like workflow wrapper. However, the actual code-generation quality depends entirely on the underlying agent, not Conductor itself, and no hands-on example of a multi-file feature/bug fix is shown in the evidence. missing for 10: a concrete hands-on example of Conductor implementing a described feature/bug across multiple files, and clarity on Conductor's own contribution versus the wrapped agent's capability.

   • [claimed-docs] “Conductor lets you run Claude Code, Codex, Cursor, and OpenCode in parallel.”
   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [community] “I have been imagining something like this would be perfect for working with Claude Code... This feels like just a nice clean simple extensio…”
   • [community] “We create an isolated git worktree locally on your machine — whereas Codex (I believe) is running a container on the cloud.”

   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 Cursor
   Cursor~partialclaimed6/10

   Cursor's docs describe agents that write code, run tests/checks, and 'build, maintain, and fix' software autonomously (cursor-docs-3, cursor-docs-4, cursor-docs-9, cursor-docs-12), which implies test-writing and general maintenance tasks, but there is no explicit documentation of lint-error fixing, merge-conflict resolution, or dependency-update workflows specifically. missing for 10: explicit lint-fixing examples, explicit merge-conflict-resolution examples, explicit dependency-update examples, independent hands-on verification of these specific tasks.

   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor~partialclaimed5/10

   Docs confirm the underlying agents can test repositories, edit setup/install scripts, and run builds autonomously (conductor-docs-17, conductor-docs-32), which covers test-writing/fixing to some degree, but there is no explicit documentation or community evidence of lint-error fixing, merge-conflict resolution, or dependency updates as distinct capabilities. Missing for 10: explicit evidence of lint fixing, merge conflict resolution, and dependency-update automation.

   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”

   proof ↗⚑ flag

Codebase mapping

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

   weight 3 · round to Cursor
   Cursor~partialclaimed6/10

   Cursor's docs explicitly claim the ability to 'trace how a repo fits together and find the right places to start,' directly matching the story, but this is a single marketing-style doc line with no detailed walkthrough, feature docs (e.g., codebase indexing/@codebase chat), or independent corroboration of how it actually surfaces architecture understanding. Missing for 10: detailed documentation of the codebase-mapping/indexing feature itself, concrete examples of it locating relevant code, and independent/hands-on validation of accuracy.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”

   proof ↗⚑ flag

   Conductor—none0/10

   Conductor's evidence focuses on orchestrating parallel coding agents, worktrees, and workspace management, not on codebase comprehension features; the only related item is a basic file-content search (⌘⇧F), which does not constitute understanding how a codebase fits together or where to start making changes.

   • [claimed-docs] “Search file contents in your current local project or cloud workspace with ⌘⇧F.”

   proof ↗⚑ flag

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

   weight 3 · round to Cursor
   Cursor~partialclaimed4/10

   First-party docs claim Cursor can 'trace how a repo fits together and find the right places to start' (cursor-docs-1), implying automatic codebase mapping, but there's no detail on how context is auto-gathered (e.g., codebase indexing/@codebase) nor any independent/hands-on confirmation that it explains an unfamiliar codebase without manual file selection. Missing for 10: technical explanation of automatic context retrieval, independent user validation of whole-codebase explanation, and comparison to manual context selection workflows.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”

   proof ↗⚑ flag

   Conductor—none0/10

   Conductor's evidence focuses on orchestrating parallel agent workspaces, worktrees, git branches, and collaboration—not on any built-in whole-codebase mapping or explanation capability. The closest feature is manual file-content search (⌘⇧F), which requires the developer to search rather than having the agent autonomously map/explain the codebase.

   • [claimed-docs] “Search file contents in your current local project or cloud workspace with ⌘⇧F.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”

   proof ↗⚑ flag

Context management

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence describes persistent memory that automatically builds and recalls context across sessions; docs mention repo tracing, plan mode, and MCP integrations but nothing about cross-session memory recall.

   ⚑ flag

   Conductor—none0/10

   Evidence covers checkpoints (revert to earlier turn), static 'general preferences' for repo-wide instructions, and parallel workspace/session management, but nothing describes the agent automatically building or recalling memory across sessions (e.g., persistent knowledge base, learned context reuse). This is a fair axis for a coding-agent orchestration tool, so absence of evidence yields none.

   • [claimed-docs] “Checkpoints | Session/workspace | Revert code and chat state to an earlier turn”
   • [claimed-docs] “`General preferences` apply broad instructions to agents in a repository.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence in the pack mentions multi-root workspaces or including multiple project directories in a single Cursor session; docs cover repo navigation, MCP, agents, and integrations but not multi-directory context.

   ⚑ flag

   Conductor—none0/10

   Conductor's workspace model is built on git worktrees scoped to a single repository/branch per workspace (conductor-docs-27, conductor-docs-29), and there's no documentation of combining multiple project directories into one session. A community member explicitly requested multi-repo task support, implying it isn't currently available (conductor-comm-12).

   • [claimed-docs] “Create a new workspace with Command + N when work should have its own branch, files, running environment, and review path.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [community] “I've been looking for a tool like this, that lets Claude operate on multiple repos... but all the tools for background/multiplexing are alwa…”

   proof ↗⚑ flag

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

   weight 3 · round to Conductor
   Cursor~partialclaimed3/10

   Cursor's docs mention adding 'rules' as one of its features (alongside plugins, skills, MCPs) which aligns with the project-instructions concept, but the evidence pack gives no detail on how project rule files work, their scope, or how the agent applies them to enforce coding standards. missing for 10: documentation of the rules file format/location, examples of coding standards enforcement, independent confirmation the agent actually follows these instructions consistently.

   • [claimed-docs] “Add plugins, skills, MCPs, and rules from one place”

   proof ↗⚑ flag

   Conductor~partialclaimed4/10

   Docs mention 'General preferences' that 'apply broad instructions to agents in a repository,' which is the closest match to a project instructions/conventions file, but there is no detail on file format, location, or how it maps to underlying agents' native instruction files (e.g., CLAUDE.md). Missing for 10: documentation of the actual file/config mechanism, examples of setting coding standards, and independent confirmation it works across all supported agents (Claude Code, Codex, Cursor, OpenCode).

   • [claimed-docs] “`General preferences` apply broad instructions to agents in a repository.”

   proof ↗⚑ flag

Issue diagnosis

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

   weight 3 · round drawn
   Cursor~partialclaimed6/10

   cursor-docs-3 directly claims the exact capability ('Reproduce issues, narrow the root cause, and verify the fix'), and supporting docs on codebase tracing, diffs/checks, and agents running their own environments (cursor-docs-1, cursor-docs-4, cursor-docs-12) plausibly back this workflow. However, this is a first-party marketing/docs claim only, with no independent or hands-on corroboration of actual debugging workflows, and community evidence highlights general bugginess/quality concerns rather than validating this specific capability. Missing for 10: independent verification or hands-on case studies of reproduce/root-cause/verify-fix workflows, more detail on how reproduction (e.g., test running, log inspection) is concretely supported.

   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor~partialclaimed6/10

   Conductor provides isolated worktrees/workspaces where agents can run builds, tests, and setup scripts (conductor-docs-17, conductor-docs-32, conductor-docs-29), diff/PR review paths to verify fixes (conductor-docs-2, conductor-docs-21), and checkpoints to revert code/chat state when narrowing down a bad change (conductor-docs-18). These features support the reproduce→diagnose→verify loop, but the evidence is all first-party docs describing environment/orchestration features rather than direct debugging tooling (log inspection, stack traces, targeted bisection) or independent hands-on accounts of successfully reproducing/root-causing a bug. missing for 10: dedicated debugging/log-inspection features, independent user reports of using Conductor to isolate root causes or verify fixes end-to-end.

   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”
   • [claimed-docs] “Checkpoints | Session/workspace | Revert code and chat state to an earlier turn”
   • [claimed-docs] “Search file contents in your current local project or cloud workspace with ⌘⇧F.”

   proof ↗⚑ flag

Marketplace

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

   weight 1 · round to Cursor
   Cursor~partialclaimed6/10

   Cursor's docs mention a marketplace to 'Add plugins, skills, MCPs, and rules from one place' and detailed MCP support (custom servers, marketplace install, enterprise controls), enabling developers to extend the agent with specialized tool integrations. However, there's no dedicated documentation on a 'skills' framework distinct from MCP/rules, no examples of custom skill creation workflow, and no independent/community corroboration of this specific capability. Missing for 10: detailed skills documentation/tutorial, examples of custom skill authoring, independent hands-on validation.

   • [claimed-docs] “Add plugins, skills, MCPs, and rules from one place”
   • [claimed-docs] “Model Context Protocol (MCP) enables Cursor to connect to external tools and data sources.”
   • [claimed-docs] “Click "Add to Cursor" on a marketplace entry to install it and authenticate with OAuth.”
   • [claimed-docs] “Configure custom MCP servers with a JSON file”
   • [claimed-docs] “Enterprise admins can control which MCP servers users may run from the Cursor dashboard.”

   proof ↗⚑ flag

   Conductor—none0/10

   Conductor orchestrates existing coding agents (Claude Code, Codex, Cursor, OpenCode) and offers 'general preferences' for broad instructions, but there's no evidence of a custom skills/plugin/tool system for equipping agents with specialized capabilities; a community request even notes the lack of 'custom tools' in its menu (conductor-comm-2).

   • [claimed-docs] “`General preferences` apply broad instructions to agents in a repository.”
   • [community] “It'd be great to change the default branch used for creating new workspaces. I'd like the ability to add custom tools to the 'Open in...' me…”

   proof ↗⚑ flag

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

   weight 1 · round to Cursor
   Cursor✓fullclaimed7/10

   Cursor documents a marketplace for adding third-party plugins, skills, and MCP servers with OAuth authentication, plus native integrations with GitHub, GitLab, Slack, Linear, and more, letting teams plug partner-built tools/agents into their workflows, with enterprise admin controls over which servers are allowed. Missing for 10: independent/hands-on corroboration of using specific partner-built agent apps (vs. generic tool connectors) and clearer distinction between simple MCP data-tools and full third-party 'agent apps'.

   • [claimed-docs] “Add plugins, skills, MCPs, and rules from one place”
   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”
   • [claimed-docs] “Model Context Protocol (MCP) enables Cursor to connect to external tools and data sources.”
   • [claimed-docs] “Click "Add to Cursor" on a marketplace entry to install it and authenticate with OAuth.”
   • [claimed-docs] “Configure custom MCP servers with a JSON file”
   • [claimed-docs] “Enterprise admins can control which MCP servers users may run from the Cursor dashboard.”

   proof ↗⚑ flag

   Conductor~partialcommunity7/10

   Conductor natively integrates several third-party agent apps (Claude Code, Codex, Cursor, OpenCode) into its parallel-workspace workflow, with per-org connection configuration and subscription/API-key support, and even exposes its own MCP server so other agent clients can manage workspaces. However, community feedback shows requests for additional partners (Gemini CLI, Amazon Q) that aren't yet supported, indicating a fixed rather than open/extensible partner ecosystem. Missing for 10: an open plugin/marketplace model for arbitrary partner agents, and independent confirmation of seamless integration beyond the listed agents.

   • [claimed-docs] “Conductor lets you run Claude Code, Codex, Cursor, and OpenCode in parallel.”
   • [claimed-docs] “Configure cloud agent connections separately for each organization, and choose whether Claude Code, Codex, and Cursor use an API key or subs…”
   • [claimed-docs] “Sign in to your Cursor subscription for cloud workspaces.”
   • [claimed-docs] “Conductor's hosted Model Context Protocol (MCP) server lets ChatGPT, Claude, Codex, and other MCP clients manage your cloud workspaces.”
   • [community] “Love the design. does it build on electron? and will it support other code agents, like gemini cli, codex, opencode ext.”
   • [community] “Would be cool if I can use this with opencode, Amazon Q or whatever. I reckon the logic would be quite similar. Seen a few of these tools bu…”

   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 Conductor
   Cursor—none0/10

   Evidence shows integrations (GitHub, Slack, Linear), MCP/plugins, and rules configuration, but nothing describes a dedicated 'shared workspace' feature that unifies docs and repos into a common team source of truth — this is a fair ask for a team-oriented dev tool but unaddressed in the pack.

   ⚑ flag

   Conductor~partialclaimed4/10

   Conductor's cloud workspaces are shared with the whole organization and teammates can follow, reassign, or pick up the same workspace/chat, giving some sense of a shared team space tied to a repo (conductor-docs-24, conductor-docs-25, conductor-docs-16). However, there's no evidence of a workspace built from 'docs' (knowledge base, wiki, or design docs) alongside repos, or of any feature explicitly positioned as a team 'source of truth' beyond per-repo agent preferences. missing for 10: docs ingestion/aggregation into a workspace, explicit source-of-truth knowledge base feature, independent corroboration of team-wide shared-workspace usage.

   • [claimed-docs] “Workspaces and chats are shared with your organization, so a teammate can open the same workspace, follow the same conversation, and pick up…”
   • [claimed-docs] “browse everyone's work in **Home**, contribute to a teammate's chat, follow workspaces you care about, and hand work off with **Reassign to*…”
   • [claimed-docs] “Right-click the workspace and choose **Reassign to** to make a teammate responsible for it.”
   • [claimed-docs] “`General preferences` apply broad instructions to agents in a repository.”

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

   Cursor documents MCP support that connects to external tools/data sources, an MCP marketplace with OAuth install, and explicit integration with Slack alongside GitHub/GitLab/Linear/Jira-style trackers, plus Slack-based agent collaboration—covering the story's workflow-tool extension use case. Missing for 10: explicit first-party Jira/Google Drive connector documentation and independent hands-on verification of these integrations working end-to-end.

   • [claimed-docs] “Model Context Protocol (MCP) enables Cursor to connect to external tools and data sources.”
   • [claimed-docs] “Click "Add to Cursor" on a marketplace entry to install it and authenticate with OAuth.”
   • [claimed-docs] “Configure custom MCP servers with a JSON file”
   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”

   proof ↗⚑ flag

   Conductor—none0/10

   Evidence shows Conductor integrates with GitHub and Linear (issue/branch creation) and exposes an MCP server for managing cloud workspaces, but there is no mention of Jira, Slack, or Google Drive integrations anywhere in the docs or community evidence.

   ⚑ flag

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

   weight 2 · round to Cursor
   Cursor~partialclaimed7/10

   Cursor's docs explicitly list integrations with GitHub, GitLab, Slack, and Linear, and describe agents that run on triggers/schedules and collaborate in Slack or review PRs in GitHub, supporting the story's core claim. However, there's no detailed first-party documentation of the exact trigger mechanics per platform (e.g., a Linear ticket auto-spawning an agent) nor independent/hands-on confirmation that this works reliably. Missing for 10: platform-specific trigger documentation for each of GitHub/GitLab/Linear/Slack, and independent verification of the workflow in practice.

   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”

   proof ↗⚑ flag

   Conductor~partialclaimed5/10

   Conductor lets you create a workspace (kick off an agent task) from a GitHub branch, pull request, GitHub issue, or Linear issue, and can trigger agent runs via GitHub Actions/scheduled routines, but there is no evidence of GitLab or Slack integration for starting tasks. missing for 10: GitLab task-kickoff support, Slack task-kickoff support, and independent confirmation of these triggers working in practice.

   • [claimed-docs] “Use Command + Shift + N or the `...` button next to `New workspace` to create a workspace from a branch, pull request, GitHub issue, or Line…”
   • [claimed-docs] “Introducing routines! You can now run your agents on a schedule or via GitHub action.”

   proof ↗⚑ flag

Cross device continuity

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

   weight 2 · round to Conductor
   Cursor~partialclaimed5/10

   Cursor's Background Agents run remotely and can be monitored/interacted with via terminal, Slack, and GitHub PRs, implying a task could be checked or continued from different surfaces, but there is no explicit documentation of resuming a specific in-progress task from a different device or browser session. Missing for 10: explicit cross-device/browser session handoff documentation, hands-on confirmation of resuming a task started elsewhere, and details on state syncing across clients.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor~partialclaimed6/10

   Cloud workspaces are shared with the organization and support handoff via 'Reassign to' and shared links, so a teammate (or the same developer on another device) can open a workspace and pick up where they left off, and cloud agents keep working after the laptop closes. However, evidence is framed around team collaboration/handoff rather than explicit single-user cross-device continuity, and local (non-cloud) workspaces are tied to the machine's worktree. missing for 10: explicit documentation of the same developer resuming a *local* task from a different device, confirmation of seamless single-user cross-browser/device session continuity, and independent hands-on confirmation of this specific workflow.

   • [claimed-docs] “Workspaces and chats are shared with your organization, so a teammate can open the same workspace, follow the same conversation, and pick up…”
   • [claimed-docs] “browse everyone's work in **Home**, contribute to a teammate's chat, follow workspaces you care about, and hand work off with **Reassign to*…”
   • [claimed-docs] “The link opens the workspace in Conductor for any member of the organization.”
   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “Following is useful when someone else is assigned to the workspace but you want to keep it in your workflow.”

   proof ↗⚑ flag

Ide integration

1. developerView interactive diffs and share selected code as context from within my JetBrains IDE

   weight 1 · round drawn
   Cursor—none0/10

   The only evidence touching JetBrains is a single line listing JetBrains among integrations (cursor-docs-6), with no detail on interactive diffs or context-sharing features within a JetBrains IDE specifically. No documentation, screenshots, or community reports confirm this JetBrains-specific capability.

   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”

   proof ↗⚑ flag

   Conductor—none0/10

   Conductor is presented as a standalone Mac app with its own workspace/diff/terminal UI (conductor-docs-2, conductor-probe-1), not a JetBrains IDE plugin; none of the docs, changelog, or community threads mention any JetBrains integration, extension, or plugin for viewing diffs or sharing context from within a JetBrains IDE.

   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.conductor.build/llms.txt # Conductor > Conductor is a Mac app that lets you run many coding agents …”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Cursor✓fullcommunity7/10

   Cursor's docs describe an IDE-integrated assistant that traces repo structure, scopes changes via Plan Mode, reproduces issues, and hands off tasks while the developer reviews — all consistent with in-IDE contextual chat, and community commentary confirms it functions as a VS Code-based assistant with prompts/harness. missing for 10: no explicit citation naming a dedicated 'chat panel' UI or independent praise of chat quality/context-awareness specifically.

   • [claimed-docs] “Trace how a repo fits together and find the right places to start”
   • [claimed-docs] “Scope changes, use Plan Mode, and ship bigger work with confidence”
   • [claimed-docs] “Reproduce issues, narrow the root cause, and verify the fix”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [community] “"Cursor is an extension for VS Code, a harness and a bunch of prompts. They have their own model (Composer 2) which is based on Kimi K2.5, b…”

   proof ↗⚑ flag

   Conductor✓fullcommunity7/10

   Conductor provides each task/workspace its own chat, terminal, diff and review path directly alongside the running coding agent (Claude Code, Codex, Cursor, OpenCode), letting a developer converse with the assistant in context of their code (conductor-docs-2, conductor-docs-27). Community reports confirm the chat works locally against Claude Code with no meaningful complaint about chat context/quality beyond stylistic preference (conductor-comm-9, conductor-comm-15). Missing for 10: no evidence of a native plugin embedding this chat inside third-party IDEs like VS Code/JetBrains (it's a separate Mac app), and no independent hands-on review of contextual-help quality beyond one HN thread.

   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [claimed-docs] “Create a new workspace with Command + N when work should have its own branch, files, running environment, and review path.”
   • [community] “There's a 'feel' to the way Claude Code outputs the text. And for input as well. Sadly, this is lost with conductor. I just don't feel as jo…”
   • [community] “Your messages are just between you and Claude Code — it all runs on your local Claude Code installation via the SDK.”

   proof ↗⚑ flag

Session management

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

   weight 2 · round to Conductor
   Cursor✓fullclaimed6/10

   Cursor's docs explicitly describe inspecting diffs before merge and launching fleets of agents to work in parallel, both core to a desktop IDE experience with visual diff review and concurrent sessions. Missing for 10: independent/hands-on confirmation of the side-by-side session UI and a detailed walkthrough of the diff viewer beyond marketing copy.

   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor✓fullprobed8/10

   Conductor is a native desktop (Mac) app that runs multiple coding agents (Claude Code, Codex, Cursor, OpenCode) in parallel, each in its own workspace/branch/worktree with a dedicated diff and review path before opening a PR, and community users independently confirm the git-worktree-based parallel session model. Missing for 10: independent hands-on evaluation specifically praising the visual diff-review UI's quality/UX (only vendor docs describe the diff view) and no screenshots/video corroboration.

   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”
   • [claimed-docs] “Create a new workspace with Command + N when work should have its own branch, files, running environment, and review path.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.conductor.build/llms.txt # Conductor > Conductor is a Mac app that lets you run many coding agents …”
   • [community] “Oh cool, I was already doing this with git worktrees but a ui for it would be handy.”
   • [community] “We create an isolated git worktree locally on your machine — whereas Codex (I believe) is running a container on the cloud.”

   proof ↗⚑ flag

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

   weight 2 · round to Conductor
   Cursor✓fullclaimed7/10

   Cursor's docs explicitly describe launching 'fleets of agents that work in parallel on ambitious tasks for hours or days' and setting up always-on agents on schedules/triggers, all accessible from Cursor's interface spanning terminal, Slack, and GitHub — directly matching a unified multi-session agent workspace for a lead overseeing parallel work. Missing for 10: independent/hands-on corroboration of the multi-agent dashboard UX, and no detail on cross-session visibility/coordination features specifically framed for engineering-lead oversight.

   • [claimed-docs] “Launch fleets of agents that work in parallel on ambitious tasks for hours or days.”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Accelerate development by handing off tasks to Cursor, while you focus on making decisions.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor✓fullcommunity8/10

   Conductor is explicitly built as a unified workspace for running multiple coding agents (Claude Code, Codex, Cursor, OpenCode) in parallel, each with its own workspace/branch/terminal/diff, plus team collaboration features (reassign, follow, shared workspaces) that support engineering-lead oversight. Community hands-on posts corroborate the parallel-agent workflow, though some raised concerns about permissions/data practices unrelated to the core multi-session management claim. missing for 10: independent lead-level testimony specifically on cross-team oversight at scale, and clearer evidence of a dashboard view aggregating all sessions' status for a lead.

   • [claimed-docs] “Conductor lets you run Claude Code, Codex, Cursor, and OpenCode in parallel.”
   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [claimed-docs] “Workspaces and chats are shared with your organization, so a teammate can open the same workspace, follow the same conversation, and pick up…”
   • [claimed-docs] “browse everyone's work in **Home**, contribute to a teammate's chat, follow workspaces you care about, and hand work off with **Reassign to*…”
   • [claimed-docs] “Create a new workspace with Command + N when work should have its own branch, files, running environment, and review path.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [community] “I have been imagining something like this would be perfect for working with Claude Code... This feels like just a nice clean simple extensio…”
   • [community] “Oh cool, I was already doing this with git worktrees but a ui for it would be handy.”

   proof ↗⚑ flag

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round to Cursor
   Cursor✓fullprobed7/10

   Cursor ships an official CLI (cursor.com/cli) with a documented install command (curl ... | bash) and docs explicitly state 'Cursor runs in your terminal', confirming a local terminal-based agent capability alongside its IDE. Missing for 10: independent/hands-on verification of terminal agent usage and deeper CLI usage documentation beyond the install step.

   • [probe] “official CLI documented at https://cursor.com/cli”
   • [claimed-docs] “curl https://cursor.com/install -fsS | bash”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”

   proof ↗⚑ flag

   Conductor~partialprobed7/10

   Conductor documents running local coding agents (Claude Code, Codex, Cursor, OpenCode) with per-task local git worktrees and a dedicated terminal per workspace, and community confirms it runs the agent locally via the local CLI/SDK install (conductor-comm-15, conductor-comm-17). However, hands-on reports show it isn't a pure lightweight local terminal wrapper—it requires GitHub OAuth/cloning rather than just running an existing local repo, and some users complain the local CLI 'feel' (e.g., Claude Code's native terminal UX) is lost inside Conductor's GUI (conductor-comm-6, conductor-comm-9). Missing for 10: independent confirmation that pure terminal-only (non-GUI) workflows are fully supported, and clearer first-party disclosure addressing the community concerns about local vs. cloud/GitHub dependency.

   • [claimed-docs] “Conductor lets you run Claude Code, Codex, Cursor, and OpenCode in parallel.”
   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [community] “Your messages are just between you and Claude Code — it all runs on your local Claude Code installation via the SDK.”
   • [community] “We create an isolated git worktree locally on your machine — whereas Codex (I believe) is running a container on the cloud.”
   • [community] “I was really excited to try this but this does NOT work the way I expected. I wanted a simple git worktree manager for my existing, already-…”
   • [community] “There's a 'feel' to the way Claude Code outputs the text. And for input as well. Sadly, this is lost with conductor. I just don't feel as jo…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.conductor.build/llms.txt # Conductor > Conductor is a Mac app that lets you run many coding agents …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor~partialprobed6/10

   Cursor ships an official CLI (cursor-probe-1, cursor-docs-14) and documents 'always-on agents that run on schedules or triggers to build, maintain, and fix your software' (cursor-docs-9), which implies non-interactive/automated agent execution suitable for scripts/CI. However, there is no concrete documentation of CLI flags, headless/print modes, exit codes, or scripting examples, nor independent hands-on confirmation of this workflow. Missing for 10: explicit CLI non-interactive flag/usage docs, examples of piping/scripting the agent, and independent verification that scheduled/triggered agents work as scripted automation.

   • [probe] “official CLI documented at https://cursor.com/cli”
   • [claimed-docs] “curl https://cursor.com/install -fsS | bash”
   • [claimed-docs] “Set up always-on agents that run on schedules or triggers to build, maintain, and fix your software.”

   proof ↗⚑ flag

   Conductor~partialclaimed6/10

   Conductor exposes a programmatic API to create workspaces, send prompts and read agent replies, and supports 'routines' to run agents on a schedule or via GitHub Action, which enables non-interactive, scripted automation of the agent outside the GUI. However, this is all first-party documentation with no independent/hands-on confirmation, and Conductor is fundamentally a GUI-first Mac app rather than a CLI tool built for scripting. Missing for 10: independent verification that the API/routines work reliably in real automation pipelines, and clearer CLI-style invocation/flags for non-interactive use.

   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [claimed-docs] “Introducing routines! You can now run your agents on a schedule or via GitHub action.”
   • [claimed-docs] “Conductor's hosted Model Context Protocol (MCP) server lets ChatGPT, Claude, Codex, and other MCP clients manage your cloud workspaces.”

   proof ↗⚑ flag

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

   weight 2 · round to Conductor
   Cursor—none0/10

   The evidence pack shows no public API for Cursor; it mentions an official CLI and MCP (for connecting external tools INTO Cursor), but nothing about a programmatic interface exposing Cursor's own UI capabilities (agents, plan mode, review, etc.) for external control.

   ⚑ flag

   Conductor~partialprobed5/10

   Conductor documents a programmatic API and a hosted MCP server that let you create cloud workspaces, send prompts, and read agent replies, giving genuine API access to core agent workflows (conductor-docs-13, conductor-docs-14, conductor-docs-30, conductor-probe-4). However, the API is explicitly scoped to 'cloud workspaces' only, with no evidence it exposes local workspace/worktree management, collaboration features (reassign, follow, sharing), settings like port forwarding, or UI-specific conveniences (loadouts, sections, checkpoints) — and no OpenAPI spec is discoverable (conductor-probe-3), suggesting the API surface is narrower than the full UI. missing for 10: full parity coverage of local workspace/git-worktree operations via API, coverage of collaboration/organization features via API, and a public OpenAPI spec or independent confirmation of API completeness.

   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”
   • [claimed-docs] “Conductor's hosted Model Context Protocol (MCP) server lets ChatGPT, Claude, Codex, and other MCP clients manage your cloud workspaces.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically. Use it to do things like: Create workspaces, send prompts to the coding…”
   • [probe] “official MCP server documented at https://www.conductor.build/docs/api/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.conductor.build/openapi.json, https://www.conductor.build/swagger.json, https://www.cond…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Cursor—none0/10

   No evidence in the pack addresses data export, portability, or open-format data extraction from Cursor; being built on VS Code (a fork) doesn't itself guarantee user data/settings export tooling is documented anywhere here.

   ⚑ flag

   Conductor—none0/10

   Conductor stores workspace state, chat history, and cloud workspace data, but no evidence in the pack shows an explicit data-export feature or open-format export guarantee; while code lives in git worktrees (inherently portable), there's no documentation of exporting chats, settings, or cloud workspace metadata. Community threads even raise unresolved concerns about data practices and lack of transparency (conductor-comm-3, conductor-comm-5), reinforcing the absence of an export/leave story.

   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [community] “Love it! Even just simply freeing my main branch would be a big win so I can keep working as well. But no way to find out if there's any dat…”
   • [community] “Full read-write access required to all your Github account's repos. Not just code. Settings, deploy keys. The works... Zero disclosure of da…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   Cursor is known to be closed-source (a proprietary VS Code fork), and the evidence pack contains no mention of any open-source license or public repository for Cursor's source code; all references are to product docs, features, or community complaints unrelated to licensing.

   ⚑ flag

   Conductor—none0/10

   There is no evidence Conductor's source is available under any open license; it is distributed as a compiled Mac app with docs/API only, and a community comment explicitly contrasts it with an open-source alternative ('Crystal... unlike Conductor is open source'), indicating Conductor's source is not open.

   • [community] “Crystal can do all of this and more, and unlike Conductor is open source.”

   proof ↗⚑ flag

Authentication

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

   weight 2 · round to Conductor
   Cursor—none0/10

   No evidence in the pack describes API key authentication as an alternative to account login for Cursor; docs reference OAuth-based MCP authentication and account-based login flows only.

   ⚑ flag

   Conductor✓fullclaimed7/10

   Conductor explicitly supports 'bring your own subscriptions and keys' and lets you configure Claude Code, Codex, and Cursor connections to use an API key instead of a subscription/account login per organization. This directly satisfies the developer's need to authenticate via API key rather than an account login flow. missing for 10: independent/hands-on confirmation that API-key auth works end-to-end without any account sign-in step, and detail on whether Conductor's own app access also supports API-key-only login (vs. GitHub OAuth).

   • [claimed-docs] “Bring your own subscriptions and keys”
   • [claimed-docs] “Configure cloud agent connections separately for each organization, and choose whether Claude Code, Codex, and Cursor use an API key or subs…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   The evidence pack shows Cursor has enterprise admin controls for MCP servers but contains no evidence of SSO/SAML integration, enterprise identity provider authentication (e.g., Okta, Azure AD, Google Workspace), or cloud platform login for compliance purposes. This is a fair and applicable axis for a widely-adopted dev tool sold to enterprises, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Enterprise admins can control which MCP servers users may run from the Cursor dashboard.”

   proof ↗⚑ flag

   Conductor—none0/10

   Evidence shows only GitHub OAuth/GitHub App authentication and per-organization agent connection settings (conductor-comm-13, conductor-comm-14, conductor-docs-23); there is no mention of SSO, SAML, OIDC, or enterprise identity provider integration for compliance/scale. missing for 10: SSO/SAML/OIDC support, enterprise IdP integration, admin/compliance controls tied to identity.

   • [community] “Right now the app uses GitHub's OAuth sign in which unfortunately doesn't allow for fine-grained permissions... We're switching our sign-in …”
   • [community] “Fixed! You can now give Conductor fine-grained GitHub repository access. Or, skip the integration and use your local GitHub CLI auth.”
   • [claimed-docs] “Configure cloud agent connections separately for each organization, and choose whether Claude Code, Codex, and Cursor use an API key or subs…”

   proof ↗⚑ flag

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

   weight 2 · round to Conductor
   Cursor—none0/10

   The evidence pack describes Cursor's agent features, MCP integrations, and installation steps, but contains no documentation or confirmation that users authenticate with an existing subscription plan to access the coding agent (only tangential community chatter about login policy hallucinations). Missing for 10: explicit account/subscription sign-in flow docs, plan-tier access confirmation, and any first-party statement linking subscription plan to agent usage.

   • [community] “Cursor's AI support agent hallucinated a single-device login policy, telling a user this was intentional. A Cursor developer later clarified…”

   proof ↗⚑ flag

   Conductor✓fullclaimed8/10

   Docs explicitly state you can 'bring your own subscriptions and keys' and sign in with existing Cursor, Claude Code, or Codex subscriptions rather than requiring a separate Conductor-specific plan, with per-organization control over subscription vs API key. Missing for 10: independent hands-on confirmation that subscription sign-in works smoothly across all supported agents (only vendor changelog/docs evidence).

   • [claimed-docs] “Bring your own subscriptions and keys”
   • [claimed-docs] “Sign in to your Cursor subscription for cloud workspaces.”
   • [claimed-docs] “Configure cloud agent connections separately for each organization, and choose whether Claude Code, Codex, and Cursor use an API key or subs…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Cursor—none0/10

   The evidence pack contains no documentation or first-party description of a sign-in flow that grants free-tier access without requiring API keys; only tangential community mentions of account workarounds for usage limits exist. Missing for 10: any docs on account creation/sign-in, free-tier terms, or explicit no-API-key requirement.

   • [community] “Cursor is caught in a cat-and-mouse game against workarounds where users create new accounts to get unlimited use; a repo enabling this (cur…”

   proof ↗⚑ flag

   Conductor—none0/10

   Conductor's docs describe a 'bring your own subscriptions and keys' model where users must sign in to their own Claude Code, Codex, or Cursor subscription or supply an API key (conductor-docs-19, conductor-docs-23, conductor-docs-7); there is no mention of a free tier accessible purely via personal account sign-in without managing credentials. Community discussion also focuses on GitHub OAuth/permissions issues, not a free-tier access model.

   • [claimed-docs] “Bring your own subscriptions and keys”
   • [claimed-docs] “Configure cloud agent connections separately for each organization, and choose whether Claude Code, Codex, and Cursor use an API key or subs…”
   • [claimed-docs] “Sign in to your Cursor subscription for cloud workspaces.”

   proof ↗⚑ flag

Model choice

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

   weight 1 · round drawn
   Cursor—none0/10

   The evidence shows Cursor lets developers manually choose among multiple models (OpenAI, Anthropic, Gemini, etc.) but nothing indicates an automatic 'best model for the task' selection feature. missing for 10: any documentation or claim of an auto-select/router feature that picks models per task, evidence of cost/performance-based automatic routing.

   • [claimed-docs] “Choose between every cutting-edge model from OpenAI, Anthropic, Gemini, SpaceXAI, and Cursor.”

   proof ↗⚑ flag

   Conductor—none0/10

   Conductor documents manual model selection via 'loadouts' and keyboard shortcuts to switch between chosen models, but there is no evidence of an automatic mechanism that picks the best model per task based on cost/performance tradeoffs.

   • [claimed-docs] “Pick a loadout of your favorite models to quickly switch between. It’s keyboard accessible too: change models (⌃⌘ 1-5), effort (⌘⇧/), speed …”
   • [claimed-docs] “Configure cloud agent connections separately for each organization, and choose whether Claude Code, Codex, and Cursor use an API key or subs…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor✓fullclaimed8/10

   cursor-docs-7 confirms Cursor lets developers choose between models from multiple providers (OpenAI, Anthropic, Gemini, and Cursor's own), directly matching the story. Missing for 10: independent hands-on verification of per-session model switching UI/behavior and pricing implications tied to model choice.

   • [claimed-docs] “Choose between every cutting-edge model from OpenAI, Anthropic, Gemini, SpaceXAI, and Cursor.”

   proof ↗⚑ flag

   Conductor✓fullcommunity8/10

   Conductor explicitly supports running Claude Code, Codex, Cursor, and OpenCode as interchangeable providers, with a 'loadout' UI and keyboard shortcuts to switch models per session, plus per-organization configuration of API key vs subscription for each provider. Community comments confirm interest in and some support for multi-agent/provider use, though no independent hands-on review specifically validates seamless mid-session switching. Missing for 10: independent/hands-on verification of the model-switching UX and confirmation across all listed providers beyond vendor docs.

   • [claimed-docs] “Conductor lets you run Claude Code, Codex, Cursor, and OpenCode in parallel.”
   • [claimed-docs] “Pick a loadout of your favorite models to quickly switch between. It’s keyboard accessible too: change models (⌃⌘ 1-5), effort (⌘⇧/), speed …”
   • [claimed-docs] “Configure cloud agent connections separately for each organization, and choose whether Claude Code, Codex, and Cursor use an API key or subs…”
   • [community] “Love the design. does it build on electron? and will it support other code agents, like gemini cli, codex, opencode ext.”
   • [community] “Would be cool if I can use this with opencode, Amazon Q or whatever. I reckon the logic would be quite similar. Seen a few of these tools bu…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls for Cursor; the docs snippets cover agents, MCP, and integrations but nothing about choosing data storage region. Missing for 10: any mention of regional data residency options, enterprise data location controls, or compliance documentation addressing storage jurisdiction.

   ⚑ flag

   Conductor—none0/10

   No evidence anywhere in the pack addresses data residency, region selection, or storage location controls for cloud workspaces; community comments even highlight lack of disclosure about where data is sent.

   • [community] “Love it! Even just simply freeing my main branch would be a big win so I can keep working as well. But no way to find out if there's any dat…”
   • [community] “Full read-write access required to all your Github account's repos. Not just code. Settings, deploy keys. The works... Zero disclosure of da…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Cursor—none0/10

   The evidence pack contains no documentation of a privacy mode, opt-out of training, or data-retention controls for Cursor; all cited docs cover unrelated features (agents, MCP, integrations) and community threads are unrelated to training-data privacy.

   ⚑ flag

   Conductor—none0/10

   No documentation or policy statement anywhere in the evidence pack addresses training-data opt-out or data-usage controls; in fact community reports explicitly note 'no way to find out if there's any data sent to your servers' and 'zero disclosure of data practices,' underscoring the absence of any such privacy control.

   • [community] “Love it! Even just simply freeing my main branch would be a big win so I can keep working as well. But no way to find out if there's any dat…”
   • [community] “Full read-write access required to all your Github account's repos. Not just code. Settings, deploy keys. The works... Zero disclosure of da…”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Cursor—none0/10

   The evidence pack contains no documentation of data retention settings, deletion controls, privacy dashboard, or data handling policies for Cursor; only unrelated docs on features (MCP, agents, integrations) and community complaints about bugs/pricing are present. Missing for 10: any first-party privacy policy docs, retention period settings, data deletion request mechanism, or enterprise data controls.

   ⚑ flag

   Conductor—none0/10

   No documentation describes retention periods, data-deletion controls, or export/purge mechanisms for cloud workspace data; community feedback explicitly flags 'zero disclosure of data practices' and no way to verify what is sent to Conductor's servers.

   • [community] “Love it! Even just simply freeing my main branch would be a big win so I can keep working as well. But no way to find out if there's any dat…”
   • [community] “Full read-write access required to all your Github account's repos. Not just code. Settings, deploy keys. The works... Zero disclosure of da…”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Cursor—none0/10

   The evidence pack contains no mention of telemetry settings, privacy controls, or usage-tracking opt-out mechanisms; docs only cover unrelated features like MCP, agents, and integrations. Missing for 10: any privacy policy or settings documentation, telemetry opt-out toggle, or usage data collection disclosure.

   ⚑ flag

   Conductor—none0/10

   No documentation or changelog entry describes any telemetry/usage-tracking settings or an opt-out mechanism; community commenters explicitly note there is 'no way to find out if there's any data sent to your servers' and 'zero disclosure of data practices,' confirming the absence of any documented privacy control for telemetry.

   • [community] “Love it! Even just simply freeing my main branch would be a big win so I can keep working as well. But no way to find out if there's any dat…”
   • [community] “Full read-write access required to all your Github account's repos. Not just code. Settings, deploy keys. The works... Zero disclosure of da…”

   proof ↗⚑ flag

Data governance

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

   weight 1 · round drawn
   Cursor—none0/10

   The evidence pack contains no mention of privacy settings, opt-out of training, or data usage policies for Cursor; all docs entries relate to unrelated features (agents, MCP, integrations) and community items focus on bugs/pricing/model sourcing, not training data controls.

   ⚑ flag

   Conductor—none0/10

   No evidence anywhere in the pack of a data-usage/training opt-out policy or setting; in fact community reports explicitly complain about 'zero disclosure of data practices' and no way to find out what is sent to Conductor's servers, reinforcing the absence of any documented opt-out mechanism.

   • [community] “Love it! Even just simply freeing my main branch would be a big win so I can keep working as well. But no way to find out if there's any dat…”
   • [community] “Full read-write access required to all your Github account's repos. Not just code. Settings, deploy keys. The works... Zero disclosure of da…”

   proof ↗⚑ flag

Pr review

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

   weight 3 · round to Conductor
   Cursor~partialclaimed4/10

   Docs show GitHub/GitLab integration and agents that build/test/demo work end-to-end for review (cursor-docs-6, cursor-docs-10, cursor-docs-12), implying some git-workflow automation, but there's no explicit documentation of the agent staging changes, writing commit messages, creating branches, or opening pull requests. missing for 10: explicit commit-message generation, branch creation, PR-opening workflow documentation, and any hands-on confirmation these steps work end-to-end.

   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”

   proof ↗⚑ flag

   Conductor✓fullcommunity8/10

   Docs explicitly state each task gets its own branch/worktree, agents can be given autonomy to test/build without confirmation, and Conductor 'helps you review the diff, open a pull request, merge, and archive the workspace' — covering branch creation, staging/commits (implied by agent workflow), diffs, and PR creation. Community evidence corroborates git worktree branch isolation and GitHub integration for PR workflows. Missing for 10: explicit first-party mention of 'commit message writing' as a distinct feature and independent hands-on confirmation of the full stage→commit→branch→PR pipeline working end-to-end.

   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”
   • [claimed-docs] “Create a new workspace with Command + N when work should have its own branch, files, running environment, and review path.”
   • [claimed-docs] “Conductor creates a separate working tree for each workspace. That lets agents work in parallel without editing the same files on disk.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [community] “We create an isolated git worktree locally on your machine — whereas Codex (I believe) is running a container on the cloud.”
   • [community] “Fixed! You can now give Conductor fine-grained GitHub repository access. Or, skip the integration and use your local GitHub CLI auth.”

   proof ↗⚑ flag

2. developerGet automatic code review with contextual feedback on every pull request

   weight 3 · round to Cursor
   Cursor✓fullclaimed7/10

   Cursor's docs explicitly claim it 'reviews PRs in GitHub' and can 'inspect diffs, run checks, and catch problems before you merge,' directly matching automated PR review with contextual feedback, backed by GitHub/GitLab/Bitbucket integration claims. missing for 10: independent/hands-on verification of review quality, details on triggering on every PR automatically, and no community corroboration of this specific feature.

   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Work with GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, Linear, and more”

   proof ↗⚑ flag

   Conductor—none0/10

   Conductor's evidence describes parallel agent orchestration, diffs, and human-facing review workflows (e.g., 'Conductor helps you review the diff, open a pull request' and PR comments loading from GitHub) but no automated code-review bot that posts contextual feedback on pull requests. No evidence of an AI reviewer analyzing PR diffs and commenting automatically.

   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”
   • [claimed-docs] “PR comments and failing-check logs now load while a cloud workspace is asleep.”

   proof ↗⚑ flag

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

   weight 3 · round to Conductor
   Cursor~partialclaimed5/10

   cursor-docs-4 explicitly claims the capability ('Inspect diffs, run checks, and catch problems before you merge') and cursor-docs-10/12 support a broader PR review workflow, but there is no independent or hands-on corroboration of diff inspection or check-running in practice, and community evidence focuses on unrelated bugs/pricing rather than this feature. missing for 10: independent verification of diff review UI, details on what 'checks' run (tests/linters/CI), and hands-on confirmation of pre-merge workflow.

   • [claimed-docs] “Inspect diffs, run checks, and catch problems before you merge”
   • [claimed-docs] “Cursor runs in your terminal, collaborates in Slack, and reviews PRs in GitHub.”
   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor~partialclaimed6/10

   Docs show each workspace has its own diff and review path, and Conductor explicitly helps you 'review the diff, open a pull request, merge' before finishing work, plus it surfaces PR comments and failing-check logs even while a cloud workspace sleeps, and agents can run builds/tests as part of setup. However, there's no detailed description of built-in linting/test-runner integration beyond agent-run builds, and no independent/hands-on confirmation that this catches real problems pre-merge. Missing for 10: dedicated CI/check-running feature docs, independent verification of diff/check accuracy, and coverage of how failing checks block or warn before merge.

   • [claimed-docs] “Each task gets its own workspace, branch, files, terminal, diff, and review path.”
   • [claimed-docs] “When the work is ready, Conductor helps you review the diff, open a pull request, merge, and archive the workspace.”
   • [claimed-docs] “PR comments and failing-check logs now load while a cloud workspace is asleep.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [claimed-docs] “You can also have an agent configure the computer for you: it can test your repositories, edit setup scripts, and run builds.”

   proof ↗⚑ flag

Safe execution

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

   weight 2 · round to Cursor
   Cursor✓fullclaimed8/10

   Docs show enterprise admins can restrict which MCP servers users may run from the Cursor dashboard, and users can toggle individual servers on/off, giving engineering leads direct control over external tool/integration access. Missing for 10: independent/hands-on corroboration of the admin dashboard controls and finer-grained per-tool permission examples beyond MCP servers.

   • [claimed-docs] “Enterprise admins can control which MCP servers users may run from the Cursor dashboard.”
   • [claimed-docs] “Toggle servers on/off without removing them”
   • [claimed-docs] “Model Context Protocol (MCP) enables Cursor to connect to external tools and data sources.”
   • [claimed-docs] “Configure custom MCP servers with a JSON file”

   proof ↗⚑ flag

   Conductor~partialcommunity5/10

   Conductor lets an org configure agent connections per organization (choosing API-key vs subscription per agent) and, after community pushback over full GitHub OAuth access, added fine-grained GitHub repository permissions or local GitHub CLI auth as an alternative [conductor-docs-23, conductor-comm-13, conductor-comm-14]. However there's no documented allow-list/deny-list for arbitrary external tools, MCP servers, or third-party integrations beyond GitHub scopes and model provider choice, and the initial full-write-access design (comm-4, comm-5, comm-6) shows the control was originally coarse and only partially remedied. missing for 10: granular per-tool/integration allow-listing beyond GitHub and model provider, admin-level policy enforcement across the org, and independent verification that fine-grained access covers all agent-invoked external services (e.g., MCP servers).

   • [claimed-docs] “Configure cloud agent connections separately for each organization, and choose whether Claude Code, Codex, and Cursor use an API key or subs…”
   • [community] “Any way to have it not require full write access to your entire GitHub account?”
   • [community] “Full read-write access required to all your Github account's repos. Not just code. Settings, deploy keys. The works... Zero disclosure of da…”
   • [community] “Right now the app uses GitHub's OAuth sign in which unfortunately doesn't allow for fine-grained permissions... We're switching our sign-in …”
   • [community] “Fixed! You can now give Conductor fine-grained GitHub repository access. Or, skip the integration and use your local GitHub CLI auth.”

   proof ↗⚑ flag

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

   weight 2 · round to Conductor
   Cursor—none0/10

   The evidence pack contains no mention of sandboxing, isolated execution environments, or network/tool restriction controls for the agent; docs describe agents using 'their own computers' but give no detail on containment/sandboxing mechanisms. Missing for 10: any documentation of a sandbox/isolation feature, network egress controls, or filesystem restriction for agent actions.

   • [claimed-docs] “Agents use their own computers to build, test, and demo features end to end for you to review.”

   proof ↗⚑ flag

   Conductor~partialcommunity5/10

   Conductor's cloud workspaces are explicitly described as spinning up in "sandboxes" and the agent can run builds/tests without step-by-step confirmation, suggesting isolated execution for cloud mode. However, the local mode (the primary use case per community feedback) uses plain git worktrees on the user's own machine with no described network/tool sandboxing, and early versions required full read-write GitHub account access with no disclosed data practices, which is the opposite of a hardened sandbox model (though later mitigated with fine-grained GitHub App permissions). Missing for 10: explicit sandbox isolation details (container/VM boundaries, network egress controls) for local workspaces, and independent confirmation that cloud sandboxes restrict network/tool access beyond marketing language.

   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “The agent can test your repositories, update install and setup scripts, and run builds — without asking you to confirm each step.”
   • [community] “We create an isolated git worktree locally on your machine — whereas Codex (I believe) is running a container on the cloud.”
   • [community] “Any way to have it not require full write access to your entire GitHub account?”
   • [community] “Full read-write access required to all your Github account's repos. Not just code. Settings, deploy keys. The works... Zero disclosure of da…”
   • [community] “Right now the app uses GitHub's OAuth sign in which unfortunately doesn't allow for fine-grained permissions... We're switching our sign-in …”
   • [community] “Fixed! You can now give Conductor fine-grained GitHub repository access. Or, skip the integration and use your local GitHub CLI auth.”

   proof ↗⚑ flag

Security checks

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

   weight 1 · round drawn
   Cursor—none0/10

   No evidence anywhere in the pack mentions license detection, public code matching, provenance references, or IP attribution for AI-suggested code; docs focus on repo navigation, diffs, agents, and integrations, none of which addresses license/code-match transparency.

   ⚑ flag

   Conductor—none0/10

   No evidence anywhere in the pack of license compliance checks, public-code/plagiarism matching, or provenance references for AI-suggested code; Conductor's documentation focuses on orchestration, workspaces, and diffs/PRs but never mentions license or code-provenance scanning.

   ⚑ flag