{"version":"2.1.317","anchor":"http-hook-logs-and-errors-omit-the-url-in-some-cases","canonical_anchor":"http-hook-logs-and-errors-omit-the-url-in-some-cases","heading":"HTTP hook logs and errors can leave out the request address","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/http-hook-logs-and-errors-omit-the-url-in-some-cases","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### HTTP hook logs and errors can leave out the request address\n\nIn some cases, logs for HTTP hooks no longer show the URL, and their errors say only that the request failed\n\n**Unclear.** It is not stated what condition decides when the address and error text are hidden.\n\n**What**\n\nHooks are commands or web requests that Claude Code runs automatically at set points. An HTTP hook sends a web request (a POST) to an address you set. Under a certain condition, two things now change:\n\n- The debug log line, from the detailed log Claude Code writes for troubleshooting, reads 'Hooks: HTTP hook POST' without the ' to ' part.\n\n- When the request fails, the error text is replaced with 'the request failed', plus an error code where there is one.\n\nWhen the condition does not hold, the address and the original error text still appear. Before this change, they always appeared.\n\n**Why**\n\nIn those cases, the hook's address and the raw error stay out of logs and error messages. That also leaves less detail to work from when a hook fails.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}