Conductor reverses shutdown and withdraws Cloud deadlines
Conductor says it is not shutting down and has crossed out its November Cloud deadlines. Its revised announcement confirms continued development.
14 November update: Conductor reverses its shutdown plan
Conductor’s 0.94.2 changelog now explicitly says the product is not shutting down and development has resumed. The earlier 0.93.0 entry has crossed out the Cloud read-only date of 13 November, the shutdown date of 20 November and the previous local-support timeline. Those dates should no longer be treated as current deadlines.
This resolves the conflict we reported on 13 November, when the announcement had changed but the older changelog still displayed the wind-down schedule. The revised announcement and FAQ say development will continue and the product will keep working normally.
For teams using Conductor for store development, the announced shutdown is no longer a reason to rush a migration. Keep ordinary backups of important work; the FAQ still documents workspace transfer and data export. We have verified the public statements, not tested every Cloud workspace or established a new long-term support guarantee.
Earlier shutdown account — historical context
The account below records the superseded announcement. Its shutdown, sign-up, refund and support-timeline statements are historical, not current instructions. Read them against the reversal above.
Conductor Cloud becomes read-only on 13 November 2026 and shuts down on 20 November, following the coding-tool company's move to Meta. For agencies and store development teams with work in its hosted workspaces, the immediate task is to preserve that work and arrange where development will continue.
The company's announcement and timeline say users can still read old chats and export data during the read-only period, but cannot send new messages. Cloud user-data deletion begins on 20 November. The announcement gives dates without a cutoff timezone; our recommendation is to finish the export before the shutdown day.
Two ways to preserve the work
Conductor's 0.93.0 changelog documents two routes. To move an individual cloud workspace and its chats onto a Mac, right-click the workspace and select Transfer to local. To download an archive of the account's data, use Settings → Account → Export data.
Our suggested handover check: list the active client projects, assign an owner to each transfer, and open the resulting local workspace or archive. Confirm that the files and conversations needed for unfinished work are present. Separately check that intended code changes have reached the team's repository and that someone knows how to resume the build. A completed download alone is not a tested recovery plan.
Local use has a longer runway
The changelog says local Conductor will receive new models and critical bug fixes until early 2027. That gives existing users a transition route, not an indefinite support commitment. The company has stopped new sign-ups and says active subscribers will receive refunds.
For ecommerce teams, this is a development-workspace deadline. It does not establish that a deployed Shopify store or app stops serving customers when Conductor Cloud closes. Check where the live service actually runs, then separate production hosting from the tool used to work on its code.
The practical lesson is to keep project continuity independent of any one coding interface: accessible repositories, a documented build process and a recoverable record of unfinished decisions. Teams also reviewing their hosting dependencies can read our Gadget migration deadline guide; that is a separate service change with its own timetable.
Charlie Holtz announces Conductor's move to Meta, 4 November 2026
Read the founder's original announcement if the embed is unavailable.
More from News
See all →