Conductor is a Mac app that runs several AI coding agents such as Claude Code, Codex, Cursor Agent and OpenCode in parallel and gives every workspace its own Git worktree. It adds diff review, pull requests, Conductor Cloud with isolated sandboxes, an iOS app and an API. As an AI harness, Conductor mainly covers the orchestration building block. As of 22 November 2026.
What is Conductor?
Conductor is a proprietary tool by Melty Labs, Inc. from San Francisco that launched in July 2025. On 4 November 2026, the team announced with version 0.93.0 that it was joining Meta and initially planned to shut down Conductor Cloud on 20 November. With version 0.94.2 from 13 November, it reversed the shutdown (“Conductor is back”), and the website has since listed the product as “Conductor from Meta”. According to the changelog, the current version is 0.98.0 from 20 November 2026, with several releases per week. The desktop app runs on macOS only; there is a waitlist for Windows and Linux. According to the website, more than 100,000 developers use Conductor.
Conductor as an AI harness
Conductor is the workspace layer above the agents: according to its harness overview, it manages repositories, workspaces, sessions, terminals, diffs, checks and pull requests, while the harness runs the agent loop and tool calls. Every workspace gets its own Git worktree with a branch, named after a city. Several chats in the same workspace share branch and code, so Claude Code can implement while Codex reviews in a second tab. Setup scripts prepare new workspaces, checkpoints save the state before every agent response, and the PR view shows review comments and CI status.
Besides local operation, there is Conductor Cloud: every agent runs in its own Linux sandbox with 8 vCPUs and 16 GB RAM, and workspaces and chats can be shared with the organization and prompted together. The iOS app controls cloud workspaces and, experimentally via remote control, local workspaces on the Mac as well. An API in beta creates cloud workspaces and starts agents, also through an MCP server.
Models and model access
Within its four harnesses, Conductor is model-agnostic: Claude Code uses Claude models via subscription, the Anthropic API or third-party providers, Codex uses GPT models via a ChatGPT plan or API key, Cursor Agent uses the models of the Cursor account, and OpenCode the providers configured there. According to its docs, Conductor does not bill model usage. For Claude Code, the provider guide describes OpenRouter, Vercel AI Gateway, Amazon Bedrock and Z.ai via ANTHROPIC_BASE_URL or Bedrock variables, and for Codex OPENAI_BASE_URL. This also lets you route model access through a central proxy such as innFactory’s AI Gateway. Since version 0.98.0, a usage page shows chats, tokens and estimated costs of local workspaces per model and workspace.
Company use: data protection and governance
Companies should settle four points before a broad rollout. First, permissions: per its FAQ, local agents run without a sandbox with all the permissions of your user account. A worktree only separates files, not processes, network access or credentials; Conductor itself recommends a separate machine or VM for extra safety. Second, the cloud: per the cloud FAQ, cloud workspaces run in Vercel sandboxes in the us-east-1 region, and Conductor stores session content on its own servers. Third, telemetry: analytics events with metadata, error messages, operating system and IP address go to PostHog, and the privacy page does not mention a switch for it. Fourth, the product roadmap after the move to Meta, which remains open for long-term rollouts. For central policies, Conductor offers managed settings in ~/.conductor/settings.managed.toml, for example for endpoints and the “Enterprise data privacy” option, which disables AI-based extras and custom MCP servers.
Which agents does Conductor support?
Conductor supports exactly four harnesses: Claude Code, Codex, Cursor Agent and OpenCode. Claude Code, Codex and OpenCode come bundled; Conductor can use your own installation instead. Cursor Agent runs through the Cursor API with its own API key. You choose one harness and one model per chat tab. Claude Code’s experimental agent teams can be enabled via an environment variable. Further CLIs such as Gemini CLI, Amp or Pi are not supported as harnesses; Orca, Paradev or herdr cover those.
How it fits: Conductor, Orca, herdr and the AI Gateway
Conductor supports fewer agents than Orca or Paradev and is not open source, but offers a tightly guided interface and an extensive cloud with team features. herdr, by contrast, relies on long-lived terminals and barely intervenes in the agents. You will find a detailed comparison in the article herdr vs. Orca. Conductor’s usage page shows costs per machine; developers’ costs and agent time across teams and projects are captured by the AI Gateway in proxy and companion mode. For business users outside development, CompanyGPT is the right harness; our AI harness overview gives an overview.
