{"version":"2.1.283","anchor":"plugin-errors-in-the-session-init-message-now-carry-a-path","canonical_anchor":"plugin-errors-in-the-session-init-message-now-carry-a-path","heading":"Plugin errors reported to SDK and IDE clients now include a file path","tier":"notice","area":"Agents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/plugin-errors-in-the-session-init-message-now-carry-a-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Plugin errors reported to SDK and IDE clients now include a file path\n\nPlugin errors in the session's startup message now carry a `path` field when Claude Code can work one out\n\n**What**\n\nWhen a session starts, Claude Code sends a startup message to the program driving it, such as an SDK client (code using the Claude Code programming library) or an editor integration. The list of plugin errors in that message now includes a `path` field when one can be worked out from the error. Before, each entry held only the plugin, the error type and the message.\n\n**Why**\n\nThose clients can now point you to the file that failed to load.\n\n- Area: Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}