{"version":"2.1.301","anchor":"org-hooks-claude-code-shell-prefix-and-inherited-env-now-co","canonical_anchor":"org-hooks-claude-code-shell-prefix-and-inherited-env-now-co","heading":"Simpler check for which hooks get the organization's shell prefix","tier":"internal","area":"Hooks","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/org-hooks-claude-code-shell-prefix-and-inherited-env-now-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Simpler check for which hooks get the organization's shell prefix\n\nWhether a hook counts as your organization's, and so gets CLAUDE_CODE_SHELL_PREFIX, no longer depends on the hook's type or its plugin\n\n**Unclear.** It is not clear what the new check tests, so it is not known which hooks now count as the organization's.\n\n**What**\n\nHooks are commands Claude Code runs automatically at set points. Claude Code uses a simpler check to decide whether a hook belongs to your organization. Hooks that pass get the organization's shell prefix from `CLAUDE_CODE_SHELL_PREFIX`, a command placed in front of every hook command, along with the organization's environment variables.\n\nThe check no longer looks at the kind of hook or at the plugin or skill it came from. Before, status line and file suggestion hooks were always left out. Claude Code can also now report when an organization hook starts without the environment variables a person's plugin set.\n\n**Why**\n\nThis can change which hooks run with your organization's shell prefix and environment.\n\n- Area: Hooks\n- Names: `CLAUDE_CODE_SHELL_PREFIX`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}