connector CLI launch information is unavailable

Error message

connector CLI launch information is unavailable

What it means

Error "connector CLI launch information is unavailable" thrown in cline/cline.

Source

Thrown at sdk/packages/core/src/services/connectors/connector-cleanup.ts:36

 *
 * What has to be cleaned up — the process state file, thread→session bindings,
 * and the hub sessions the connector owned — is all connector-specific knowledge
 * that lives in the CLI's adapters. Rather than duplicate those conventions in
 * the hub, the supervisor shells back into the CLI's own stop path, which
 * already does exactly this for a process that is no longer running.
 *
 * `--cleanup-instance` deliberately preserves the autostart record: the instance
 * died, it was not retired, so the supervisor still intends to restart it.
 */
export async function cleanupConnectorInstanceViaCli(
	channel: string,
	instanceId: string,
	options: CleanupConnectorInstanceOptions = {},
): Promise<void> {
	const spec =
		"launchSpec" in options ? options.launchSpec : readConnectorCliLaunchSpec();
	if (!spec) {
		throw new Error("connector CLI launch information is unavailable");
	}
	const spawnProcess = options.spawnProcess ?? spawn;
	const timeoutMs = options.timeoutMs ?? CLEANUP_TIMEOUT_MS;

	await new Promise<void>((resolve, reject) => {
		let settled = false;
		let timer: ReturnType<typeof setTimeout> | undefined;
		const finish = (error?: Error) => {
			if (settled) {
				return;
			}
			settled = true;
			if (timer) {
				clearTimeout(timer);
			}
			if (error) {
				reject(error);
			} else {

View on GitHub (pinned to 491b30b806)

When it happens

Trigger: Thrown at sdk/packages/core/src/services/connectors/connector-cleanup.ts:36 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of cline/cline@491b30b806 (2026-08-25). Data as JSON: /api/errors/c1e796e7ced9bfb6. Report an issue: GitHub.