What probably matters to youSection of the release
What
Hooks modules (packages of automated scripts that run at certain points in Claude Code) can now declare a dependencies field in their manifest, saying which other hooks modules they depend on. Claude Code computes a load order from these dependencies so that a module loads after the modules it depends on, within the same tier. If two modules depend on each other in a cycle, Claude Code detects this, refuses to load them that way, and shows a warning.
Why
This lets hooks modules that build on each other load in a predictable, correct order, and prevents a circular dependency from causing undefined or broken behavior.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up dependencies, on Create and distribute a plugin marketplace.Claude Code copies each installed plugin into the local versioned plugin cache at `~/.claude/plugins/cache`, unless the plugin loads in place. A [`command` source in link mode](#copy-mode-and-link-mode) loads in place, and so does a [relat…plugin-marketplacessee the edit
Added sinceA small documentation edit on Configure cloud environments touched a line naming dependencies after this was published.* **No cloud-only scoping**: hooks run in both local and cloud sessions. To skip local execution, exit early unless the `CLAUDE_CODE_REMOTE` environment variable is `true`, the way the [dependency install script](#install-dependencies-with…cloud-environmentssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesA small documentation edit on Configure cloud environments touched a line naming dependencies after this was published.
