stablyai/orca · error · Error

Orca could not verify the originating Codex session file, so

Error message

Orca could not verify the originating Codex session file, so automatic resume was stopped to avoid using a different account.

What it means

Thrown (UNVERIFIED_CODEX_RESUME_ERROR) when dropAgentResumeArgvFromCommand returned status 'unrecognized' AND the session metadata claimed Codex provenance (claimedCodexProvenance). Orca could not strip the resume argv from the launch command, and because the session claims to be a real Codex rollout, launching would risk resuming under whichever account is currently selected — potentially a different account. So it aborts the launch rather than cross accounts.

Source

Thrown at src/main/codex/codex-unverified-resume-launch.ts:32

 */
export function dropUnverifiedCodexResumeArgv(args: {
  command: string | undefined
  providerSession: AgentProviderSessionMetadata | null
  claimedCodexProvenance: boolean
}): { command: string | undefined; droppedResumeArgv: boolean } {
  if (!args.command || !args.providerSession) {
    return { command: args.command, droppedResumeArgv: false }
  }
  const drop = dropAgentResumeArgvFromCommand({
    command: args.command,
    agent: 'codex',
    providerSession: args.providerSession
  })
  if (drop.status === 'dropped') {
    return { command: drop.command, droppedResumeArgv: true }
  }
  if (drop.status === 'unrecognized' && args.claimedCodexProvenance) {
    throw new Error(UNVERIFIED_CODEX_RESUME_ERROR)
  }
  return { command: args.command, droppedResumeArgv: false }
}

View on GitHub (pinned to 1136503c6a)

Solutions

Update dropAgentResumeArgvFromCommand to recognize the new codex resume flag syntax.
If the account is correct and you want to proceed, ensure the resume argv is in a recognized form (direct codex invocation, not wrapped).
Launch a fresh session instead of resuming to avoid the account-crossing risk.
Verify providerSession and claimedCodexProvenance are set correctly — if the session isn't actually a codex rollout, provenance should be false.
Check the agent-resume-argv-drop shared helper against the current codex CLI argv grammar.

Defensive patterns

Strategy: validation

Validate before calling

// Before launching, confirm the resume argv is recognizable so launch doesn't abort:
const drop = dropAgentResumeArgvFromCommand({ command, agent: 'codex', providerSession })
if (drop.status === 'unrecognized' && claimedCodexProvenance) {
  // choose: launch fresh (drop command) or fix the argv grammar; do not call dropUnverifiedCodexResumeArgv expecting success
}

Try / catch

try {
  const { command: safe } = dropUnverifiedCodexResumeArgv(args)
  launch(safe)
} catch (error) {
  if (error instanceof Error && error.message === UNVERIFIED_CODEX_RESUME_ERROR) {
    // do NOT launch; surface to user that resume was blocked for account safety
    // offer a fresh session instead
  } else throw error
}

Prevention

Keep dropAgentResumeArgvFromCommand's codex argv grammar current with the codex CLI release.
Launch direct codex commands (not wrapped in shell pipelines) so the resume flag is strippable.
Set claimedCodexProvenance accurately — false for non-rollout sessions avoids the throw.
Prefer starting a fresh session over forcing an unverified resume.

When it happens

Trigger: The resume command's argv structure doesn't match any pattern dropAgentResumeArgvFromCommand knows for codex (e.g., --resume, -c continued-session); providerSession is set and claimedCodexProvenance is true but the resume flag is in an unexpected position/form; a codex CLI change altered the resume flag syntax.

Common situations: Codex changed its resume flag syntax in a new release so the drop pattern no longer matches; a custom alias/wrapper rewrites the codex command into an unrecognizable form; the session metadata says codex but the command is a shell pipeline.

Related errors

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