Problem
install.sh runs supermodel setup </dev/tty immediately after installing the binary. At that point the working directory is wherever the user ran the curl command — typically their home directory or a downloads folder, not their project.
Two consequences:
-
Hook installation targets the wrong directory: The setup wizard detects Claude Code and offers to install the PostToolUse hook. The hook is installed relative to the cwd, so it ends up in the wrong place (or the wizard skips it because there's no .claude dir there).
-
Watch starts in the wrong directory: After setup, shards.Watch is called with the install cwd. The user's actual project directory is never analysed.
Evidence
# User runs from ~
cd ~
curl -fsSL https://supermodeltools.com/install | sh
# wizard starts, hook installed in ~/.claude/settings.json ✓ (home dir, so ok)
# watch starts in ~ — analyses home directory, not the project
Fix
See #153 — remove wizard from install.sh entirely and let the user run supermodel inside their project. That's when the wizard runs in the right context.
Problem
install.shrunssupermodel setup </dev/ttyimmediately after installing the binary. At that point the working directory is wherever the user ran the curl command — typically their home directory or a downloads folder, not their project.Two consequences:
Hook installation targets the wrong directory: The setup wizard detects Claude Code and offers to install the
PostToolUsehook. The hook is installed relative to the cwd, so it ends up in the wrong place (or the wizard skips it because there's no.claudedir there).Watch starts in the wrong directory: After setup,
shards.Watchis called with the install cwd. The user's actual project directory is never analysed.Evidence
Fix
See #153 — remove wizard from
install.shentirely and let the user runsupermodelinside their project. That's when the wizard runs in the right context.