What happened
After relocating a Prism project on disk, the langfuse hooks written into .claude/settings.json still point at the old absolute path. The PreToolUse hook (langfuse_session_init_hook.py) then fails on every tool invocation, which blocks the entire session (including the Skill tool, so /prism-feedback itself cannot run). Recovery requires editing settings.json from outside Claude Code.
Reproduction
prism new <project> (or prism init) in dir A.
- Move the project to dir B (e.g. reorganize into a subfolder).
- Start Claude Code in dir B. Every tool call fails with:
python3: can't open file '<dir A>/.claude/hooks/langfuse_session_init_hook.py'
Suggested fix
Write hook paths as ${CLAUDE_PROJECT_DIR}/.claude/hooks/... (or resolve relative to the project root at runtime) instead of hard-coding absolute paths at project creation time.
Environment
- ASTRA: 0.1.2
- Prism: 0.1.2.dev23+g2897ae8b9
- Python: 3.13.11
- OS: Linux 6.4.0-150600
What happened
After relocating a Prism project on disk, the langfuse hooks written into
.claude/settings.jsonstill point at the old absolute path. The PreToolUse hook (langfuse_session_init_hook.py) then fails on every tool invocation, which blocks the entire session (including the Skill tool, so/prism-feedbackitself cannot run). Recovery requires editingsettings.jsonfrom outside Claude Code.Reproduction
prism new <project>(orprism init) in dir A.python3: can't open file '<dir A>/.claude/hooks/langfuse_session_init_hook.py'Suggested fix
Write hook paths as
${CLAUDE_PROJECT_DIR}/.claude/hooks/...(or resolve relative to the project root at runtime) instead of hard-coding absolute paths at project creation time.Environment