{"version":"2.1.318","anchor":"http-hook-lists-flaglists-and-organizationlists","canonical_anchor":"http-hook-lists-flaglists-and-organizationlists","heading":"Organization HTTP hook rules can apply on machines without a sign-in","tier":"notice","area":"Hooks","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/http-hook-lists-flaglists-and-organizationlists","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Organization HTTP hook rules can apply on machines without a sign-in\n\nThe organization's HTTP hook rules gain flag and organization lists plus a fallback, so a machine with no sign-in no longer always errors\n\n**What**\n\nA hook is a command or web request Claude Code runs automatically at set points; an HTTP hook sends a request to a web address. An organization can keep lists controlling these hooks. Before, a machine with no sign-in always stopped with an error saying it could not read the organization's HTTP hook lists. Now the part that applies those lists accepts a fallback, so such a machine can still run. The hook settings format also gains:\n\n- `flagLists`\n\n- `organizationLists`\n\n- `serverRefused`\n\n**Why**\n\nThis changes how an organization's hook rules are applied, notably on machines that are not signed in.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}