{"version":"2.1.282","anchor":"hooks-from-settings-now-carry-a-projectroot","canonical_anchor":"hooks-from-settings-now-carry-a-projectroot","heading":"Hooks from settings now pass their project folder along when they run","tier":"internal","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/hooks-from-settings-now-carry-a-projectroot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Hooks from settings now pass their project folder along when they run\n\nHooks defined in settings can now carry the project folder they belong to through to the moment they run\n\n**Unclear.** It is unclear where the project folder gets attached to a hook, or how running the hook uses it, for example whether it sets `CLAUDE_PROJECT_DIR`.\n\n**What**\n\nA hook is a command you configure Claude Code to run automatically at certain moments, for example before or after it uses a tool. When Claude Code gathers the hooks that apply to a moment, a hook from settings that records a project folder now keeps that folder with it until it runs. This applies only to hooks that do not already come from a plugin, a skill or another marked origin. Before, only plugin and skill information was carried along this way.\n\n**Why**\n\nIn practice, a hook declared in one project's settings may now run against that project rather than whatever folder the session happens to be in.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}