Meta buys Conductor, the parallel coding-agent orchestrator, for Superintelligence Labs
The Mac app that runs Claude Code, Codex, Cursor and OpenCode side by side joins Meta Superintelligence Labs, and Conductor Cloud shuts down on 20 November. What survives is the workflow pattern, not the product.
What happened
Summary of reporting by TechCrunchMeta has acquired Conductor, the startup behind a Mac app that runs several coding agents side by side in one development loop. Deal terms were not disclosed. Founder and CEO Charlie Holtz and his team are joining Meta Superintelligence Labs. Reporting: TechCrunch, The Register, Axios via Techmeme.
Conductor orchestrates Claude Code, Codex, Cursor and OpenCode in parallel. Each task gets its own workspace with its own branch, files, terminal, diff and review path, and several agents can share one workspace when their changes must land on the same branch. A Checks tab gathers git status, pull request metadata, CI status, deployments and review threads before merge (parallel agents, checks).
The product now winds down. Per the changelog dated 4 November 2026, Conductor Cloud goes read-only on 13 November and shuts down on 20 November, with cloud data deleted afterwards. Local builds keep getting new models and critical bug fixes only until early 2027. Conductor charged nothing for local parallel agents, $50 per month for Pro and $60 per user per month for Teams (pricing).
The purchase extends Meta's push into agentic software development, alongside its existing coding tools.
The Azrty take
Meta has bought the multi-agent developer interface. GCC engineering leaders should own the workflow, the gateway and the merge gate instead of renting the UI.
Start with the business reality. The multi-agent developer interface is consolidating into the big platforms, and Conductor's own changelog shows what that means for customers. Sixteen days after the 4 November 2026 announcement, Conductor Cloud shuts down on 20 November and the cloud data is deleted after that. Local builds get new models and critical fixes only until early 2027. Anyone who moved their development loop into Conductor Cloud got sixteen days of notice. What survives an acqui-hire is not the interface. It is the workflow shape: one isolated worktree per task, agents fanned out across issues, and one merge gate where a person decides.
Conductor earned the attention because the loop it built is the one engineering teams keep re-inventing. Per its docs, each task gets its own workspace, branch, files, terminal, diff and review path, running Claude Code, Codex, Cursor or OpenCode in parallel; when changes must land together, several agents share one workspace and one branch (parallel agents). The free tier ran that locally, Pro cost $50 per month for cloud workspaces, the Conductor API and the mobile app, and Teams cost $60 per user per month (pricing). Local sessions sent prompts straight to the model provider; cloud sessions ran in Vercel sandboxes (8-core CPU, 16GB RAM, us-east-1) with chat messages stored on Conductor's own servers. For GCC code-handling policies, that last point is the hard question. Meta is buying the orchestration layer around models it does not own: the agents come from Anthropic and OpenAI.
Where teams will get it wrong is buying the fan-out and skipping the gate. Conductor's Checks documentation describes merge blocking as something the app may do when todos or checks are open (checks): advisory, not enforced. Multiply that by five parallel agents and you have half-finished diffs, duplicated work on shared files, and a reviewer reconciling branches under time pressure. Concurrency without a hard quality gate multiplies token spend and defect rate together. The second mistake is treating orchestration UX as strategy: once the vendor is acquired, the roadmap becomes someone else's platform decision, and your team inherits the shutdown dates.
Our position: keep the orchestration on your infrastructure and make the merge gate the system of record. One git worktree per task, agents fanned out per issue, every model call through a single OpenAI-compatible gateway with per-team budgets and access control, then a required gate of tests, lint and format checks plus an independent review before merge. In our stack that is FastLLM Proxy as the gateway, quality gates in the style of Procoder, and isolated agent runs with an independent review in NovaForge, with Dhole holding the human approval step where a change is risky (AI engineering). The policy shape looks like this:
# Merge gate policy for agent-authored branches
merge_policy:
isolation: one-git-worktree-per-task
gateway: fastllm-proxy # one OpenAI-compatible endpoint, per-team budgets
required_checks:
- go test ./...
- golangci-lint run
- gofmt -l . # must print nothing
merge:
independent_review: true # reviewer did not author the change
untested_work: block
For UAE and GCC organisations the acquisition sharpens a data question rather than a coding one. Cloud mode stored session inputs and outputs on the vendor's servers in us-east-1, and those records are now being deleted on a short clock. Enterprise development loops in the region are better served by running agents and gates on infrastructure you control, with residency, budgets and audit in your own tenancy. That is the work our team in Dubai does: platform design, deployment and support. Parallel agents genuinely compress the time from issue to reviewed pull request, but the durable asset is the gate and the gateway, not the agent window. Expect more acqui-hires of developer-tool startups in 2027, and plan for your workflow to outlive any of them.
What to do now
- If any team used Conductor, get the work out now: export or transfer every cloud workspace to local before Conductor Cloud goes read-only on 13 November and shuts down on 20 November 2026, and confirm the repository state you need is in your own git remote, not only in the vendor's app.
- Put a hard merge gate on agent-authored branches: required status checks for tests, lint and format in GitHub or GitLab branch protection, or Procoder and NovaForge where you want the gate and the independent review built in, so untested or unformatted work cannot merge.
- Route all coding-agent traffic through one gateway (FastLLM Proxy) with per-team budgets and access control, pin the agent CLIs (Claude Code, Codex, Cursor) to versions you have tested, and log model and cost per task.
- Pilot the fan-out pattern on one repository: one git worktree per issue, three to five parallel agents, a single reviewer at the merge point. Measure merge conflicts, review time and token spend per merged pull request for four weeks before widening it.
- Before adopting any agent tool with a cloud mode, check where session data is stored, who can delete it and on what notice, and require an in-tenancy or self-hosted option for repositories carrying client or regulated data.
