Try itExperimental
See what an agent can do with Conductor before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://www.conductor.build/docs/api/mcp.md | head -8recorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Autonomy agents — stories about autonomy agents in this arenaAutonomy agentsevidence →
Stories about autonomy agents in this arena
Code generation — quality of generated code — correctness, style, fit to the codebaseCode generationevidence →
Quality of generated code — correctness, style, fit to the codebase
Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understandingevidence →
How deeply the tool maps your repo — cross-file context, architecture awareness, history
Ecosystem — integrations, plugins, and third-party ecosystem storiesEcosystemevidence →
Integrations, plugins, and third-party ecosystem stories
Ide terminal integration — meeting you in the IDE and terminal — extensions, inline flows, contextIde terminal integrationevidence →
Meeting you in the IDE and terminal — extensions, inline flows, context
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limitsevidence →
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safetyevidence →
Keeping generated changes safe — diffs, approvals, guardrails
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 0 free · 1 paid · 0 enterprise · 41 not stated in evidence
Follow the green: where the map greys out is where Conductor stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓7/10
unlocks → Webhooks · Machine-readable spec · Versioning policy · Official CLI · Full data export · View interactive diffs and share selected code as context from within my JetBrains IDE
Subscribe to events via webhooks
—0/10
Build against official SDKs
~5/10
Issue scoped/least-privilege API credentials for an agent
~4/10
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~6/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
✓8/10
unlocks → MCP client
Operate the product with natural-language commands
✓8/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
~4/10
Set up automations that run autonomously in the background
✓7/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Autonomy agents — stories about autonomy agents in this arenaAutonomy agents
Stories about autonomy agents in this arena
Background execution
Parallel agents
Set up always-on agents that run on schedules or triggers to maintain and fix my software autonomously
~6/10
Code generation — quality of generated code — correctness, style, fit to the codebaseCode generation
Quality of generated code — correctness, style, fit to the codebase
Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding
How deeply the tool maps your repo — cross-file context, architecture awareness, history
Ecosystem — integrations, plugins, and third-party ecosystem storiesEcosystem
Integrations, plugins, and third-party ecosystem stories
Ide terminal integration — meeting you in the IDE and terminal — extensions, inline flows, contextIde terminal integration
Meeting you in the IDE and terminal — extensions, inline flows, context
Start a task on one device and continue it later from another device or browser
~6/10
Ide integration
Session management
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safety
Keeping generated changes safe — diffs, approvals, guardrails
Sorted by importance (agentic first) (high → low) · 74/74 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Xcommunity | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Tprobed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Xcommunity | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 6/10 | Xcommunity | |
Have the agent stage changes, write commit messages, create branches, and open pull requests C Pr review | developer | Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safety | 3 | full | 8/10 | Xcommunity | |
Chat with the coding assistant directly inside my IDE for contextual help C Ide integration | developer | Ide terminal integration — meeting you in the IDE and terminal — extensions, inline flows, contextIde terminal integration | 3 | full | 7/10 | Xcommunity | |
Delegate longer-running coding tasks to run in the background in an isolated cloud environment C Background execution | developer | Autonomy agents — stories about autonomy agents in this arenaAutonomy agents | 3 | partialpaid | 7/10 | Xcommunity | |
Run a coding agent locally from my terminal C Terminal workflow | developer | Ide terminal integration — meeting you in the IDE and terminal — extensions, inline flows, contextIde terminal integration | 3 | partial | 7/10 | Tprobed | |
Turn a tracked issue into a complete pull request end-to-end C Feature implementation | developer | Code generation — quality of generated code — correctness, style, fit to the codebaseCode generation | 3 | full | 7/10 | Cclaimed | |
Describe a feature or bug in plain language and have the agent implement or fix it across multiple files C Feature implementation | developer | Code generation — quality of generated code — correctness, style, fit to the codebaseCode generation | 3 | partial | 6/10 | Xcommunity | |
Inspect diffs and run checks to catch problems before merging C Pr review | developer | Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safety | 3 | partial | 6/10 | Cclaimed | |
Reproduce issues, narrow down root causes, and verify fixes C Issue diagnosis | developer | Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding | 3 | partial | 6/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 5/10 | Cclaimed | |
Have the agent write tests, fix lint errors, resolve merge conflicts, and update dependencies for me C Maintenance automation | developer | Code generation — quality of generated code — correctness, style, fit to the codebaseCode generation | 3 | partial | 5/10 | Cclaimed | |
Add a project instructions file to set coding standards and conventions the agent follows C Context management | developer | Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding | 3 | partial | 4/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Get automatic code review with contextual feedback on every pull request C Pr review | developer | Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safety | 3 | none | 0/10 | ||
Have the agent map and explain an entire unfamiliar codebase without manually selecting context files C Codebase mapping | developer | Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | 0/10 | ||
Receive inline code completions and next-edit suggestions as I type C Code completion | developer | Code generation — quality of generated code — correctness, style, fit to the codebaseCode generation | 3 | n/a | 0/10 | ||
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Understand how a codebase fits together to find where to start making changes C Codebase mapping | developer | Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding | 3 | none | 0/10 | ||
Connect the agent to workflow tools like Jira, Slack, and Google Drive to extend its context C Tool integration | developer | Ecosystem — integrations, plugins, and third-party ecosystem storiesEcosystem | 3 | none | untested | none yet | |
Choose which underlying AI model powers my session from multiple providers C Model choice | developer | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | full | 8/10 | Xcommunity | |
Manage multiple agent-driven coding sessions from one unified workspace C Session management | engineering-lead | Ide terminal integration — meeting you in the IDE and terminal — extensions, inline flows, contextIde terminal integration | 2 | full | 8/10 | Xcommunity | |
Review diffs visually and run multiple sessions side by side in a desktop app C Session management | developer | Ide terminal integration — meeting you in the IDE and terminal — extensions, inline flows, contextIde terminal integration | 2 | full | 8/10 | Tprobed | |
Sign in with my existing product subscription plan to use the coding agent C Authentication | developer | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | full | 8/10 | Cclaimed | |
Authenticate with an API key instead of an account login G Authentication | developer | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | full | 7/10 | Cclaimed | |
Have a cloud agent build, test, and demo a feature end-to-end for my review C Background execution | ai-native user | Autonomy agents — stories about autonomy agents in this arenaAutonomy agents | 2 | full | 7/10 | Cclaimed | |
Launch fleets of autonomous agents that work in parallel on different tasks for hours or days C Parallel agents | ai-native user | Autonomy agents — stories about autonomy agents in this arenaAutonomy agents | 2 | full | 7/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 7/10 | Cclaimed | |
Configure a reproducible cloud environment with the dependencies and setup steps my repository needs C Background execution | developer | Autonomy agents — stories about autonomy agents in this arenaAutonomy agents | 2 | partial | 6/10 | Cclaimed | |
Run the agent non-interactively in scripts for workflow automation C Terminal workflow | developer | Ide terminal integration — meeting you in the IDE and terminal — extensions, inline flows, contextIde terminal integration | 2 | partial | 6/10 | Cclaimed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | full | 6/10 | Cclaimed | |
Set up always-on agents that run on schedules or triggers to maintain and fix my software autonomously C Scheduled automation | ai-native user | Autonomy agents — stories about autonomy agents in this arenaAutonomy agents | 2 | partial | 6/10 | Cclaimed | |
Start a task on one device and continue it later from another device or browser C Cross device continuity | developer | Ide terminal integration — meeting you in the IDE and terminal — extensions, inline flows, contextIde terminal integration | 2 | partial | 6/10 | Cclaimed | |
Control which external tools and integrations the agent is allowed to access C Safe execution | engineering-lead | Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safety | 2 | partial | 5/10 | Xcommunity | |
Debug issues and troubleshoot using natural-language queries C Debugging | developer | Code generation — quality of generated code — correctness, style, fit to the codebaseCode generation | 2 | partial | 5/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
Have the agent operate inside a sandbox when interacting with code, tools, and network resources C Safe execution | engineering-lead | Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safety | 2 | partial | 5/10 | Xcommunity | |
Kick off agent tasks directly from GitHub, GitLab, Linear, or Slack C Tool integration | developer | Ecosystem — integrations, plugins, and third-party ecosystem storiesEcosystem | 2 | partial | 5/10 | Cclaimed | |
Authenticate through an enterprise identity or cloud platform for compliance and scalability G Authentication | engineering-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Have the agent build and recall memory automatically across sessions C Context management | developer | Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding | 2 | none | 0/10 | ||
Include multiple project directories in a single session for broader context C Context management | developer | Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyCodebase understanding | 2 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
Generate a working app from a sketch, image, or PDF design C Multimodal generation | ai-native user | Code generation — quality of generated code — correctness, style, fit to the codebaseCode generation | 2 | n/a | untested | none yet | |
Get contextual explanations and automatic fixes for security vulnerabilities C Security checks | developer | Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safety | 2 | n/a | untested | none yet | |
Run several task attempts in parallel and compare results before choosing one C Parallel agents | developer | Autonomy agents — stories about autonomy agents in this arenaAutonomy agents | 1 | full | 8/10 | Tprobed | |
Integrate third-party partner-built agent apps into my workflows C Marketplace | engineering-lead | Ecosystem — integrations, plugins, and third-party ecosystem storiesEcosystem | 1 | partial | 7/10 | Xcommunity | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 6/10 | Cclaimed | |
Create a shared workspace from my docs and repos as a common source of truth for the team C Team knowledge | engineering-lead | Ecosystem — integrations, plugins, and third-party ecosystem storiesEcosystem | 1 | partial | 4/10 | Cclaimed | |
Equip the agent with custom skills to perform specialized tasks C Marketplace | developer | Ecosystem — integrations, plugins, and third-party ecosystem storiesEcosystem | 1 | none | 0/10 | ||
Let the tool automatically pick the best model for each task C Model choice | developer | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 1 | none | 0/10 | ||
Opt out of having my code and prompts used for AI model training C Data governance | engineering-lead | Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safety | 1 | none | 0/10 | ||
Sign in with a personal account to get free-tier access without managing API keys G Authentication | developer | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 1 | none | 0/10 | ||
View interactive diffs and share selected code as context from within my JetBrains IDE C Ide integration | developer | Ide terminal integration — meeting you in the IDE and terminal — extensions, inline flows, contextIde terminal integration | 1 | none | 0/10 | ||
Debug a live running web application directly from my coding assistant C Debugging | developer | Code generation — quality of generated code — correctness, style, fit to the codebaseCode generation | 1 | n/a | untested | none yet | |
See license and public-code matching references for AI-suggested code C Security checks | engineering-lead | Review safety — keeping generated changes safe — diffs, approvals, guardrailsReview safety | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 52 stories with headroom
What would move Conductor’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
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.
Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyUnderstand how a codebase fits together to find where to start making changes
nonemoves PA Scoreimpact 30
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.
Review safety — keeping generated changes safe — diffs, approvals, guardrailsGet automatic code review with contextual feedback on every pull request
nonemoves PA Scoreimpact 30
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.
Ecosystem — integrations, plugins, and third-party ecosystem storiesConnect the agent to workflow tools like Jira, Slack, and Google Drive to extend its context
nonemoves PA Scoreimpact 30
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.
Codebase understanding — how deeply the tool maps your repo — cross-file context, architecture awareness, historyHave the agent map and explain an entire unfamiliar codebase without manually selecting context files
nonemoves PA Scoreimpact 30
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.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
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.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
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.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
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.
Showing the top 8 of 52 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map6 surfaces · 44 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs38 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Build against official SDKs
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Version, review, and roll back my automations
- Have a cloud agent build, test, and demo a feature end-to-end for my review
- Delegate longer-running coding tasks to run in the background in an isolated cloud environment
- Configure a reproducible cloud environment with the dependencies and setup steps my repository needs
- Launch fleets of autonomous agents that work in parallel on different tasks for hours or days
- Run several task attempts in parallel and compare results before choosing one
- Set up always-on agents that run on schedules or triggers to maintain and fix my software autonomously
- Debug issues and troubleshoot using natural-language queries
- Turn a tracked issue into a complete pull request end-to-end
- Describe a feature or bug in plain language and have the agent implement or fix it across multiple files
- Have the agent write tests, fix lint errors, resolve merge conflicts, and update dependencies for me
- Add a project instructions file to set coding standards and conventions the agent follows
- Reproduce issues, narrow down root causes, and verify fixes
- Integrate third-party partner-built agent apps into my workflows
- Create a shared workspace from my docs and repos as a common source of truth for the team
- Kick off agent tasks directly from GitHub, GitLab, Linear, or Slack
- Start a task on one device and continue it later from another device or browser
- Chat with the coding assistant directly inside my IDE for contextual help
- Review diffs visually and run multiple sessions side by side in a desktop app
- Manage multiple agent-driven coding sessions from one unified workspace
- Run a coding agent locally from my terminal
- Run the agent non-interactively in scripts for workflow automation
- Do everything through the API that I can do in the UI
- Choose which underlying AI model powers my session from multiple providers
- Have the agent stage changes, write commit messages, create branches, and open pull requests
- Inspect diffs and run checks to catch problems before merging
- Have the agent operate inside a sandbox when interacting with code, tools, and network resources
Changelog docs18 stories
- Run the product headlessly / in CI for automation
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- Delegate longer-running coding tasks to run in the background in an isolated cloud environment
- Launch fleets of autonomous agents that work in parallel on different tasks for hours or days
- Set up always-on agents that run on schedules or triggers to maintain and fix my software autonomously
- Reproduce issues, narrow down root causes, and verify fixes
- Integrate third-party partner-built agent apps into my workflows
- Kick off agent tasks directly from GitHub, GitLab, Linear, or Slack
- Run the agent non-interactively in scripts for workflow automation
- Authenticate with an API key instead of an account login
- Sign in with my existing product subscription plan to use the coding agent
- Choose which underlying AI model powers my session from multiple providers
- Inspect diffs and run checks to catch problems before merging
- Control which external tools and integrations the agent is allowed to access
Hacker News15 stories
- Issue scoped/least-privilege API credentials for an agent
- Delegate tasks to a built-in AI assistant inside the product
- Test against a sandbox environment without touching production data
- Delegate longer-running coding tasks to run in the background in an isolated cloud environment
- Run several task attempts in parallel and compare results before choosing one
- Describe a feature or bug in plain language and have the agent implement or fix it across multiple files
- Integrate third-party partner-built agent apps into my workflows
- Chat with the coding assistant directly inside my IDE for contextual help
- Review diffs visually and run multiple sessions side by side in a desktop app
- Manage multiple agent-driven coding sessions from one unified workspace
- Run a coding agent locally from my terminal
- Choose which underlying AI model powers my session from multiple providers
- Have the agent stage changes, write commit messages, create branches, and open pull requests
- Control which external tools and integrations the agent is allowed to access
- Have the agent operate inside a sandbox when interacting with code, tools, and network resources
llms.txt4 stories
OpenAPI spec3 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://www.conductor.build/docs/api/mcp.md | head -8reproduced$ curl -s https://www.conductor.build/docs/api/mcp.md | head -8 --- title: "Conductor MCP server" url: "/docs/api/mcp" description: "Connect an MCP client to create and manage Conductor cloud workspaces" --- # Conductor MCP server
$curl -s https://www.conductor.build/llms.txt | head -4reproduced$ curl -s https://www.conductor.build/llms.txt | head -4 # Conductor > Conductor is a Mac app that lets you run many coding agents in parallel on your codebase.
$curl -si -X POST https://api.conductor.build/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -si -X POST https://api.conductor.build/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
HTTP/2 401
date: Mon, 14 Sep 2026 23:49:57 GMT
content-type: application/json; charset=utf-8
access-control-expose-headers: retry-after, X-Conductor-Request-Id
cf-cache-status: DYNAMIC
rndr-id: 17de285f-fcea-47a0
server: cloudflare
vary: Origin
vary: Accept-Encoding
www-authenticate: Bearer resource_metadata="https://api.conductor.build/.well-known/oauth-protected-resource/mcp", scope="mcp:tools"
x-conductor-request-id: 8f2ee26a724b5c3224c6f9739aca098e
x-render-origin-server: Render
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=XDf94wrYtSSR6y0doi3F36GQQSAIwzTvE6EoL0rOv%2FNoahsprtToXXYsI5lECg8pf6WcFNHDaqdyOVWzf0VH%2BE%2BRm0alo6%2BMxdxryshGLfoQW%2BjdmY7Hblx4g3j%2FpKjtAFA2ZigK"}]}
cf-ray: a3b34a895e850dac-SJC
alt-svc: h3=":443"; ma=86400
{"jsonrpc":"2.0","error":{"code":-32001,"message":"Unauthorized"},"id":null}
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
5 of 14 testable claims verified · 0 contradicted → integrity 36/100
20 distinct capability claims found in Conductor’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
5
Verified
9
Unverified
0
Contradicted
30
Undersold
Verified (8)
“Run multiple coding agents (Claude Code, Codex, Cursor, OpenCode) in parallel”
Choose which underlying AI model powers my session from multiple providersfullproof ↗
“Each task runs in its own isolated workspace with dedicated branch, files, terminal, diff, and review path”
Delegate longer-running coding tasks to run in the background in an isolated cloud environmentpartialproof ↗
“Save a loadout of favorite models and switch between them quickly, including keyboard shortcuts for model/effort/speed/order”
Choose which underlying AI model powers my session from multiple providersfullproof ↗
“View PR comments and failing check logs even while the cloud workspace is asleep”
Delegate longer-running coding tasks to run in the background in an isolated cloud environmentpartialproof ↗
“Manage cloud workspaces programmatically via the Conductor API”
Drive the product through a documented public APIfullproof ↗
“Hosted MCP server lets ChatGPT, Claude, Codex, and other MCP clients manage cloud workspaces”
“Agent can test repositories, update install/setup scripts, and run builds without confirming each step”
Have the agent operate inside a sandbox when interacting with code, tools, and network resourcespartialproof ↗
“Sandboxes spin up in seconds and agents keep working after you close your laptop”
Delegate longer-running coding tasks to run in the background in an isolated cloud environmentpartialproof ↗
Unverified (10)
“Run multiple coding agents (Claude Code, Codex, Cursor, OpenCode) in parallel”
Launch fleets of autonomous agents that work in parallel on different tasks for hours or daysfullproof ↗
“Run agents on a schedule or trigger them via a GitHub Action ('routines')”
“Run agents on a schedule or trigger them via a GitHub Action ('routines')”
Set up always-on agents that run on schedules or triggers to maintain and fix my software autonomouslypartialproof ↗
“Sign in with an existing Cursor subscription to use cloud workspaces”
Sign in with my existing product subscription plan to use the coding agentfullproof ↗
“Create a new workspace directly from a branch, pull request, GitHub issue, or Linear issue”
Kick off agent tasks directly from GitHub, GitLab, Linear, or Slackpartialproof ↗
“Create a new workspace directly from a branch, pull request, GitHub issue, or Linear issue”
Turn a tracked issue into a complete pull request end-to-endfullproof ↗
“Share a link that opens a workspace in Conductor for any org member”
Create a shared workspace from my docs and repos as a common source of truth for the teampartialproof ↗
“Agent can test repositories, update install/setup scripts, and run builds without confirming each step”
Have the agent write tests, fix lint errors, resolve merge conflicts, and update dependencies for mepartialproof ↗
“Bring your own subscriptions and API keys to power agents”
Authenticate with an API key instead of an account loginfullproof ↗
“Bring your own subscriptions and API keys to power agents”
Sign in with my existing product subscription plan to use the coding agentfullproof ↗
Undersold (30)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundfullproof ↗
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
Operate the product with natural-language commandsfullproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Have a cloud agent build, test, and demo a feature end-to-end for my reviewfullproof ↗
Configure a reproducible cloud environment with the dependencies and setup steps my repository needspartialproof ↗
Run several task attempts in parallel and compare results before choosing onefullproof ↗
Debug issues and troubleshoot using natural-language queriespartialproof ↗
Describe a feature or bug in plain language and have the agent implement or fix it across multiple filespartialproof ↗
Add a project instructions file to set coding standards and conventions the agent followspartialproof ↗
Reproduce issues, narrow down root causes, and verify fixespartialproof ↗
Integrate third-party partner-built agent apps into my workflowspartialproof ↗
Start a task on one device and continue it later from another device or browserpartialproof ↗
Chat with the coding assistant directly inside my IDE for contextual helpfullproof ↗
Review diffs visually and run multiple sessions side by side in a desktop appfullproof ↗
Manage multiple agent-driven coding sessions from one unified workspacefullproof ↗
Run the agent non-interactively in scripts for workflow automationpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Have the agent stage changes, write commit messages, create branches, and open pull requestsfullproof ↗
Inspect diffs and run checks to catch problems before mergingpartialproof ↗
Control which external tools and integrations the agent is allowed to accesspartialproof ↗
Claims outside our story set (7)
Real capability claims found in Conductor’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Create private workspaces not shared with the rest of the team”
source ↗“Search file contents within a local project or cloud workspace”
source ↗“Edit attachments that are queued in messages before sending”
source ↗“Copy, save, download, or open images from chat previews”
source ↗“Enable exclusive port forwarding so only one workspace forwards ports at a time”
source ↗“Reassign a workspace to make a teammate responsible for it”
source ↗“Checkpoints let you revert code and chat state to an earlier turn in a session”
source ↗
Business model
Free Mac app runs local parallel agents with your own keys/subscriptions; Pro $50/mo adds Conductor Cloud, API and multiplayer; Teams $60/user/mo; Enterprise custom.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
