Invalid Paperclip config at ${configPath}: ${formatConfigVal

Error message

Invalid Paperclip config at ${configPath}: ${formatConfigValidationError(error)}

What it means

Schema failure in readConfigFile: the config JSON parsed but paperclipConfigSchema.parse rejected it, and the Zod issues are formatted as `path: message` pairs joined by '; '. Names exactly which config keys are invalid so the operator can correct them.

Source

Thrown at server/src/config-file.ts:42

  let raw: unknown;
  try {
    raw = JSON.parse(fs.readFileSync(configPath, "utf-8"));
  } catch (error) {
    const reason = error instanceof Error ? error.message : String(error);
    throw new Error(`Invalid Paperclip config at ${configPath}: failed to read or parse JSON: ${reason}`);
  }

  try {
    const config = paperclipConfigSchema.parse(raw);
    for (const warning of findPaperclipConfigKeyWarnings(config)) {
      console.warn(
        `Unknown config key ${warning.path}; did you mean ${warning.suggestion}? It will be preserved.`,
      );
    }
    return config;
  } catch (error) {
    if (error instanceof ZodError) {
      throw new Error(`Invalid Paperclip config at ${configPath}: ${formatConfigValidationError(error)}`);
    }

    throw error;
  }
}

View on GitHub (pinned to 120ae5428f)

Solutions

Correct the invalid fields listed by the validation error in the config file.

Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at server/src/config-file.ts:42 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/25b99efef61e16af. Report an issue: GitHub.