GitHub issue #88747 in anthropics/claude-code, opened 2026-08-22 by DearMaestro, records a report that worktree creation writes an absolute core.hooksPath into config.worktree, causing hooks fired from a worktree to execute scripts from the main checkout on whatever branch it happens to be on; the report characterizes a weakened or removed hook step still passing as a silently removed safety net.
Verbatim Excerpts from Cited Records
“With `$0` absolute, `$s` is absolute too, so **every hook fired from the worktree executes the MAIN checkout's scripts — on whatever branch that checkout happens to be sitting on.**”
·
anthropics/claude-code (issue 88747 opening body, Consequence section)
·
2026-08-22T03:28:21Z
·GitHub Issue ↗
“**A PR that WEAKENS or REMOVES a hook step still runs the old, stronger hook** — so the push goes green on a change that disabled a gate.”
·
anthropics/claude-code (issue 88747 opening body, Consequence section)
·
2026-08-22T03:28:21Z
·GitHub Issue ↗
“Write nothing. Git already resolves a relative `core.hooksPath` per worktree, which is what the repo's shared config asks for. If a value must be written, write the **relative** one.”
·
anthropics/claude-code (issue 88747 opening body, Expected section)
·
2026-08-22T03:28:21Z
·GitHub Issue ↗
Counter-record: No in-thread refutation of the reported absolute-path behavior as of 2026-10-05: 18 comments discuss the worktree hooksPath issue. The report itself documents a workaround (per-worktree git config override) while warning it can disable hooks entirely on worktrees lacking their own husky shim.
Falsification probe: If issue #88747 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author/maintainers post a definitive retraction showing the reported config.worktree behavior was misattributed, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.