paperclipai/paperclip · info

Import cancelled.

Error message

Import cancelled.

What it means

Informational warning from `paperclipai worktree import`: after collecting and displaying the merge plan, the apply step requires opts.apply plus a confirmation. When the user declines or cancels the p.confirm ('Import N issues and M comments from X into Y?'), the CLI returns before applyMergePlan — nothing was written to the target database.

Source

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

    console.log(renderMergePlan(collected.plan, {
      sourcePath: `${sourceEndpoint.label} (${sourceEndpoint.rootPath})`,
      targetPath: `${targetEndpoint.label} (${targetEndpoint.rootPath})`,
      unsupportedRunCount: collected.unsupportedRunCount,
    }));

    if (!opts.apply) {
      return;
    }

    const confirmed = opts.yes
      ? true
      : await p.confirm({
        message: `Import ${collected.plan.counts.issuesToInsert} issues and ${collected.plan.counts.commentsToInsert} comments from ${sourceEndpoint.label} into ${targetEndpoint.label}?`,
        initialValue: false,
      });
    if (p.isCancel(confirmed) || !confirmed) {
      p.log.warn("Import cancelled.");
      return;
    }

    const applied = await applyMergePlan({
      sourceStorages,
      targetStorage,
      targetDb: targetHandle.db,
      company,
      plan: collected.plan,
    });
    if (applied.skippedMissingAttachmentObjects > 0) {
      p.log.warn(
        `Skipped ${applied.skippedMissingAttachmentObjects} attachments whose source files were missing from storage.`,
      );
    }
    p.outro(
      pc.green(
        `Imported ${applied.insertedProjects} projects (${applied.insertedProjectWorkspaces} workspaces), ${applied.insertedIssues} issues, ${applied.insertedComments} comments, ${applied.insertedDocuments} documents (${applied.insertedDocumentRevisions} revisions, ${applied.mergedDocuments} merged), and ${applied.insertedAttachments} attachments into ${company.issuePrefix}.`,

View on GitHub (pinned to a7e689b3c3)

Solutions

  1. Re-run and confirm with 'y' to actually apply the plan.
  2. Add --yes to the command for non-interactive automation (it forces confirmed = true).
Defensive patterns

Strategy: validation

Prevention

When it happens

Trigger: Running worktree import with --apply in a TTY without --yes, then answering 'N' or cancelling (Ctrl-C/Escape) at the import confirmation prompt.

Common situations: Reviewing the plan counts and aborting; scripts that pass --apply but not --yes and hit the interactive prompt.

Related errors


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