paperclipai/paperclip · error
Pass --from or --from-config/--from-instance explicitly so…
Error message
Pass --from <worktree> or --from-config/--from-instance explicitly so the reseed source is unambiguous.
What it means
Ambiguity guard in reseed source resolution: no --from worktree and no explicit config-source flag was given, and the default resolution was not unambiguous, so the command refuses to guess which instance to copy data from.
Solutions
- Pass --from <worktree> or --from-config/--from-instance explicitly to identify the reseed source.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at cli/src/commands/worktree.ts:883 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/530d982274d1f16d.
Report an issue: GitHub.
Appendix: source
Thrown at cli/src/commands/worktree.ts:899
return {
configPath: endpoint.configPath,
label: endpoint.label,
};
}
if (hasExplicitConfigSource) {
const configPath = resolveSourceConfigPath({
fromConfig: fromConfig ?? undefined,
fromDataDir: fromDataDir ?? undefined,
fromInstance: fromInstance ?? undefined,
});
return {
configPath,
label: configPath,
};
}
throw new Error(
"Pass --from <worktree> or --from-config/--from-instance explicitly so the reseed source is unambiguous.",
);
}
function resolveWorktreeRepairSource(input: WorktreeRepairOptions): ResolvedWorktreeReseedSource {
const fromConfig = nonEmpty(input.fromConfig);
const fromDataDir = nonEmpty(input.fromDataDir);
const fromInstance = nonEmpty(input.fromInstance) ?? "default";
const configPath = resolveSourceConfigPath({
fromConfig: fromConfig ?? undefined,
fromDataDir: fromDataDir ?? undefined,
fromInstance,
});
return {
configPath,
label: configPath,
};
}View on GitHub (pinned to 01ad858492)