{"version":"2.1.281","anchor":"plugins-pinned-to-a-directory-are-cloned-without-submodules","canonical_anchor":"plugins-pinned-to-a-directory-are-cloned-without-submodules","heading":"Plugins pinned to a directory are cloned without submodules","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/plugins-pinned-to-a-directory-are-cloned-without-submodules","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Plugins pinned to a directory are cloned without submodules\n\nPlugins with a directory pin are now cloned without fetching git submodules\n\n**Unclear.** The finding does not say how a plugin comes to have a `directoryPin`.\n\n**What**\n\nWhen Claude Code downloads a plugin with git and that plugin has a `directoryPin`, the clone now skips submodules. A submodule is a separate git repository nested inside another one. This applies to plugins from these sources:\n\n- `github`\n\n- `url`\n\n- `git-subdir`\n\nThe clone runs with `--no-recurse-submodules` and `-c submodule.recurse=false`, driven by a new `noSubmodules` option. The usage data recorded about each clone now also notes whether the plugin is a directory plugin, and the plugin loader is now given the git commit SHA recorded for it. A commit SHA is the unique ID of one saved version in a git repository.\n\n**Why**\n\nA pinned plugin no longer pulls in extra nested repositories during installation. If a plugin of this kind relied on its submodules being present, those files will not be downloaded."}