Files
claude-code-system-prompts/system-prompts/data-sdk-system-init-plugin-errors-field.md
T
2026-11-13 12:17:31 -07:00

1.7 KiB

Plugin load-time errors. A plugin that did not load (an unmet dependency, a --plugin-dir entry that failed, a plugin enabled by managed settings that the loader could not load) is absent from plugins[]; a plugin that loaded without one of its components keeps its row and gets an entry here too. plugin is name@marketplace, or the positional inline[N] / synced[N] tag for a directory entry that failed before it had a name; type is a category from an open set (path-not-found, generic-error, manifest-validation-error, dependency-unsatisfied, hook-load-failed, …) — treat a value you do not recognize as a generic failure; message is display text; over a transport that may store its frames (a cloud worker or a self-hosted runner), an entry that is here only because managed settings enable the plugin carries one fixed sentence in its place, with no path or URL. The key is omitted when there are no errors; CI can fail on (plugin_errors?.length ?? 0) > 0. That check also trips on a machine that has no copy yet of a plugin enabled by managed settings, which is every run on a throwaway CI runner; CLAUDE_CODE_SYNC_PLUGIN_INSTALL=1 makes the first turn wait for the install. A Remote Control worker and the hosted worker always omit this key — plugin diagnostics stay in the local log there, so an omitted key does not assert a clean load.