paperclipai/paperclip · error
Local plugin path does not exist: ${absLocalPath}
Error message
Local plugin path does not exist: ${absLocalPath} What it means
Thrown during plugin install when localPath was provided: the resolved absolute directory does not exist on disk, so a local plugin install cannot proceed from that path.
Source
Thrown at server/src/services/plugin-loader.ts:1213
installOptions: PluginInstallOptions,
): Promise<DiscoveredPlugin> {
const { packageName, localPath, version, installDir } = installOptions;
if (!packageName && !localPath) {
throw new Error("Either packageName or localPath must be provided");
}
const targetInstallDir = installDir ?? localPluginDir;
// Step 1 & 2: Resolve and install package
let resolvedPackagePath: string;
let resolvedPackageName: string;
if (localPath) {
// Local path install — validate the directory exists
const absLocalPath = path.resolve(localPath);
if (!existsSync(absLocalPath)) {
throw new Error(`Local plugin path does not exist: ${absLocalPath}`);
}
resolvedPackagePath = absLocalPath;
const pkgJson = await readPackageJson(absLocalPath);
resolvedPackageName =
typeof pkgJson?.["name"] === "string"
? pkgJson["name"]
: path.basename(absLocalPath);
log.info(
{ localPath: absLocalPath, packageName: resolvedPackageName },
"plugin-loader: fetching plugin from local path",
);
} else {
// npm install
const spec = version ? `${packageName}@${version}` : packageName!;
log.info(
{ spec, installDir: targetInstallDir },View on GitHub (pinned to 120ae5428f)
Solutions
- Correct the localPath to an existing directory containing the plugin package; check for typos or an unmounted path.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at server/src/services/plugin-loader.ts:1213 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of paperclipai/paperclip@120ae5428f (2026-08-18).
Data as JSON: /api/errors/f16009ec47376de4.
Report an issue: GitHub.