paperclipai/paperclip · info

Reseed cancelled.

Error message

Reseed cancelled.

What it means

Informational warning from `paperclipai worktree reseed`: reseeding overwrites the target worktree's isolated Paperclip database, so it asks 'Overwrite the isolated Paperclip DB for X from Y using Z seed mode?'. If the user declines or cancels the p.confirm (and --yes was not passed), the command returns before seedWorktreeDatabase — the target DB is untouched.

Source

Thrown at cli/src/commands/worktree.ts:4320

  const targetPaths = resolveWorktreeReseedTargetPaths({
    configPath: targetEndpoint.configPath,
    rootPath: targetEndpoint.rootPath,
  });
  const runningTargetPid = resolveRunningEmbeddedPostgresPid(targetConfig);
  if (runningTargetPid && !opts.allowLiveTarget) {
    throw new Error(
      `Target worktree database appears to be running (pid ${runningTargetPid}). Stop Paperclip in ${targetEndpoint.rootPath} before reseeding, or re-run with --allow-live-target if you want to override this guard.`,
    );
  }

  const confirmed = opts.yes
    ? true
    : await p.confirm({
      message: `Overwrite the isolated Paperclip DB for ${targetEndpoint.label} from ${source.label} using ${seedMode} seed mode?`,
      initialValue: false,
    });
  if (p.isCancel(confirmed) || !confirmed) {
    p.log.warn("Reseed cancelled.");
    return;
  }

  if (runningTargetPid && opts.allowLiveTarget) {
    p.log.warning(`Proceeding even though the target embedded PostgreSQL appears to be running (pid ${runningTargetPid}).`);
  }

  const spinner = p.spinner();
  spinner.start(`Reseeding ${targetEndpoint.label} from ${source.label} (${seedMode})...`);
  const markers = resolveWorktreeSeedMarkerPaths(targetEndpoint.configPath);
  mkdirSync(path.dirname(markers.lock), { recursive: true });
  const releaseSeedLock = await acquireWorktreeSeedLock(markers.lock);
  try {
    let targetBackupSummary: string | null = null;
    if (opts.backupTarget) {
      targetBackupSummary = await backupWorktreeReseedTarget({ targetConfig, targetPaths });
      p.log.message(pc.dim(`Recoverable pre-repair backup: ${targetBackupSummary}`));
    }

View on GitHub (pinned to a7e689b3c3)

Solutions

  1. Re-run and confirm with 'y' if you want the reseed to proceed.
  2. Pass --yes for non-interactive runs (it skips the prompt entirely).
Defensive patterns

Strategy: validation

Prevention

When it happens

Trigger: Running `paperclipai worktree reseed` in a TTY without --yes, then answering 'N' or cancelling at the overwrite confirmation prompt.

Common situations: User backs out after seeing the seed-mode in the prompt; scripted invocation missing --yes.

Related errors


AI-assisted analysis of paperclipai/paperclip@a7e689b3c3 (2026-08-18). Data as JSON: /api/errors/8aaf51b689995555. Report an issue: GitHub.