paperclipai/paperclip · error · Error
Use either --apply or --dry, not both.
Error message
Use either --apply or --dry, not both.
What it means
Mutually-exclusive mode guard in worktree merge-history: --apply (write changes) and --dry (preview only) name opposite execution modes and were both passed, so the command refuses to guess intent.
Solutions
- Pass either --apply or --dry, not both.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at cli/src/commands/worktree.ts:3292 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of paperclipai/paperclip@01ad858492 (2026-08-18).
Data as JSON: /api/errors/9b505fb755b71589.
Report an issue: GitHub.
Appendix: source
Thrown at cli/src/commands/worktree.ts:4107
return {
insertedProjects,
insertedProjectWorkspaces,
insertedIssues,
insertedComments,
insertedDocuments,
mergedDocuments,
insertedDocumentRevisions,
insertedAttachments,
skippedMissingAttachmentObjects,
insertedIssueIdentifiers,
};
});
}
export async function worktreeMergeHistoryCommand(sourceArg: string | undefined, opts: WorktreeMergeHistoryOptions): Promise<void> {
if (opts.apply && opts.dry) {
throw new Error("Use either --apply or --dry, not both.");
}
if (sourceArg && opts.from) {
throw new Error("Use either the positional source argument or --from, not both.");
}
const targetEndpoint = opts.to
? resolveWorktreeEndpointFromSelector(opts.to, { allowCurrent: true })
: resolveCurrentWorktreeEndpoint();
const sourceEndpoint = opts.from
? resolveWorktreeEndpointFromSelector(opts.from, { allowCurrent: true })
: sourceArg
? resolveWorktreeEndpointFromSelector(sourceArg, { allowCurrent: true })
: await promptForSourceEndpoint(targetEndpoint.rootPath);
if (path.resolve(sourceEndpoint.configPath) === path.resolve(targetEndpoint.configPath)) {
throw new Error("Source and target Paperclip configs are the same. Choose different --from/--to worktrees.");
}View on GitHub (pinned to 01ad858492)