Skip to Content
Mind Palace 0.3.1-alpha is out. Check it out →
ReferenceError Reference

Error Reference

Mind Palace ecosystem components use standardized error codes for consistent error handling across CLI, extension, and MCP integrations.

Error Code Format

MP-{CATEGORY}{NUMBER}
  • MP: Mind Palace prefix
  • CATEGORY: Single letter (see below)
  • NUMBER: 3-digit code

Categories

CategoryLetterDescription
ConfigurationCConfig file errors
IndexIDatabase/indexing errors
SchemaSValidation errors
File SystemFFile access errors
MCPMProtocol errors
RuntimeRExecution errors

Error Reference

Configuration Errors (MP-Cxxx)

CodeMessageDescriptionResolution
MP-C001Config not found.palace/palace.jsonc missingRun palace init
MP-C002Invalid configConfig fails schema validationCheck schema errors in output
MP-C003Missing required fieldRequired field not presentAdd missing field to config
MP-C010Room not foundReferenced room doesn’t existCreate room or fix reference
MP-C011Playbook not foundReferenced playbook doesn’t existCreate playbook or fix reference
MP-C020Invalid neighbor configCorridor neighbor misconfiguredCheck URL/path and auth settings

Index Errors (MP-Ixxx)

CodeMessageDescriptionResolution
MP-I001Index not found.palace/index/palace.db missingRun palace scan
MP-I002Index staleFiles changed since last scanRun palace scan
MP-I003Index corruptedDatabase integrity check failedDelete .palace/index/ and rescan
MP-I010Scan failedError during indexingCheck file permissions
MP-I020FTS query errorInvalid search querySimplify query syntax

Schema Errors (MP-Sxxx)

CodeMessageDescriptionResolution
MP-S001Schema version mismatchArtifact version != CLI versionUpgrade CLI or regenerate artifacts
MP-S002Validation failedArtifact doesn’t match schemaFix artifact per error details
MP-S003Unknown schemaSchema not embedded in CLICheck artifact kind field
MP-S010Invalid JSONMalformed JSON/JSONCFix syntax error at reported location
MP-S011Invalid JSONCMalformed JSONC syntaxCheck for unclosed comments

File System Errors (MP-Fxxx)

CodeMessageDescriptionResolution
MP-F001File not foundReferenced file doesn’t existUpdate reference or create file
MP-F002Permission deniedCannot read/write fileCheck file permissions
MP-F003Path outside workspacePath escapes project rootUse relative paths within project
MP-F010Guardrail violationFile matches do-not-touch patternRemove from guardrails or skip file

MCP Errors (MP-Mxxx)

CodeMessageDescriptionResolution
MP-M001Server not runningpalace serve not startedStart MCP server
MP-M002Connection lostMCP connection droppedReconnect or restart server
MP-M003Request timeoutMCP request took too longCheck server status, retry
MP-M010Unknown toolTool name not recognizedCheck available tools
MP-M011Invalid argumentsTool arguments malformedCheck tool schema
MP-M020Protocol errorInvalid JSON-RPC messageCheck message format

Runtime Errors (MP-Rxxx)

CodeMessageDescriptionResolution
MP-R001Binary not foundpalace not in PATHInstall CLI or set path
MP-R002Version mismatchCLI/Extension incompatibleUpgrade to compatible versions
MP-R003Workspace not openNo workspace folderOpen a folder in VS Code
MP-R010Command failedCLI command returned errorCheck command output
MP-R020Git not availableGit commands failedInstall git or check PATH

Exit Codes

The CLI uses these exit codes:

CodeMeaning
0Success
1General error
2Configuration error
3Validation error
4Index error (stale/missing)
5File system error

Structured Error Output

When --json flag is used (where supported), errors are returned as:

{ "error": { "code": "MP-I002", "message": "Index stale", "details": { "staleFiles": ["src/main.ts", "src/utils.ts"], "lastScan": "2025-01-15T10:30:00Z" } } }

Extension Error Handling

The VS Code extension maps error codes to user-friendly notifications:

Error CodeNotification TypeAction Offered
MP-C001Warning”Run palace init” button
MP-I002Info”Heal” button
MP-R001Error”Configure path” link
MP-R002WarningVersion mismatch details
Last updated on