cubic vs Conductor

Agent access

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

   weight 2 · round drawn
   cubic✓fullprobed9/10

   cubic hosts a dedicated llms.txt file at docs.cubic.dev/llms.txt (confirmed via live probe returning HTTP 200 with a documentation summary), directly enabling agents to be pointed at agent-oriented docs; this is reinforced by MCP server and CLI docs designed for agent consumption. Missing for 10: no independent/community confirmation of an agent successfully using llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.cubic.dev/llms.txt # cubic documentation > cubic reviews code on GitHub and in local coding workfl…”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   proof ↗⚑ 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
   cubic~partialprobed6/10

   cubic automatically reviews PRs once installed (headless, event-triggered automation on GitHub) and ships a standalone CLI (`cubic review`) that can run local/pre-push checks, which could be scripted into CI. However, there's no explicit documentation of a CI/CD pipeline integration (e.g., GitHub Actions workflow, exit codes, non-interactive flags) confirming true headless CI usage beyond the GitHub-app webhook flow. missing for 10: explicit CI pipeline integration docs/examples, confirmation of non-interactive/exit-code behavior for CLI in automated pipelines.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “Run a review before you push to catch issues while you're working.... review your uncommitted changes: `cubic review`”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [claimed-docs] “cubic automatically starts reviewing new pull requests in your selected repositories.”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-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 drawn
   cubic—none0/10

   All MCP-related evidence describes cubic acting as an MCP *server* that other coding agents/clients connect to (cubic-docs-15, cubic-docs-3, cubic-probe-3) — the reverse of this story, which asks whether a user can plug external MCP servers into cubic so it can consume their tools. No evidence shows cubic itself connecting to or invoking external MCP servers/tools.

   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “You can now ask your coding agent to check your cubic subscription, manage team seats and roles, and purchase more seats without leaving you…”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”

   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 userConnect an agent via an official MCP server

   weight 3 · round drawn
   cubic✓fullprobed8/10

   cubic documents an official MCP server that lets a coding agent read review findings, codebase context, request PR reviews, triage issues, and even manage subscription/seats without leaving the MCP client, confirmed by a dedicated docs page (probe) and quickstart references. Missing for 10: independent/hands-on community confirmation that the MCP server works as described (all evidence is vendor docs).

   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “You can now ask your coding agent to check your cubic subscription, manage team seats and roles, and purchase more seats without leaving you…”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”

   proof ↗⚑ flag

   Conductor✓fullprobed8/10

   Conductor documents a hosted MCP server that lets ChatGPT, Claude, Codex, and other MCP clients manage cloud workspaces, corroborated by a dedicated probe hit confirming the docs page exists. Missing for 10: independent/hands-on community confirmation of actually connecting an external agent via this MCP server (all community evidence discusses other features, not MCP usage).

   • [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

5. ai-native userUse an official CLI

   weight 2 · round to cubic
   cubic✓fullprobed8/10

   cubic ships an official CLI (`cubic review`) that reviews local/uncommitted changes and generates fix prompts for coding agents, documented explicitly and confirmed by a docs probe; it also integrates with agent workflows via MCP. Missing for 10: independent hands-on verification of the CLI itself (community evidence covers other product aspects, not CLI usage) and broader CLI command documentation beyond the single review command.

   • [claimed-docs] “Run a review before you push to catch issues while you're working.... review your uncommitted changes: `cubic review`”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [claimed-docs] “Connect your existing **ChatGPT Plus/Pro** or **Claude Code** subscription to use its models for local reviews.”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   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

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

   weight 3 · round to Conductor
   cubic~partialprobed6/10

   cubic documents an MCP server (cubic-docs-15, cubic-probe-3) that lets an AI agent request PR reviews, read findings, and triage issues, plus an Analytics API (cubic-docs-20) for PR-level data and a CLI (cubic-probe-4) for local reviews — all documented, agent-drivable surfaces. However, probes for a formal public API spec (openapi/swagger) all returned 404 (cubic-probe-2), so there's no evidence of a comprehensive documented public REST/GraphQL API beyond these narrower interfaces. Missing for 10: a full public API reference/spec, broader programmatic control beyond analytics/MCP/CLI, and independent confirmation of API usage.

   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”

   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

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

   weight 2 · round to Conductor
   cubic—none0/10

   Cubic documents role-based access control for team subscription/settings (cubic-docs-47) and exposes an MCP server, Analytics API, and CLI that agents can connect to, but there is no evidence of issuing scoped or least-privilege API credentials/tokens specifically for an agent's use — no API key scoping, OAuth scope, or agent-specific credential mechanism is documented.

   • [claimed-docs] “cubic uses a role-based access control system to manage who can make changes to your team's subscription and settings.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”

   proof ↗⚑ 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

8. ai-native userBuild against official SDKs

   weight 2 · round to Conductor
   cubic—none0/10

   cubic documents an MCP server, CLI, and an Analytics API, but there is no evidence of official language SDKs (e.g., Python/JS client libraries) for building against cubic programmatically; the OpenAPI probe also returned 404s across candidate paths, suggesting no formal SDK/API spec is published.

   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   proof ↗⚑ 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

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   cubic—none0/10

   No evidence of any webhook subscription mechanism; cubic exposes an MCP server, CLI, and Analytics API but nothing describing event-driven webhooks for subscribing to updates. missing for 10: any documentation of webhook endpoints, event types, or subscription setup.

   ⚑ 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 cubic
   cubic~partialcommunity6/10

   Cubic generates AI-driven insights from a user's own code/PR data via automated reviews, Ultrareview, AI-powered codebase scans, an AI wiki that indexes the codebase, and an analytics dashboard summarizing AI coding/review impact (cubic-docs-4,13,18,20,21,22). However, community hands-on feedback is mixed, with several users noting a large share of AI-generated comments are irrelevant or low-value (cubic-comm-3,9), tempering claims of consistently useful insights. Missing for 10: independent benchmarking of insight accuracy, and confirmation that analytics/wiki insights are broadly praised rather than just described in docs.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “Ultrareview runs a longer review using cubic's most capable review models, which is useful for risky migrations, security-sensitive changes,…”
   • [claimed-docs] “The analytics dashboard shows how your team ships code across three lenses: AI coding usage, AI review impact, and delivery speed.”
   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “cubic's AI wiki automatically indexes your codebase and produces searchable wikis, complete with links to source code, architecture diagrams…”
   • [community] “I've tried something similar in the past. The concept is cool, but so far the solutions I've seen are not so useful in terms of comments qua…”
   • [community] “what I saw using 5-6 tools like this: PR description is never useful, they barely summarize file changes; 90% of comments are wrong or irrel…”

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

   cubic ships several autonomous background automations: it auto-starts PR reviews on install (cubic-docs-4, cubic-docs-41), can auto-approve clean PRs under policy (cubic-docs-12, cubic-docs-35), runs codebase scans deploying many AI agents (cubic-docs-21), keeps an AI wiki current via rolling PRs (cubic-docs-23), does cross-repo checks (cubic-docs-37), and auto-purchases flex capacity to keep reviews running (cubic-docs-24) — all without manual triggering. Missing for 10: evidence of user-defined scheduled/cron-style custom automations beyond PR-triggered events, and independent hands-on confirmation that these autonomous flows run reliably unattended.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “cubic automatically starts reviewing new pull requests in your selected repositories.”
   • [claimed-docs] “cubic can approve clean pull requests automatically when your repository policy allows it. Start in shadow mode to see which PRs cubic would…”
   • [claimed-docs] “Auto-approval lets you skip human review for pull requests that cubic determines are low risk and issue-free.”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “cubic exports the wiki as markdown files into a directory in your repo (default `.cubic/wiki`) and keeps them current through a rolling pull…”
   • [claimed-docs] “Cross-repo reviews help cubic catch changes that need a matching update in another repository.”
   • [claimed-docs] “You set a monthly spend limit, and cubic buys extra reviewed-line capacity only when a review would otherwise be paused.”

   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 Conductor
   cubic✓fullclaimed7/10

   Cubic ships a built-in AI chat/assistant experience where users can delegate tasks — asking chat to 'tour this PR', adding code to AI chat for contextual Q&A, requesting one-click fixes ('Fix with cubic') that get generated and pushed automatically, and interacting via PR comments to trigger reviews or fixes. This is a genuine in-product assistant, not just an external agent integration. Missing for 10: independent/hands-on validation specifically of the chat-delegation UX (community evidence only covers review-comment quality, not the assistant/chat delegation flow), and no detail on task-completion reliability or scope limits of delegated tasks.

   • [claimed-docs] “Click **Fix with cubic** on a review comment... cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “Ask chat to "tour this PR" for a step-by-step review of the changes and what to check.”
   • [claimed-docs] “Select code and choose **Add to AI chat** to ask about it with the diff and codebase as context.”
   • [claimed-docs] “Interact with cubic in PR comments to ask questions, trigger reviews, and fix issues.”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “Ask follow-up questions about code changes without leaving the PR”
   • [claimed-docs] “The chat sidebar helps you quickly understand and navigate your pull requests (PRs) with intelligent, context-aware assistance directly with…”

   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 to Conductor
   cubic✓fullclaimed7/10

   cubic supports natural-language interaction via PR comments and chat: users can type commands like '@cubic-dev-ai review this PR', ask chat to 'tour this PR', reply to comments for clarification, request fixes, and connect an MCP server so a coding agent can trigger reviews and manage settings conversationally. Missing for 10: independent/hands-on evidence validating the quality and reliability of these NL interactions, and no evidence of broader free-form command coverage beyond the documented set of trigger phrases.

   • [claimed-docs] “To review a PR that was opened _before_ you installed the app, comment: `@cubic-dev-ai review this PR`.”
   • [claimed-docs] “Reply to a review comment to ask for clarification”
   • [claimed-docs] “Ask chat to "tour this PR" for a step-by-step review of the changes and what to check.”
   • [claimed-docs] “Interact with cubic in PR comments to ask questions, trigger reviews, and fix issues.”
   • [claimed-docs] “Post this comment on GitHub to start a review: text theme={null} @cubic-dev-ai review this PR ”
   • [claimed-docs] “Ask follow-up questions about code changes without leaving the PR”
   • [claimed-docs] “The chat sidebar helps you quickly understand and navigate your pull requests (PRs) with intelligent, context-aware assistance directly with…”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “You can now ask your coding agent to check your cubic subscription, manage team seats and roles, and purchase more seats without leaving you…”

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

   cubic documents an Analytics API but the evidence pack shows explicit probe failures for OpenAPI/swagger specs (404s) and no mention of an interactive API reference or runnable examples anywhere in the docs.

   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”

   proof ↗⚑ 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
   cubic—none0/10

   The probe explicitly checked common OpenAPI spec locations and all returned 404, and there is no other evidence of a downloadable machine-readable API spec for cubic's Analytics API or other endpoints; only an llms.txt is present, which is not an OpenAPI/API spec equivalent.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.cubic.dev/llms.txt # cubic documentation > cubic reviews code on GitHub and in local coding workfl…”
   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”

   proof ↗⚑ 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
   cubic—none0/10

   There is an Analytics API mentioned (cubic-docs-20) but no evidence of API versioning scheme or a documented deprecation policy anywhere in the docs; the OpenAPI probe even returned 404s for spec endpoints. missing for 10: versioning scheme documentation, deprecation policy, changelog/migration guides for API changes, any mention of API stability guarantees.

   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”

   proof ↗⚑ 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
   cubic~partialclaimed6/10

   cubic supports some bulk-like operations — codebase scans that 'deploy thousands of AI agents to find bugs across your repository' (cubic-docs-21), cross-repo reviews that check for related changes across multiple repos (cubic-docs-37/46), and analytics/CSV exports of PR-level data across a team (cubic-docs-19, cubic-docs-20) — but these are review/scan/export operations, not a general-purpose bulk-action capability (e.g., batch-fixing or batch-approving many PRs/items at once) with independent confirmation of scale. Missing for 10: explicit documentation of a bulk-action command/API for acting on many PRs, issues, or files simultaneously, and independent/hands-on evidence corroborating the 'thousands of agents' claim at scale.

   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “Cross-repo reviews help cubic catch changes that need a matching update in another repository.”
   • [claimed-docs] “Cross-repo reviews help cubic catch changes that need a matching update in another repository. Link related repositories so reviews can chec…”
   • [claimed-docs] “You can export team member data as CSV from both [AI coding](/analytics/ai-coding#csv-export) and [De”
   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”

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

   cubic supports several rule-based automated actions triggered by events within its code-review domain: auto-review on new PR (cubic-docs-4/41), auto-approval of clean PRs per repository policy (cubic-docs-12/35), auto thread resolution when an issue is fixed (cubic-docs-27), custom agents enforcing org rules across PRs (cubic-docs-34), and a spend-limit trigger that auto-purchases extra capacity (cubic-docs-24/48), all configurable via cubic.yaml (cubic-docs-16/36). These are genuine user-defined rule→action automations, but they are scoped to the code-review/PR lifecycle rather than a general-purpose event/rule engine for arbitrary triggers and actions. Missing for 10: a generic rules/automation builder spanning non-review events, explicit UI for defining custom trigger conditions beyond built-in policies, and independent confirmation these automations behave reliably at scale.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “cubic can approve clean pull requests automatically when your repository policy allows it. Start in shadow mode to see which PRs cubic would…”
   • [claimed-docs] “Enable automatic thread resolution to close findings when the issue is fixed”
   • [claimed-docs] “Custom agents are review rules that enforce your organization's specific best practices across pull requests.”
   • [claimed-docs] “You set a monthly spend limit, and cubic buys extra reviewed-line capacity only when a review would otherwise be paused.”
   • [claimed-docs] “Flex capacity keeps GitHub PR AI reviews running after your workspace uses its included reviewed-line capacity. You set a monthly spend limi…”
   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [claimed-docs] “cubic.yaml lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, an…”
   • [claimed-docs] “cubic automatically starts reviewing new pull requests in your selected repositories.”
   • [claimed-docs] “Auto-approval lets you skip human review for pull requests that cubic determines are low risk and issue-free.”

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

   cubic is a code review/PR automation tool triggered by PR events, webhooks, or manual commands (e.g., @cubic-dev-ai review, cubic review CLI), but no evidence describes scheduling recurring jobs or workflows on a time-based cadence (cron-like automation). Codebase scans and wiki updates appear event/PR-triggered, not user-schedulable recurring jobs.

   ⚑ 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
   cubic~partialclaimed4/10

   cubic.yaml (the config defining review behavior and custom agents) lives in the repo root, so it inherits git's native versioning and can be reviewed like any code change (cubic-docs-16, cubic-docs-11), but there is no dedicated changelog, rollback UI, or history feature specifically for cubic's automations/config themselves. Missing for 10: explicit rollback/version-history feature for automation configs, evidence of reviewing changes to cubic.yaml itself, dedicated UI for managing automation versions.

   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [claimed-docs] “**Custom agents**: Enforce your team’s coding standards”
   • [claimed-docs] “Create a repository named `cubic-config` in your organization and add a `cubic.yaml` file to the root directory. cubic automatically applies…”

   proof ↗⚑ 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 to Conductor
   cubic—none0/10

   cubic is an AI code-review platform: it reviews PRs, fixes flagged issues, generates PR descriptions, and can auto-approve clean PRs, but there is no evidence it autonomously builds a feature from scratch, runs tests, and produces a demo for review — it only acts on existing diffs/PRs authored by humans or other coding agents.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “Click **Fix with cubic** on a review comment... cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “By default, cubic pushes commits directly to your PR branch.”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “cubic helps your team spend less time writing PR descriptions automatically by generating clear, concise summaries.”

   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

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

   cubic is positioned as an AI code-review, codebase-scan, and wiki-generation tool, not a platform for users to launch autonomous agent fleets to work on arbitrary tasks for hours/days. 'Codebase scans deploy thousands of AI agents' (cubic-docs-21) is an internal review mechanism, not a user-directed fleet of autonomous agents working independently over long time horizons, and no evidence describes user-initiated multi-agent parallel task execution.

   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “**Custom agents**: Enforce your team’s coding standards”

   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

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

   cubic ships trigger-based automation — it auto-reviews every new PR, reacts to force-pushes, can auto-fix flagged issues, auto-approve clean PRs, and runs codebase-wide scans with 'thousands of AI agents' plus a self-updating wiki via rolling PRs — which covers autonomous, trigger-driven maintenance of software. However, there is no evidence of user-defined schedules (cron-like) or general-purpose 'always-on agent' configuration beyond PR/code-review events. Missing for 10: explicit schedule/cron-based agent triggers, evidence of autonomous fixes/maintenance outside the PR-review workflow, and independent confirmation these agents run continuously without human PR-based triggers.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “cubic can approve clean pull requests automatically when your repository policy allows it. Start in shadow mode to see which PRs cubic would…”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “cubic exports the wiki as markdown files into a directory in your repo (default `.cubic/wiki`) and keeps them current through a rolling pull…”
   • [claimed-docs] “Auto-approval lets you skip human review for pull requests that cubic determines are low risk and issue-free.”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “cubic now reviews the new changes after a force-push when it can safely compare them with a previously reviewed version.”

   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 cubic
   cubic~partialcommunity6/10

   cubic supports natural-language interaction for understanding and troubleshooting issues it finds in code review — e.g., replying to review comments for clarification, asking chat to 'tour this PR', adding code to AI chat with diff/codebase context, and its MCP server lets agents 'read review findings... and triage PR or codebase scan issues.' However, this is scoped to PR-review/bug-flagging conversations rather than general-purpose debugging of runtime errors or arbitrary issues outside the review flow. Missing for 10: evidence of open-ended debugging (e.g., stack trace analysis, runtime error investigation) beyond PR/code-review context, and independent hands-on confirmation that these NL Q&A features actually resolve real bugs (community comments dispute overall comment quality/bug-catching rate).

   • [claimed-docs] “Reply to a review comment to ask for clarification”
   • [claimed-docs] “Ask chat to "tour this PR" for a step-by-step review of the changes and what to check.”
   • [claimed-docs] “Select code and choose **Add to AI chat** to ask about it with the diff and codebase as context.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [claimed-docs] “Ask follow-up questions about code changes without leaving the PR”
   • [community] “what I saw using 5-6 tools like this: PR description is never useful, they barely summarize file changes; 90% of comments are wrong or irrel…”

   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. developerDescribe a feature or bug in plain language and have the agent implement or fix it across multiple files

   weight 3 · round to Conductor
   cubic~partialclaimed3/10

   Cubic is primarily a code-review platform that finds issues and can push targeted one-click fixes to specific flagged problems (docs-7, docs-44), and its CLI generates a fix prompt for external coding agents (docs-31) rather than implementing features itself. It does not document taking a plain-language feature/bug description and independently implementing changes across multiple files; that work is explicitly handed off to a separate 'coding agent' (docs-15, docs-30). Missing for 10: evidence of accepting an open-ended natural-language feature/bug description (not just a flagged review comment) and autonomously implementing multi-file changes, plus any hands-on validation of such end-to-end generation.

   • [claimed-docs] “Click **Fix with cubic** on a review comment... cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “By default, cubic pushes commits directly to your PR branch.”

   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 Conductor
   cubic~partialclaimed3/10

   cubic can automatically fix issues it flags in review (e.g., 'Fix with cubic' pushes a fix commit, docs-7/44) which could cover some lint-style issues, but there is no evidence it writes tests, resolves merge conflicts, or updates dependencies — cubic is positioned as a review/fix-on-comment tool, not a general-purpose coding agent for these tasks. missing for 10: test generation, merge-conflict resolution, dependency updates, and any evidence beyond review-triggered lint/bug fixes.

   • [claimed-docs] “Click **Fix with cubic** on a review comment... cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [claimed-docs] “By default, cubic pushes commits directly to your PR branch.”

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

   cubic's AI wiki auto-indexes the codebase into a searchable wiki with architecture diagrams and source-code links, and its MCP server/chat features let developers query the codebase and diffs for context (cubic-docs-22, cubic-docs-23, cubic-docs-15, cubic-docs-10), which directly supports understanding how a codebase fits together before making changes. Codebase scans (cubic-docs-21) add bug/vuln discovery but aren't about architectural navigation. Missing for 10: independent/hands-on validation that the wiki or chat actually helps developers locate where to start changes, and community evidence is silent on this specific capability (only comments on PR review quality exist).

   • [claimed-docs] “cubic's AI wiki automatically indexes your codebase and produces searchable wikis, complete with links to source code, architecture diagrams…”
   • [claimed-docs] “cubic exports the wiki as markdown files into a directory in your repo (default `.cubic/wiki`) and keeps them current through a rolling pull…”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “Select code and choose **Add to AI chat** to ask about it with the diff and codebase as context.”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”

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

   cubic's AI wiki automatically indexes the entire codebase and produces searchable wikis with architecture diagrams and source links, and codebase scans deploy AI agents across the whole repo — both let a developer get a full-codebase map/explanation without hand-picking context files. However, this is documented only in first-party docs with no independent hands-on validation of how well it 'explains' an unfamiliar codebase, and community commentary focuses on PR-review quality rather than the wiki/codebase-scan features. Missing for 10: independent/hands-on verification of the AI wiki's accuracy and usefulness, and community evidence specifically evaluating whole-codebase explanation quality.

   • [claimed-docs] “cubic's AI wiki automatically indexes your codebase and produces searchable wikis, complete with links to source code, architecture diagrams…”
   • [claimed-docs] “cubic exports the wiki as markdown files into a directory in your repo (default `.cubic/wiki`) and keeps them current through a rolling pull…”
   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “Select code and choose **Add to AI chat** to ask about it with the diff and codebase as context.”

   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 to cubic
   cubic~partialclaimed3/10

   Cubic maintains some persistent state — it compares force-pushed changes against previously reviewed versions and its AI wiki auto-indexes and keeps codebase docs current — but there's no documented feature describing agent 'memory' that is built and recalled across chat/review sessions in the way the story implies. missing for 10: explicit session-memory mechanism, evidence of recall in later interactions, independent confirmation of persistent context use.

   • [claimed-docs] “cubic now reviews the new changes after a force-push when it can safely compare them with a previously reviewed version.”
   • [claimed-docs] “cubic's AI wiki automatically indexes your codebase and produces searchable wikis, complete with links to source code, architecture diagrams…”
   • [claimed-docs] “cubic exports the wiki as markdown files into a directory in your repo (default `.cubic/wiki`) and keeps them current through a rolling pull…”

   proof ↗⚑ 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 to cubic
   cubic~partialclaimed4/10

   Cubic's 'cross-repo reviews' feature lets teams link related repositories so a review can check shared APIs, schemas, or docs across them, which is the closest analogue to including multiple project directories for broader context — but this is scoped narrowly to PR review consistency checks, not a general chat/agent session that loads multiple directories for open-ended Q&A. Missing for 10: evidence of a chat/agent session (e.g., MCP or CLI) that lets a developer add multiple arbitrary project directories as context, and any hands-on confirmation of cross-repo context quality.

   • [claimed-docs] “Cross-repo reviews help cubic catch changes that need a matching update in another repository.”
   • [claimed-docs] “Cross-repo reviews help cubic catch changes that need a matching update in another repository. Link related repositories so reviews can chec…”
   • [claimed-docs] “Select code and choose **Add to AI chat** to ask about it with the diff and codebase as context.”

   proof ↗⚑ 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 cubic
   cubic~partialclaimed6/10

   cubic supports a `cubic.yaml` config file at the repo root (or a shared `cubic-config` repo) that acts as 'the source of truth for AI review behavior, ignore patterns, PR descriptions, and custom agents,' and 'Custom agents' are documented as a way to 'enforce your team's coding standards.' This is a project-level instructions/config mechanism the agent follows, though it's framed around PR review behavior rather than a general-purpose coding-standards instructions file for all agent interactions. Missing for 10: explicit documentation of a plain-text/markdown instructions file (like AGENTS.md-style) covering broader coding conventions beyond review/ignore rules, and independent confirmation that custom agents reliably enforce standards in practice.

   • [claimed-docs] “**Custom agents**: Enforce your team’s coding standards”
   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [claimed-docs] “Create a repository named `cubic-config` in your organization and add a `cubic.yaml` file to the root directory. cubic automatically applies…”

   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 to Conductor
   cubic~partialclaimed4/10

   cubic is fundamentally an AI code-review/PR platform: it can flag bugs during review (codebase scans, PR review), generate and push fixes ('Fix with cubic'), and auto-resolve threads when issues are fixed, which covers some root-cause flagging and fix verification. However there is no evidence of actual issue reproduction (running the app/tests to trigger a bug) or root-cause debugging via execution—cubic's analysis is static/AI-review based, not a runtime debugger. Missing for 10: reproduction of bugs via execution/testing, dynamic root-cause tracing, and independent verification of fixes beyond thread auto-resolution.

   • [claimed-docs] “Codebase scans deploy thousands of AI agents to find bugs and vulnerabilities across your repository.”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “Enable automatic thread resolution to close findings when the issue is fixed”
   • [claimed-docs] “Click **Fix with cubic** on a review comment... cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “Ask chat to "tour this PR" for a step-by-step review of the changes and what to check.”

   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 cubic
   cubic~partialclaimed4/10

   cubic supports 'custom agents' configured via cubic.yaml to enforce coding standards, which is a limited form of custom skill/persona equipping for the review agent, but this is scoped narrowly to code-review behavior rather than general-purpose specialized task skills. Missing for 10: documentation on creating arbitrary custom skills/tools beyond coding-standard enforcement, examples of diverse specialized tasks, and independent validation of the custom agents feature.

   • [claimed-docs] “**Custom agents**: Enforce your team’s coding standards”
   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”

   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 Conductor
   cubic~partialprobed6/10

   cubic documents concrete integrations with third-party agent apps - connecting ChatGPT Plus or Claude Code subscriptions for local reviews, exposing an MCP server so coding agents can pull review findings and request PRs, pushing fixes via coding agents, and Linear or Jira issue-analysis integration - showing real ecosystem hooks for partner-built agent tools. Missing for 10: a documented marketplace or catalog of certified partner agent apps, examples beyond the major AI vendors, and independent evidence confirming these integrations work smoothly in practice.

   • [claimed-docs] “Connect your existing **ChatGPT Plus/Pro** or **Claude Code** subscription to use its models for local reviews.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “By default, cubic pushes commits directly to your PR branch.”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “cubic can automatically analyze your pull requests to see if they meet the requirements from your linked Linear or Jira issues.”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”

   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 cubic
   cubic~partialclaimed5/10

   cubic's AI wiki automatically indexes a repo's codebase into a searchable, shared wiki (with architecture diagrams) that's exported into the repo and kept current via PRs, giving teams a common source of truth derived from code — but this is scoped to repos, not to ingesting a team's existing docs into one workspace. Missing for 10: explicit support for importing/aggregating external docs, cross-repo/team-wide workspace view (only per-repo wiki + cross-repo review linking), and any independent evidence the wiki is actually used as a 'workspace' by teams.

   • [claimed-docs] “cubic's AI wiki automatically indexes your codebase and produces searchable wikis, complete with links to source code, architecture diagrams…”
   • [claimed-docs] “cubic exports the wiki as markdown files into a directory in your repo (default `.cubic/wiki`) and keeps them current through a rolling pull…”
   • [claimed-docs] “Cross-repo reviews help cubic catch changes that need a matching update in another repository.”
   • [claimed-docs] “Cross-repo reviews help cubic catch changes that need a matching update in another repository. Link related repositories so reviews can chec…”

   proof ↗⚑ 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 drawn
   cubic—none0/10

   cubic's documented integrations are limited to GitHub, an MCP server for coding agents, and ChatGPT/Claude Code subscriptions for local reviews; there is no evidence of connectors to Jira, Slack, or Google Drive for extending context.

   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “Connect your existing **ChatGPT Plus/Pro** or **Claude Code** subscription to use its models for local reviews.”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”
   • [community] “As far as I can see, this doesn't directly integrate with github (we currently use coderabbit on github)? Is it on your timeline?”
   • [community] “Would be great to have support for GitLab also (have a project there that I would love to try this on and I can't switch it to 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 Conductor
   cubic~partialcommunity4/10

   cubic clearly supports triggering reviews and fixes from GitHub (PR comments like `@cubic-dev-ai review this PR`, 'Fix with cubic', auto-review on install) and links to Linear/Jira for issue-requirement checks, but there's no evidence of Slack integration and community comments explicitly note GitLab support is missing/requested, not confirmed. Missing for 10: documented Slack task-triggering, confirmed GitLab support, and independent corroboration that Linear integration goes beyond issue-analysis to actually kicking off agent tasks.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “To review a PR that was opened _before_ you installed the app, comment: `@cubic-dev-ai review this PR`.”
   • [claimed-docs] “cubic automatically starts reviewing new pull requests in your selected repositories.”
   • [claimed-docs] “Post this comment on GitHub to start a review: text theme={null} @cubic-dev-ai review this PR ”
   • [claimed-docs] “cubic can automatically analyze your pull requests to see if they meet the requirements from your linked Linear or Jira issues.”
   • [community] “Would be great to have support for GitLab also (have a project there that I would love to try this on and I can't switch it to GitHub)”
   • [community] “It looks like graphite.dev has pivoted into this space too, which is annoying since they still don't have gitlab support after several years…”

   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
   cubic~partialclaimed3/10

   cubic's reviews, chat, and fix actions happen inside GitHub PR comments and threads (docs-29, docs-45, docs-7), which are cloud-hosted and thus technically accessible from any device/browser, but cubic never documents an explicit cross-device 'resume task' or session-continuity feature for a developer's own work-in-progress task. Missing for 10: explicit session/task persistence across CLI, IDE, and browser, documented device-handoff workflow, and any first-party or community confirmation of resuming an in-progress task on a new device.

   • [claimed-docs] “Interact with cubic in PR comments to ask questions, trigger reviews, and fix issues.”
   • [claimed-docs] “Ask follow-up questions about code changes without leaving the PR”
   • [claimed-docs] “Click **Fix with cubic** on a review comment... cubic generates the fix and pushes it to your PR branch.”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”

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

   cubic's docs describe CLI review, MCP server for coding agents, and an 'Add to AI chat' feature for selecting code with diff context, but none of this is documented as a JetBrains IDE plugin or in-IDE interactive diff viewer — the 'ide/' docs paths refer to CLI and agent/MCP setup, not JetBrains integration specifically.

   • [claimed-docs] “Select code and choose **Add to AI chat** to ask about it with the diff and codebase as context.”
   • [claimed-docs] “Connect your existing **ChatGPT Plus/Pro** or **Claude Code** subscription to use its models for local reviews.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   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 to Conductor
   cubic~partialclaimed5/10

   cubic offers chat-based interaction (an 'Add to AI chat' feature with diff/codebase context, a chat sidebar for PR navigation, and an MCP server that lets coding agents in the IDE read review findings), but these are mostly scoped to reviewing PRs/code review rather than a general-purpose in-IDE chat assistant for arbitrary contextual coding help. Missing for 10: evidence of a native IDE chat panel for general coding questions (not tied to PR/diff review), and independent hands-on confirmation of in-IDE chat quality.

   • [claimed-docs] “Select code and choose **Add to AI chat** to ask about it with the diff and codebase as context.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “The chat sidebar helps you quickly understand and navigate your pull requests (PRs) with intelligent, context-aware assistance directly with…”
   • [claimed-docs] “Ask chat to "tour this PR" for a step-by-step review of the changes and what to check.”

   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

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round to Conductor
   cubic~partialprobed5/10

   cubic ships an official local CLI (`cubic review`) that runs from the terminal to review uncommitted changes before push, and can connect to Claude Code/ChatGPT subscriptions for local reviews, but this is a review agent rather than a general-purpose coding agent that writes/edits code interactively in the terminal. Missing for 10: evidence of an interactive terminal coding-agent loop (code generation/editing, multi-turn task execution) beyond review-only CLI use.

   • [claimed-docs] “Run a review before you push to catch issues while you're working.... review your uncommitted changes: `cubic review`”
   • [claimed-docs] “Connect your existing **ChatGPT Plus/Pro** or **Claude Code** subscription to use its models for local reviews.”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   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 to Conductor
   cubic~partialprobed5/10

   cubic ships a CLI (`cubic review`) that reviews local/uncommitted changes and automatically reviews PRs on GitHub without manual intervention, both of which suggest it can be woven into automated workflows (docs-4, docs-8, docs-31, docs-41). However, there is no explicit documentation of a non-interactive/headless mode, CI pipeline integration, exit codes, or scripting flags for the CLI. missing for 10: explicit CI/script integration docs, non-interactive mode flags, exit-code/output-format guarantees for automation, independent evidence of scripted use.

   • [claimed-docs] “Run a review before you push to catch issues while you're working.... review your uncommitted changes: `cubic review`”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “cubic automatically starts reviewing new pull requests in your selected repositories.”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   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
   cubic~partialprobed4/10

   cubic exposes some functionality outside the UI — an Analytics API for PR-level data (cubic-docs-20), an MCP server for reading review findings, requesting reviews, and even managing subscriptions/seats (cubic-docs-3, cubic-docs-15), and a CLI for local reviews (cubic-docs-8, cubic-probe-4) — but there is no general-purpose public API (openapi probes 404, cubic-probe-2) covering the full UI surface (codebase scans, AI wiki, cubic.yaml config, analytics dashboard CSV exports, custom agents, auto-approve settings). Missing for 10: a comprehensive REST/GraphQL API or OpenAPI spec covering all UI features, evidence of API parity for wiki/codebase-scan/config management, and independent confirmation that MCP+CLI+Analytics API together replicate full UI functionality.

   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”
   • [claimed-docs] “You can now ask your coding agent to check your cubic subscription, manage team seats and roles, and purchase more seats without leaving you…”
   • [claimed-docs] “Run a review before you push to catch issues while you're working.... review your uncommitted changes: `cubic review`”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”
   • [probe] “official MCP server documented at https://docs.cubic.dev/ide/mcp-server”
   • [probe] “official CLI documented at https://docs.cubic.dev/ide/cli-review”

   proof ↗⚑ 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 to cubic
   cubic~partialclaimed4/10

   cubic offers some data portability: CSV export of team analytics (cubic-docs-19), an Analytics API for PR-level data (cubic-docs-20), and AI wiki content exported as markdown files into the repo (cubic-docs-23). However, there's no evidence of comprehensive export covering all review history, comments, configs, or account data in open formats, nor any documented account deletion/migration path for 'leaving' the platform. Missing for 10: full account/data export (reviews, comments, configs), explicit data-portability policy, independent confirmation of export completeness.

   • [claimed-docs] “You can export team member data as CSV from both [AI coding](/analytics/ai-coding#csv-export) and [De”
   • [claimed-docs] “The Analytics API gives you PR-level data on how many issues were flagged, how many were fixed, how much AI code was authored, etc.”
   • [claimed-docs] “cubic exports the wiki as markdown files into a directory in your repo (default `.cubic/wiki`) and keeps them current through a rolling pull…”

   proof ↗⚑ 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
   cubic—none0/10

   No evidence in the pack indicates cubic's source code is open or available under any open license; it appears to be a closed, commercial SaaS/CLI product with only documentation exposed publicly. Missing for 10: any open-source repository, license file, or public source code reference.

   ⚑ 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

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   cubic—none0/10

   cubic is presented as a hosted SaaS code review platform (GitHub app, cloud dashboard, analytics, flex capacity billing) with no documentation of a self-hostable core, on-prem deployment, or open-source release. Absence of any self-hosting evidence for an applicable axis (a code review tool could plausibly be self-hosted) means this is 'none'.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “You set a monthly spend limit, and cubic buys extra reviewed-line capacity only when a review would otherwise be paused.”
   • [claimed-docs] “Flex capacity keeps GitHub PR AI reviews running after your workspace uses its included reviewed-line capacity. You set a monthly spend limi…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”

   proof ↗⚑ flag

   Conductor—none0/10

   Conductor is a proprietary Mac app with a hosted cloud service and API/MCP server; there is no evidence of a self-hostable core product—no open-source repo, on-prem deployment option, or self-hosting docs are mentioned. Community even contrasts it unfavorably with 'Crystal,' which is explicitly noted as open source unlike Conductor, reinforcing that self-hosting isn't offered.

   • [community] “Crystal can do all of this and more, and unlike Conductor is open source.”
   • [claimed-docs] “Sandboxes spin up in seconds, and agents keep working after you close your laptop.”
   • [claimed-docs] “The Conductor API lets you manage cloud workspaces programmatically.”

   proof ↗⚑ flag

Authentication

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

   weight 2 · round to Conductor
   cubic—none0/10

   No evidence in the pack mentions API key authentication as an alternative to account login; cubic's docs describe GitHub app installation, roles/permissions, and subscription management but nothing about API-key-based auth for developers. The OpenAPI probe also returned 404s, suggesting no documented API surface with key auth.

   • [claimed-docs] “cubic uses a role-based access control system to manage who can make changes to your team's subscription and settings.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cubic.dev/openapi.json, https://docs.cubic.dev/swagger.json, https://docs.cubic.dev/api…”

   proof ↗⚑ 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
   cubic—none0/10

   The evidence pack shows role-based access control for team/subscription management (cubic-docs-47) but no mention of SSO, SAML, OAuth enterprise identity provider integration, or cloud IAM authentication anywhere in the docs or community items. missing for 10: SSO/SAML support, enterprise IdP integration (Okta/Azure AD/Google Workspace), cloud IAM authentication, any compliance certification tied to auth.

   • [claimed-docs] “cubic uses a role-based access control system to manage who can make changes to your team's subscription and settings.”

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

   cubic explicitly lets developers connect an existing ChatGPT Plus/Pro or Claude Code subscription to power local CLI reviews, which matches 'sign in with existing subscription to use the coding agent.' However, this only applies to local review via CLI, not the full agent/reviewer product, and there's no independent verification of this flow working in practice. Missing for 10: broader applicability beyond CLI reviews, and community/hands-on confirmation of the subscription linking process.

   • [claimed-docs] “Connect your existing **ChatGPT Plus/Pro** or **Claude Code** subscription to use its models for local reviews.”

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

   cubic is a code-review/PR platform with team subscriptions, seats, and flex-capacity billing; no evidence describes a personal-account sign-in path granting free-tier access without API key management—this pricing/auth model story is unaddressed in the pack.

   ⚑ 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
   cubic—none0/10

   Cubic's docs describe distinct manually-invoked review modes (standard review vs. Ultrareview) and let users connect their own ChatGPT/Claude subscriptions for local reviews, but there is no evidence the tool automatically selects the best model per task based on cost or complexity — mode selection is user-driven, not automatic.

   • [claimed-docs] “Ultrareview runs a longer review using cubic's most capable review models, which is useful for risky migrations, security-sensitive changes,…”
   • [claimed-docs] “Ultrareview is cubic's deepest review. It runs a longer, multi-pass analysis using cubic's most capable review models”
   • [claimed-docs] “Ultrareview is cubic's deepest review. It runs a longer, multi-pass analysis using cubic's most capable review models, and typically takes a…”
   • [claimed-docs] “Connect your existing **ChatGPT Plus/Pro** or **Claude Code** subscription to use its models for local reviews.”
   • [claimed-docs] “You set a monthly spend limit, and cubic buys extra reviewed-line capacity only when a review would otherwise be paused.”

   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 to Conductor
   cubic~partialclaimed5/10

   Cubic docs state you can "connect your existing ChatGPT Plus/Pro or Claude Code subscription to use its models for local reviews" via the CLI, showing some model-provider choice, but PR reviews and Ultrareview use cubic's own proprietary 'most capable review models' with no indication of choosing among alternative providers there. missing for 10: model choice for the core PR/Ultrareview review sessions (not just local CLI), a documented list of selectable providers, and independent confirmation of the feature working in practice.

   • [claimed-docs] “Connect your existing **ChatGPT Plus/Pro** or **Claude Code** subscription to use its models for local reviews.”
   • [claimed-docs] “Ultrareview runs a longer review using cubic's most capable review models, which is useful for risky migrations, security-sensitive changes,…”
   • [claimed-docs] “Ultrareview is cubic's deepest review. It runs a longer, multi-pass analysis using cubic's most capable review models”
   • [claimed-docs] “Ultrareview is cubic's deepest review. It runs a longer, multi-pass analysis using cubic's most capable review models, and typically takes a…”

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

   No evidence in the pack mentions data residency, region selection, or storage location controls for cubic; the docs focus entirely on code review, PR workflows, and analytics with no privacy/data-residency configuration options mentioned.

   ⚑ 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
   cubic—none0/10

   No evidence in the pack addresses data usage for AI model training, opt-out policies, or data privacy commitments — cubic's docs focus entirely on code review features with no mention of training data controls.

   ⚑ 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
   cubic—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy settings for AI-native users; docs cover review features, analytics, wiki, and pricing but nothing on retention/deletion of data. Missing for 10: any documentation on data retention periods, deletion requests, or privacy 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
   cubic—none0/10

   No evidence pack item addresses telemetry opt-out or usage-tracking controls; cubic's docs cover review features, analytics dashboards, and RBAC but never mention a privacy/telemetry toggle. missing for 10: any mention of telemetry collection, opt-out settings, or privacy controls.

   ⚑ 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
   cubic—none0/10

   No evidence in the pack addresses data-privacy or AI training opt-out policies for code/prompts; nothing in the docs, changelog, or community discussion mentions this capability. missing for 10: any documentation of data usage policy, training opt-out settings, or privacy 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
   cubic~partialclaimed4/10

   cubic can push fix commits directly to an existing PR branch and auto-generate PR descriptions/summaries (cubic-docs-30, cubic-docs-44, cubic-docs-26, cubic-docs-49), but its own docs show the developer still runs the initial git workflow (checkout -b, commit, push) to create the branch and open the PR (cubic-docs-51) — cubic is a review/fix layer, not an agent that autonomously stages changes, writes original commit messages, creates branches, or opens PRs from scratch. missing for 10: evidence of cubic independently creating a new branch, staging changes, and opening a brand-new pull request without a human first running git/opening the PR.

   • [claimed-docs] “By default, cubic pushes commits directly to your PR branch.”
   • [claimed-docs] “cubic can automatically fix issues identified during code review. Request a targeted fix with one click.”
   • [claimed-docs] “Generates PR descriptions based on code changes”
   • [claimed-docs] “cubic helps your team spend less time writing PR descriptions automatically by generating clear, concise summaries.”
   • [claimed-docs] “you can keep using normal Git commands exactly as before (e.g., `git checkout -b my-feature`, `git commit -m "message"`, `git push`). Using …”
   • [claimed-docs] “Click **Fix with cubic** on a review comment... cubic generates the fix and pushes it to your PR branch.”

   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 cubic
   cubic~partialcommunity6/10

   cubic's docs strongly document automatic PR reviews with contextual comments, fixes, follow-up chat, and PR descriptions (cubic-docs-4, cubic-docs-25, cubic-docs-29, cubic-docs-45, cubic-docs-26). However, community hands-on feedback in the same threads is mixed: some praise the contextual quality (cubic-comm-1, cubic-comm-7) while others report low signal quality and skepticism about the marketing stats (cubic-comm-9, cubic-comm-10), so the real-world contextual value is not uniformly corroborated. Missing for 10: independent third-party benchmark of comment relevance, and consistent community consensus on comment quality rather than mixed reports.

   • [claimed-docs] “Once installed, cubic automatically reviews new pull requests.”
   • [claimed-docs] “Comments on bugs and improvements in pull requests”
   • [claimed-docs] “Interact with cubic in PR comments to ask questions, trigger reviews, and fix issues.”
   • [claimed-docs] “Ask follow-up questions about code changes without leaving the PR”
   • [claimed-docs] “Generates PR descriptions based on code changes”
   • [community] “This looks like a cool solve for this problem. Some of the other tools I tried didn't seem to contextualize the app, so the comments were su…”
   • [community] “I've been testing this for the last few months, and it is now much quieter than before, and even more useful.”
   • [community] “what I saw using 5-6 tools like this: PR description is never useful, they barely summarize file changes; 90% of comments are wrong or irrel…”
   • [community] “When I read '51% fewer false positives' followed immediately by 'Median comments per pull request cut by half' it makes me wonder how many t…”

   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 cubic
   cubic✓fullcommunity8/10

   cubic provides diff-focused PR review (hiding tests, force-push re-review), a CLI (`cubic review`) to check uncommitted changes before pushing, Ultrareview for deep multi-pass checks, and auto-fix/auto-approval gating before merge — directly matching 'inspect diffs and run checks before merging'. Community feedback corroborates real-world use but also raises concerns about comment relevance and false-positive rates, tempering confidence. Missing for 10: independent quantitative validation of bug-catch accuracy and resolution of noise/false-positive concerns raised by users.

   • [claimed-docs] “Run a review before you push to catch issues while you're working.... review your uncommitted changes: `cubic review`”
   • [claimed-docs] “Ask chat to "tour this PR" for a step-by-step review of the changes and what to check.”
   • [claimed-docs] “Ultrareview runs a longer review using cubic's most capable review models, which is useful for risky migrations, security-sensitive changes,…”
   • [claimed-docs] “Ultrareview is cubic's deepest review. It runs a longer, multi-pass analysis using cubic's most capable review models”
   • [claimed-docs] “The **cubic CLI** reviews local changes before you push. It finds bugs and generates a prompt that your coding agent can use to fix them.”
   • [claimed-docs] “cubic now reviews the new changes after a force-push when it can safely compare them with a previously reviewed version.”
   • [claimed-docs] “Focus on implementation changes by hiding test files from the PR diff and file tree.”
   • [claimed-docs] “Auto-approval lets you skip human review for pull requests that cubic determines are low risk and issue-free.”
   • [community] “I've been testing this for the last few months, and it is now much quieter than before, and even more useful.”
   • [community] “what I saw using 5-6 tools like this: PR description is never useful, they barely summarize file changes; 90% of comments are wrong or irrel…”

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

   Evidence shows cubic has RBAC for subscription/settings management (cubic-docs-47) and cubic.yaml config for review behavior (cubic-docs-16/36), but nothing documents an engineering-lead controlling which external tools, MCP servers, or integrations the cubic agent itself is permitted to access. Missing for 10: any admin-facing tool/integration allowlist or permission gate for the agent's external tool access.

   • [claimed-docs] “cubic uses a role-based access control system to manage who can make changes to your team's subscription and settings.”
   • [claimed-docs] “`cubic.yaml` lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, …”
   • [claimed-docs] “cubic.yaml lives in the root of your repository and becomes the source of truth for AI review behavior, ignore patterns, PR descriptions, an…”
   • [claimed-docs] “Connect cubic's MCP server to your coding agent to read review findings and codebase context, request PR reviews, and triage PR or codebase …”

   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

Security checks

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

   weight 1 · round drawn
   cubic—none0/10

   cubic's evidence covers PR review, bug/vulnerability detection, custom agents, analytics, and codebase scans, but there is no mention of license compliance checking or public-code/plagiarism matching references for AI-suggested code. Missing for 10: license detection features, public-code/match provenance references, any SCA or license-compliance tooling.

   ⚑ 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