{"version":"2.1.310","anchor":"org-level-hooks-warn-about-repository-settings-env","canonical_anchor":"org-level-hooks-warn-about-repository-settings-env","heading":"Organization hooks start without the repository's environment variables","tier":"internal","area":"Hooks","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/org-level-hooks-warn-about-repository-settings-env","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Organization hooks start without the repository's environment variables\n\nHooks set by your organization now start without the environment variables from a repository's settings, and a debug line says so\n\n**What**\n\nA hook is a command Claude Code runs automatically at a set moment, such as before a tool runs. When a hook comes from your organization rather than from a project, Claude Code now writes a debug line saying the hook starts without the environment variables set in the repository's settings file. Environment variables are named values passed to a program when it starts. A similar message already existed for plugin hooks.\n\n**Why**\n\nA repository's settings can be written by anyone who can change that repository. Keeping those values out of hooks your organization controls stops a repository from quietly changing how those hooks behave.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}