Conductor is back: what to check before restarting your agents

Conductor says it is not shutting down. Its 0.94.2 release note, dated 13 November 2026, reverses the wind-down message. For people running Claude Code or Codex through Conductor, the immediate job is to verify the workspace and funding route before restarting agents, not to assume every old deadline and setting has been resolved.

Checked 14 November 2026. This is a service-status follow-up to the earlier shutdown reports, not a migration benchmark, account-access test or announcement of new provider usage limits.

What changed after Conductor's shutdown announcement?

The maker's release note says development is continuing. Separately, All Things Muse reported on 12 November that founder Charlie Holtz had announced continued development inside Meta. The dated maker release is the first-hand confirmation behind this article; the separate report corroborates the reversal rather than proving every operational detail.

The current homepage promotes Cloud and says Conductor runs first-party Claude Code, Codex, Cursor and OpenCode agents. A product page establishes the advertised offer. It does not establish whether a particular old cloud workspace is writable or whether your saved integration still works.

Are the old Cloud deadlines definitely canceled?

Do not repeat an old shutdown schedule as current fact, but do not invent a replacement timetable either. All Things Muse's reversal report explicitly left the Cloud dates unresolved. The short 0.94.2 note does not provide a detailed revised schedule.

Current evidence	What it supports	What still needs checking
Dated 0.94.2 maker note	Conductor says it is not shutting down	Service-specific timetable and account notices
Homepage promotes Cloud	Cloud remains part of the advertised product	Existing workspace access and retained data
Independent reversal report	Continued development was separately reported	Later operational changes since that report

For an existing project, inspect the notice inside your account and verify that the specific workspace opens. Preserve any export you already made until you have checked its contents and confirmed what is available in the current product. That is our precaution, not a newly announced retention policy.

Does the return change which subscription pays for your agents?

The return announcement does not establish a new model allowance or universal free access. In Codex authentication, OpenAI still distinguishes ChatGPT subscription sign-in from API-key usage billed through the Platform account. For Claude, Anthropic's legal guidance distinguishes an end user signing into unmodified Claude Code from a third-party app collecting consumer credentials.

Check the selected runtime and account in your installation. Do not infer a supported subscription route merely because a model's name appears in a picker. Our Conductor listing, Claude app hub and ChatGPT app hub are discovery starting points; the actual session and current provider rules determine the connection.

What should you check before resuming scheduled agents?

Treat a resumed workflow as a small acceptance check. Start with a non-sensitive repository and no irreversible task. Confirm the expected branch and files, then check that the agent can complete a bounded read-only request through the intended account.

Review scheduled jobs separately from interactive chats. Check their model route, permissions, writable folders and any configured paid fallback before enabling them. The fallback billing audit explains that inventory; the login diagnosis guide helps when a saved connection fails. Neither a successful sign-in nor a resumed product announcement proves that unattended work has the correct payer.

What should you keep if you already prepared to move?

Keep the repository copy, branch references, necessary conversation exports and a record of project setup until you have compared them with the restored workflow. Do not discard a working alternative solely because the headline changed, and do not run two scheduled copies of the same job by accident.

We have not logged into Conductor, tested exports or measured model billing for this article. The confirmed news is the maker's reversal and continued development. Workspace access, detailed cloud timing and the account's actual funding remain checks for the person operating that installation. Recheck the linked maker note before relying on any service-status summary, including this one.