stablyai/orca · error · RuntimeClientError

invalid_argument

invalid_argument

Error message

The packaged Orca launcher did not provide a valid resume command. No question was created.

What it means

Thrown by resolvePackagedWindowsCompatibilityCommand when the packaged Orca launcher indicates it should provide a resume command (ORCA_WINDOWS_PACKAGED_CLI_LAUNCHER=1) but the command environment variable is missing or not one of 'orca'/'orca-ide'. This is an internal launcher-configuration error on Windows packaged builds: the orchestration/resume flow needs a known-good command to relaunch, and the launcher did not supply one.

Source

Thrown at src/cli/handlers/orchestration.ts:129

    }

function resolveCompatibilityCliCommand(): 'orca' | 'orca-ide' | 'orca-dev' {
  const configured = process.env.ORCA_CLI_COMMAND
  if (configured === 'orca' || configured === 'orca-ide' || configured === 'orca-dev') {
    return configured
  }
  return process.platform === 'linux' ? 'orca-ide' : 'orca'
}

function resolvePackagedWindowsCompatibilityCommand(): 'orca' | 'orca-ide' | undefined {
  if (process.env.ORCA_WINDOWS_PACKAGED_CLI_LAUNCHER !== '1') {
    return undefined
  }
  const command = process.env.ORCA_CLI_COMMAND
  if (command === 'orca' || command === 'orca-ide') {
    return command
  }
  throw new RuntimeClientError(
    'invalid_argument',
    'The packaged Orca launcher did not provide a valid resume command. No question was created.'
  )
}

async function flushStdout(): Promise<void> {
  await new Promise<void>((resolve, reject) => {
    process.stdout.write('', (error) => {
      if (error) {
        reject(error)
      } else {
        resolve()
      }
    })
  })
}

function getOptionalStructuredMessagePayload(

View on GitHub (pinned to 1136503c6a)

Solutions

1. Set ORCA_CLI_COMMAND to 'orca' or 'orca-ide' in the packaged launcher environment.
2. If you do not need the packaged-compatibility path, unset ORCA_WINDOWS_PACKAGED_CLI_LAUNCHER so the normal command resolution applies.
3. Update the packaged launcher/installer to always export ORCA_CLI_COMMAND alongside the flag.

Example fix

// before
export ORCA_WINDOWS_PACKAGED_CLI_LAUNCHER=1
# ORCA_CLI_COMMAND missing
// after
export ORCA_WINDOWS_PACKAGED_CLI_LAUNCHER=1
export ORCA_CLI_COMMAND=orca

function resolveLauncherCommand(): 'orca' | 'orca-ide' | undefined {
  if (process.env.ORCA_WINDOWS_PACKAGED_CLI_LAUNCHER !== '1') return undefined;
  const cmd = process.env.ORCA_CLI_COMMAND;
  if (cmd === 'orca' || cmd === 'orca-ide') return cmd;
  throw new Error('Set ORCA_CLI_COMMAND to "orca" or "orca-ide" for the packaged launcher');
}

function isLauncherCommand(value: unknown): value is 'orca' | 'orca-ide' {
  return value === 'orca' || value === 'orca-ide';
}

When it happens

Trigger: Running a packaged Windows Orca build where ORCA_WINDOWS_PACKAGED_CLI_LAUNCHER=1 is set but ORCA_CLI_COMMAND is unset, empty, or set to something other than 'orca' or 'orca-ide'. The check reads process.env.ORCA_CLI_COMMAND and compares against the two allowed values.

Common situations: A packaged build whose launcher forgot to set ORCA_CLI_COMMAND; a custom launcher/wrapper that sets the flag but not the command; an env that was partially migrated; testing a resume/orchestration flow without the full launcher env.

Related errors

• Unsupported --expect=${value}. Use none, repro, or pass.
• Unsupported --gpu=${value}. Use on, off, auto, or a comma-li
• Unknown argument: ${arg}
• No user WSL distro found. Install/enable WSL or pass --distr
• unsupported_platform

AI-assisted analysis of stablyai/orca@1136503c6a (2026-08-12). Data as JSON: /api/errors/e147e36aa796e21e. Report an issue: GitHub.