{"version":"2.1.257","anchor":"plugin-loading-now-surfaces-the-specific-reason-a-path-escap","canonical_anchor":"plugin-loading-now-surfaces-the-specific-reason-a-path-escap","heading":"Plugin loading now surfaces the specific reason a path escapes the plugin\/marketplace boundary","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/plugin-loading-now-surfaces-the-specific-reason-a-path-escap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Plugin loading now surfaces the specific reason a path escapes the plugin\/marketplace boundary\n\nPlugin path-escape errors now say why, such as the real path a symlink resolves outside of.\n\nPath-traversal errors for plugin commands, agents, skills, monitors, and hooks now include a human-readable reason, such as an unresolvable boundary or the real path a symlink resolves outside of, rather than just reporting that the path escaped. This reason is attached to both the log line and the structured error object.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}