{"version":"2.1.281","anchor":"plugin-dir-log-explains-plugin-vs-folder-of-plugins","canonical_anchor":"plugin-dir-log-explains-plugin-vs-folder-of-plugins","heading":"--plugin-dir log explains plugin vs folder-of-plugins","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/plugin-dir-log-explains-plugin-vs-folder-of-plugins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### --plugin-dir log explains plugin vs folder-of-plugins\n\nThe `--plugin-dir` debug log now explains whether a folder was read as one plugin or a folder of plugins\n\n**What**\n\n`--plugin-dir` accepts either a single plugin or a folder holding several plugins. Its debug message, the detailed log you can turn on, now says what marks a folder as a single plugin. When a folder has nothing at its top marking it as one plugin, the message says so. It also says when a marketplace root was loaded as a folder of plugins.\n\n**Why**\n\nIf a plugin does not load the way you expected, the log tells you how Claude Code read the folder and why."}