[Bug]: nix install + nah install / run claude results in broken hooks

[ryanswrt]

It seems like the .claude/setting.json hooks use the bare python interpreter without the package's site_packages to evaluate the nah_guard.py hook, which results in a ModuleNotFound error. I have a PR that ~ fixes it in ryanswrt#1 - I'm not super happy with the impl, it might be cleaner to just have the nah binary do the guard to reduce the number of entrypoints vs a seperate nah-hook script?

[manuelschipper]

Thanks for the report. I agree that long term having the hook call an installable executable is the cleaner solution going forward. Let me look into it.

[manuelschipper]

Fixed on main in f0ee4a9.

The hook path now calls the installed nah executable directly instead of relying on python -m nah or the old ~/.claude/hooks/nah_guard.py shim.

Concretely:

• nah install claude and nah run claude now install/use:
  .../bin/nah _claude-hook
• nah run codex now injects:
  .../bin/nah _codex-pre-tool-use
.../bin/nah _codex-permission-request
.../bin/nah _codex-post-tool-use
• nah update claude migrates existing direct Claude hooks from the old shim to the executable hook command.
• Existing already-running Claude/Codex sessions need to be restarted because they keep the hook command from launch time.

I verified this with a Nix-installed nah against real Claude Code and Codex in Docker, and also migrated a live VPS install from editable pip to Nix. The Nix-installed executable path works end to end for Claude direct hooks and Codex launch-time hooks.

Thanks again for the report. Your suggestion to have the nah binary handle the guard directly was the right direction, and I added Reported-by / Suggested-by attribution to the fix commit.

If you try it out, please feel free to let me know if you still hit issues, or if it works out okay on your setup.