On this page

Conductor (conductor.build) published an announcement titled Conductor is joining Meta, signed Charlie, with a matching changelog entry 0.93.0: Conductor is joining Meta dated November 4, 2026 (https://www.conductor.build/announcement; https://www.conductor.build/changelog/0.93.0-conductor-is-joining-meta). DigIntoAI records the November 4 date from Conductor’s own announcement and changelog; neither page publishes a finer UTC clock. The official lead sentence is joining Meta—not a disclosed purchase price, equity split, or closed-deal filing. DigIntoAI has not separately confirmed a Meta company blog post, and does not treat an unconfirmed Meta company blog as a primary source.

The product that is winding down on a short calendar is Conductor Cloud. Local Conductor is described as continuing with new models and critical bug fixes until early 2027. DigIntoAI has not hands-on tested Transfer to local, Settings → Account → Export data, or refund timing—facts below follow Conductor’s self-reported announcement and FAQ.

Related DigIntoAI notes on similar “join + cloud wind-down” and coding-agent context: Chroma Joins Replit: Cloud Writes Stop Nov 22, Reads Dec 22, Same Model, Different Coding Harness: Pass Rate Barely Moves, the Bill Does, Cursor Agent SDK Is Out: Folders, Eval, and Deploy, and Best Coding Agents Right Now, Ranked by Artificial Analysis (October 2026).

What Conductor says happened on November 4

Charlie’s note places the product’s public start in July 2025, framed around writing most of a codebase with coding agents—and a team of coding agents. The November 4 line is organizational: Conductor is joining Meta. The same note thanks early users and says the team has “big, crazy plans for the next interface,” then: We’ll have something new… early next year (Conductor’s wording). The FAQ repeats a softer hope to have something new by the time Local winds down. DigIntoAI treats that as a fuzzy forward promise—not a product name, not a locked ship date, and not a Meta product-line map.

Changelog 0.93.0 restates the join line, links the announcement, and repeats the Cloud / Local timeline. The same changelog also lists product improvements (for example custom completion sounds, archived cloud workspace panels, and GPT-6.1 Terra in the Codex model picker). Those improvements are not the main story here; the operational cut for operators is the Cloud read-only / shutdown calendar.

Timeline operators need

Conductor’s announcement lists four timeline beats. DigIntoAI aligns them to the local calendar dates Conductor prints (Nov 4 / 13 / 20) and notes Asia/Shanghai calendar days for the same November dates when useful—without adding clock times the pages do not publish.

  1. Wednesday, November 4 — No new sign-ups. New users can no longer sign up for Conductor or download the app. Existing free users can’t upgrade to a pro plan. Existing pro users can keep using pro features for free. Existing free users remain free but can’t move up to pro.
  2. Friday, November 13 — Conductor Cloud goes read-only. Cloud workspaces stay readable for old chats and export, but new messages can’t be sent. Active subscribers will get a refund.
  3. Friday, November 20 — Conductor Cloud shuts down. Conductor says it will begin deleting Conductor Cloud user data. The announcement says Cloud data must be exported before this date.
  4. Local Conductor — continues to receive new models and critical bug fixes until early 2027. The FAQ adds that Local will start winding down in early 2027, with the same hope of something new by then.

In Asia/Shanghai terms, those are calendar 2026-11-04, 2026-11-13, and 2026-11-20 for the three Cloud milestones Conductor labeled Wednesday / Friday / Friday—plus Local support through early 2027. DigIntoAI has not verified refund ledger entries or deletion jobs beyond Conductor’s written schedule.

Migration paths Conductor describes

For Cloud → Local, Conductor says: right-click a cloud workspace and choose Transfer to local to move the workspace and its chats to a Mac. For a full archive, go to Settings → Account → Export data. Support contact listed: support@conductor.build. DigIntoAI has not run Transfer to local or Export data on a live account, and has not confirmed refund delivery timing.

Privacy line (FAQ)

Conductor’s FAQ states the company has never sold or trained on Conductor user data, and still won’t. It also says Conductor will delete all Conductor user data when the app shuts down in early 2027, and points to its privacy policy. That early-2027 deletion line is about the broader app wind-down described in the FAQ; the November 20 Cloud shutdown is the nearer Cloud-data deletion start date Conductor printed for Cloud specifically. DigIntoAI has not audited either deletion process.

What joining Meta covers on the record

  1. Joining Meta is Conductor’s official wording. Conductor’s pages do not disclose an acquisition price, closed transaction, equity structure, or Meta org-chart landing.
  2. DigIntoAI did not separately confirm a Meta company press room / company blog post—and does not treat an unconfirmed one as a primary source.
  3. Conductor’s announcement does not name team headcount, reporting lines, or which Meta product family Conductor joins.
  4. This Conductor is conductor.build (coding-agent desktop / cloud). It is not Microsoft’s open-source Conductor execution environment. DigIntoAI does not merge those stories.
  5. DigIntoAI has not tested migration, export, or refunds.

Quick facts

  1. Who. Conductor (conductor.build); announcement signed Charlie; changelog 0.93.0.
  2. When. Announcement / changelog date November 4, 2026 (Asia/Shanghai calendar 2026-11-04).
  3. What. Official line: Conductor is joining Meta; Cloud wind-down; Local support into early 2027.
  4. Cloud Nov 13. Read-only; refunds for active subscribers; no new messages.
  5. Cloud Nov 20. Shutdown; begin deleting Conductor Cloud user data; export beforehand.
  6. Local. New models + critical bug fixes until early 2027.
  7. What’s next. “Something new… early next year” / FAQ hope—fuzzy, unnamed.
  8. Move data. Transfer to local; Settings → Account → Export data; support@conductor.build.
  9. Hands-on. DigIntoAI has not tested Transfer / Export / refunds.
  10. Meta company blog. Not separately confirmed here.

In short

Conductor’s November 4, 2026 announcement and changelog 0.93.0 say Conductor is joining Meta, stop new sign-ups immediately, put Conductor Cloud into read-only on November 13 (with refunds for active subscribers) and shut Cloud down on November 20 while beginning Cloud user-data deletion, and keep Local Conductor on new models and critical fixes until early 2027. A newer product is described only as coming early next year—not as a named ship. DigIntoAI has not tested the migration tools or refunds, and has not treated an unconfirmed Meta company blog as a second primary source. Facts follow Conductor’s self-reported announcement and FAQ.