{"version":"2.1.314","anchor":"organization-served-hooks-held-until-managed-settings-are-re","canonical_anchor":"organization-served-hooks-held-until-managed-settings-are-re","heading":"Hooks sent from another machine wait until your organization's settings are read","tier":"notice","area":"Hooks","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/organization-served-hooks-held-until-managed-settings-are-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Hooks sent from another machine wait until your organization's settings are read\n\nA hook sent from another machine is not run until this machine has read its organization's managed settings\n\n**Unclear.** It is unclear in which setups hooks are sent from another machine, so it is unclear who will see this.\n\n**What**\n\nA hook is a command that Claude Code runs automatically at set moments, for example just before it uses a tool. Managed settings are the rules an organization sets for every machine it manages.\n\nWhen another machine sends a person's hook, Claude Code no longer runs it straight away. It waits until this machine has read its organization's managed settings. Until then:\n\n- the tool call is reported as not run, because the organization's managed settings have not been read yet\n\n- a `PreToolUse` hook, which runs before a tool call, produces a permission \"ask\" instead, so you are asked to approve the tool call\n\n- in bypass mode, where approvals are normally skipped, the hook produces a decision that holds the call back instead of running\n\n**Why**\n\nThis stops a hook from slipping past the organization's policy while Claude Code is still starting up.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}