{"version":"2.1.317","anchor":"hooks-directory-refusal-message-now-mentions-windows-junctio","canonical_anchor":"hooks-directory-refusal-message-now-mentions-windows-junctio","heading":"Hooks folder error now mentions Windows junctions as well as symlinks","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/hooks-directory-refusal-message-now-mentions-windows-junctio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Hooks folder error now mentions Windows junctions as well as symlinks\n\nThe error for a hooks folder that is a link now says it may be a symlink or a Windows junction\n\n**Unclear.** It is not clear whether Windows junctions were refused before this release or whether only the error text changed.\n\n**What**\n\nHooks are your own commands that Claude Code runs at set moments. If the folder holding them is a link to somewhere else, Claude Code does not read it. The error used to say the folder was a symlink. It now reads: \"The hooks directory is a link (a symlink or a Windows junction) and was not read\". A symlink and a Windows junction are both ways of making a folder point at another location.\n\n**Why**\n\nOn Windows, a folder made with a junction is now described accurately, so you know why your hooks were skipped.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}