Conductor Joins Meta: Shutdown Timeline, Cloud Read-Only Date, and Alternatives
Conductor, a desktop and cloud app for orchestrating coding agents, announced that it is joining Meta. The announcement on conductor.build includes a staged shutdown: new signups and downloads stop on Wednesday, Nov 4, Conductor Cloud goes read-only on Friday, Nov 13, and the local app continues for now but begins winding down in early 2027. The Hacker News thread that followed mixed congratulations for the team with frustration over how quickly paying users lost the cloud product they depended on.
What Conductor is and what was announced
Conductor is a tool for running and managing coding agents, offered as a local desktop app and as a hosted cloud product. The company announced it is joining Meta and published a shutdown schedule for its own products on the same page.
Co-founder Charlie Holtz confirmed the news in the Hacker News thread and pointed back to the project's origin:
Conductor actually kicked off with a HN post many lifetimes ago in July 2025. I owe so much to this community. Thank you all so much! The whole team is around to help answer any questions.
The announcement does not describe what the team will work on at Meta. Commenters speculated that the technology itself is part of the acquisition, which is why an open-source release of the desktop app was not offered.
The shutdown timeline, as stated in the announcement
Conductor published specific dates for winding down its products. According to the announcement as quoted in the thread:
- Wednesday, Nov 4: New users can no longer sign up for Conductor or download the app.
- Friday, Nov 13: Conductor Cloud goes read-only.
- November 20: Conductor Cloud shuts down.
- Early 2027: Local Conductor, which continues working as normal in the interim, starts winding down.
One commenter summarized the sequence and compared it to another recent acquisition announcement:
Things will shut down over the next few months. [...] Flashback to Cloudflare acquiring Deno and hiding the shutdown at the bottom of their announcement.
The compressed timeline drew criticism from users who had recently committed to the paid cloud product. One commenter wrote that they had decided to go "all in" on Conductor Cloud the day before the announcement and were now requesting a refund and moving their organization to t3.codes.
Users say the shutdown timeline is rushed
The strongest criticism in the thread was not about the acquisition itself but about how little notice cloud customers received. Conductor Cloud going read-only on November 13 and shutting down on November 20 gives paying users roughly a week of read-only access before the product disappears.
I'm not a Conductor user, but the shutdown timeline seems rather rushed no?
Another commenter highlighted the mismatch between the shutdown notice and the product changelog published alongside it:
The changelog is truly hilarious: > Conductor Cloud goes read-only on November 13 and shuts down on November 20. 3 sentences later > Add your own completion sounds in Settings → General. [...] If you're shutting down in 9 days I really don't care that you added custom sound effects.
The sentiment among heavy users was summed up by one short comment: "Glad for the team, sad for the product."
What users say they will miss: cloud webhooks, session APIs, and isolated VMs
The features users mourned were concentrated in Conductor Cloud rather than the local app. One user described the specific capabilities they relied on:
Having cloud webhooks + workspace/session API + isolated VMs has been a massive productivity boost for me. Does anyone have suggestions for products that can match Conductor Cloud, not just Conductor Local?
Because Local Conductor remains functional until early 2027, the immediate migration pressure falls on cloud users who depend on remote execution and programmatic access.
Alternatives named in the discussion
The thread filled with users asking for and offering replacements, and several founders promoted their own tools directly in the comments. Named alternatives include:
- t3.codes, cited by multiple users, including one who said they had already switched weeks earlier and felt the Conductor product "felt a bit stale."
- Orca, mentioned by a user who migrated for better multi-machine and remote control.
- Herdr and Stencil's Tern, raised as options by the same commenter, who also cautioned that "these tools are a dime-a-dozen now."
- podium.do, built by a commenter who wanted a built-in task system for splitting complex work across agents and running agents on their own machines.
- superintelligencehive.com, described by its creator as a local orchestrator that is "forever free."
At least one team did not wait for a replacement. A commenter reported reverse engineering the product within a day:
This morning my team was a bit grumpy about this. This afternoon we've already forked + reverse engineered the whole project, including Passport (our favorite feature)! LLMs truly are amazing, lol.
The moat question: why commenters think agent harnesses are easy to clone
The most substantive argument in the thread was that agent orchestration tools have no durable technical moat, so acquisitions in the category are really about users and distribution.
There is literally no moat in most software expect the users a product has acquired. The number of slightly different solution to an existing product is wild.
A second commenter reached the same conclusion from the volume of self-promotion in the thread: "Judging by the number of alternatives that are promoted by their founders here there is clearly no moat in this."
Another commenter argued the economics are structurally difficult for small players because the model providers can always undercut resellers:
The economics of these harnesses I don't think lend to many winners, the model usage plans the big guys have at offer will always undercut the small players no matter how much they try to resell an openmodel for $20/mo.
Conductor is not Orkes Conductor
One clarification worth recording: this Conductor, the agent orchestration app, is unrelated to Orkes Conductor, the workflow orchestration platform that was the subject of a recent Jepsen analysis.
For anyone else who did a double take, this is different to Orkes Conductor which was the subject of a recent Jepsen analysis.
Practical takeaways for current Conductor users
Users who need Conductor Cloud should plan to export data and migrate before the read-only date of Friday, Nov 13, since the cloud product shuts down on November 20. Users who only rely on the local desktop app have more time: Local Conductor continues to work as normal, with a wind-down beginning in early 2027. New users cannot sign up or download the app after Wednesday, Nov 4.
For teams evaluating replacements, the discussion suggests the differentiator to check is not the local agent UI, which many tools now provide, but remote execution features such as isolated VMs, workspace and session APIs, and cloud webhooks.