{"version":"2.1.317","anchor":"http-hooks-from-projectsettings-can-be-routed-through-a-diff","canonical_anchor":"http-hooks-from-projectsettings-can-be-routed-through-a-diff","heading":"HTTP hooks from project settings can be sent differently, and errors hide the URL","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/http-hooks-from-projectsettings-can-be-routed-through-a-diff","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### HTTP hooks from project settings can be sent differently, and errors hide the URL\n\nHTTP hooks defined in project settings may now go through a separate sender, and some failure messages say \"the hook's server\" instead of the URL\n\n**Unclear.** When project hooks take the separate path is not clear.\n\n**What**\n\nA hook is a command or request Claude Code runs automatically at certain moments. An HTTP hook sends a web request to an address you configure. For HTTP hooks that come from project settings, Claude Code can now send the request through a separate path instead of sending it directly.\n\nWhen such a request fails, the error message can now say \"the hook's server\" where it used to show the URL.\n\n**Why**\n\nHooks from project settings come with the project, and you may not have written them yourself. In practice, an error from one of these hooks may no longer tell you which address it was sent to.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}