{"version":"2.1.283","anchor":"sdk-init-plugin-errors-is-now-public-gains-path-and-do","canonical_anchor":"sdk-init-plugin-errors-is-now-public-gains-path-and-do","heading":"SDK startup info now says which plugin directory failed to load","tier":"notice","area":"Agents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/sdk-init-plugin-errors-is-now-public-gains-path-and-do","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### SDK startup info now says which plugin directory failed to load\n\nPlugin load errors that Claude Code reports to SDK programs are now documented and can give the path of the directory that failed\n\n**What**\n\nThe SDK (software development kit) lets other programs run Claude Code. When a session starts, Claude Code sends those programs a startup message. Its `plugin_errors` field lists plugins that had problems loading. That field used to be marked internal. It is now documented, and each entry can carry more detail:\n\n- `path`: the directory that did not load at all. It can come from `--plugin-dir`, from the SDK `plugins` option, or from a synced directory.\n\n- `plugin`: when `path` is present, this may be a position tag such as `inline[N]` or `synced[N]` instead of a plugin name.\n\nThe description also lists the kinds of error `type` that can appear, and says more may be added later.\n\nIt also covers plugins that load but are missing one of their parts. Such a plugin now keeps its row in the `plugins[]` list and still gets an error entry. Before, the description said affected plugins were left out of `plugins[]`.\n\n**Why**\n\nA program that loads several plugin directories can now tell exactly which one failed.\n\n- Area: Agents\n- Names: `plugin_errors`, `--plugin-dir`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}