Yeachan-Heo/oh-my-codex · error · MissionCommandError

--continue-on-error is not supported for mission status.

Error message

--continue-on-error is not supported for mission status.

What it means

Thrown by parseMissionArgs when --continue-on-error is passed together with the status action, since status is read-only and never executes tasks.

Source

Thrown at src/cli/mission.ts:176

  let file: string | undefined;
  let dryRun = action === "plan";
  let continueOnError = false;
  let json = false;
  let slug: string | undefined;
  let summaryPath: string | undefined;
  let taskId: string | undefined;
  let markStatus: Extract<MissionTaskStatus, "blocked" | "needs-human-review"> | undefined;

  for (let index = 0; index < commandArgs.length; index += 1) {
    const arg = commandArgs[index] ?? "";
    if (arg === "--dry-run") {
      if (action !== "run") throw new MissionCommandError(`--dry-run is only supported for mission run/plan.`);
      dryRun = true;
      continue;
    }
    if (arg === "--continue-on-error") {
      if (action === "status") throw new MissionCommandError(`--continue-on-error is not supported for mission status.`);
      continueOnError = true;
      continue;
    }
    if (arg === "--json") {
      json = true;
      continue;
    }
    if (arg.startsWith("--summary=")) {
      summaryPath = arg.slice("--summary=".length);
      continue;
    }
    if (arg === "--summary") {
      summaryPath = readValue(commandArgs, index, arg);
      index += 1;
      continue;
    }
    if (arg.startsWith("--slug=")) {
      slug = arg.slice("--slug=".length);

View on GitHub (pinned to 3ad79a8a6f)

Solutions

1. Drop --continue-on-error from the status command
2. Use `mission run <file> --continue-on-error` when you actually want failure tolerance

Example fix

# before
mission status mission.md --continue-on-error
# after
mission status mission.md

const action = args[0];
if (args.includes('--continue-on-error') && action === 'status') {
  console.error('--continue-on-error not valid for status');
process.exit(2);
}

When it happens

Trigger: `mission status <file> --continue-on-error` — only the status action triggers it; run/resume/rerun accept the flag.

Common situations: Copy-pasting a full flag set from a run command into a status invocation; scripted wrappers passing the same flags to every subcommand.

Related errors

• --dry-run is only supported for mission run/plan.
• --task is only supported for mission mark/rerun.
• --status is only supported for mission mark.
• --keep-policy must be one of: score_improvement, pass_only
• Unknown capabilities subcommand: ${parsed.subcommand}

AI-assisted analysis of Yeachan-Heo/oh-my-codex@3ad79a8a6f (2026-08-27). Data as JSON: /api/errors/4102b3309a5e0f8a. Report an issue: GitHub.