What happened
Zed Industries’ Delta blog announcement, written by Franciska Dethlefsen and dated November 10, 2026, introduces an import path for Conductor chats. The post frames it as a response to Conductor winding down after its team announced it was joining Meta. Conductor Cloud will stop accepting new messages on November 13 and shut down on November 20, when data deletion begins, according to Delta’s announcement.
The migration begins by moving any Cloud workspaces to the user’s computer. In Conductor, the user right-clicks each Cloud workspace and chooses “Transfer to local.” Delta says to do this before November 20; users whose chats are already local can skip this step. The user then downloads and opens Delta, signs in, and sets up a provider of their choice. From the menu bar, they choose “Delta → Import Conductor Chats.” Delta also offers an import option in a sidebar prompt when it detects Conductor chats on the computer.
Imported conversations appear as private threads tagged “Conductor,” initially without a project. Users can sort them into projects themselves or choose “Organize with Delta” to have an agent sort them. The announcement draws a clear boundary around what the importer transfers: conversations, not complete workspaces. Delta recommends exporting a backup from Conductor separately to preserve everything, including files and attachments.
For users who depended on Conductor Cloud, Delta says it is launching Cloud Runners “tomorrow” relative to the November 10 announcement. A user can choose Cloud on a thread so its agent runs on a hosted runner rather than the user’s computer. Delta says the conversation and code stay in sync across desktop, web, and phone. The blog also says Delta works with agents and subscriptions users already have; Claude Code sessions sync to Delta through its CLI, with support for Pi and Codex described as coming next. Delta says it is adding support for the Agent Client Protocol (ACP) so more agents can run directly in Delta. The announcement does not state an importer price or specify a limit on the number or size of chats.
What the archive adds
New Runtime’s earlier coverage reported that Meta acquired Conductor and Conductor Cloud would shut down on November 20. That earlier note established the shutdown; Delta’s importer is a new response to the same event, with specific migration steps and a limitation that conversations transfer without complete workspaces.
Trend signal
This update is adjacent to the question of whether agent work can survive changes in tools: Delta presents conversations as context that users should be able to carry between agents. It does not yet demonstrate a broadly portable capability layer, however. This does not yet fit a pattern New Runtime tracks.
Why now
The timing follows Conductor’s shutdown schedule. Delta’s announcement gives users less than two weeks between its November 10 publication and the November 20 closure, while Cloud Runners are announced for the day after publication as an alternative for users who relied on hosted execution.
Why it matters
Agent conversations can contain decisions, constraints, and iterations that are difficult to reconstruct from the final code alone. Preserving that history may help a team understand why an implementation took its current form and give a later agent useful context. That is especially relevant during a tool migration, when switching environments can otherwise force people to rediscover prior work.
But the importer is not a full recovery mechanism. A conversation history without its associated files, attachments, or workspace state may not be enough to resume a task. Teams should treat chat migration and workspace backup as separate jobs, verify that important threads arrived, and check that required project material remains accessible. Delta’s offer is one vendor’s route into its own product; the announcement does not establish that imported threads can subsequently be exported in a portable format or that another agent can consume every part of their history.
Limits and uncertainty
Delta’s announcement describes the importer’s workflow but does not report tests of migration completeness, supported conversation counts, maximum archive sizes, or how formatting and tool-call details are handled. It explicitly says the importer moves conversations rather than complete workspaces and recommends a separate Conductor backup for files and attachments. The announcement does not establish how long that backup remains retrievable after shutdown, whether imported threads preserve every kind of context, or whether users can export them from Delta later. These are practical issues for teams deciding whether the migration is sufficient for their records.
Skill to build now
If your team has Conductor Cloud workspaces, inventory them and transfer the ones you need to local storage before November 20. Import the conversations into Delta, then separately export and check a backup for files and attachments. A small verification pass—opening several representative threads and confirming that referenced project materials exist—can reveal gaps before the shutdown date rather than after it.
Reader takeaway
Delta gives Conductor users a concrete way to keep conversation history, not a complete workspace migration. Move Cloud workspaces locally before November 20, import the chats, and preserve files and attachments with a separate backup. Treat the migrated threads as useful context, then verify that the project state needed to continue work survived independently.