{"version":"2.1.289","anchor":"plugin-update-message-for-folder-sourced-plugins","canonical_anchor":"plugin-update-message-for-folder-sourced-plugins","heading":"Clearer handling of plugins loaded from a local folder","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/plugin-update-message-for-folder-sourced-plugins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### Clearer handling of plugins loaded from a local folder\n\nFolder-based plugins now get a note on update, extra lines in `\/reload-plugins` output, and file watching that follows the real path\n\n**Unclear.** The exact conditions under which the note appears are not settled.\n\n**What**\n\nA plugin can be loaded straight from a folder on your computer instead of being installed from a marketplace. Claude Code now handles these folder plugins more clearly.\n\n- Update note: updating a folder plugin that is already up to date now says there is nothing to update. It adds that edits there take effect at the next session start or `\/reload-plugins`.\n\n- Reload output: `\/reload-plugins` now adds lines listing the plugin folders it read.\n\n- Watching: the watchers that notice changes in a plugin folder now resolve the folder's real path before watching, following any links, and map changes back to the folder you gave.\n\n- Matching: plugin sources are compared in a normalised form, and the plugin state keeps a `folderReadAt` record.\n\n**Why**\n\nPlugin authors working from a local folder are told how to apply their edits and can see which folders a reload read. Changes inside linked folders should now be noticed.\n\n- Area: Plugins\n- Names: `\/reload-plugins`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}