Settings

Open Settings to configure how spwn finds Claude, where sessions keep their files, and how it updates.

Claude CLI path

spwn uses your own authenticated claude command. It auto-detects it in the usual locations and shows the path it found. If your claude lives somewhere unusual, set the Claude CLI path here to point spwn at it.

Because spwn uses your existing Claude login, there’s nothing else to sign in to — and nothing is re-uploaded or proxied. See How it works & your data for what spwn touches.

Session worktree location

Each Claude session in a git repo runs in its own worktree. Session worktree location controls where those worktrees are created. It applies to new sessions only — existing worktrees stay where they were created.

Option	Where worktrees go	Notes
Sibling (default)	A dot-prefixed folder beside the repo	Outside the working tree, so builds, file watchers, and IDE indexers never recurse into it.
Inside repo	<repo>/.spwn/worktrees/…	Excluded via the repo’s .git/info/exclude (your tracked .gitignore is untouched). Some tools with explicit include globs may still scan it.
App data	Under spwn’s app-data directory	Away from your repos entirely.

Global hooks

spwn’s shared hooks live in ~/.spwn/hooks/ and run for every session in every project. This is also where spwn’s own built-in behavior ships as default scripts — creating the session worktree, committing each turn, and taking checkpoints.

• Run shared global hooks — the toggle that enables or disables the whole ~/.spwn/hooks/ folder. Per-repo .spwn/hooks are unaffected.
• Open hooks folder — reveals ~/.spwn/hooks/ in Finder (creating it if needed), so you can read or edit the default scripts and add your own.

Disabling turns off worktree management

Because creating and removing session worktrees is one of those default global hooks, turning global hooks off means spwn no longer manages worktrees: new sessions run in the project folder with no isolated worktree or branch, existing session worktrees aren’t auto-removed on delete, and the per-turn commit + checkpoint stop. Leave it on unless you specifically want spwn to stop managing sessions’ git state.

Updates

spwn has a built-in updater. When a new release is available, an update banner appears — apply it and spwn relaunches on the new version. Updates it installs don’t trigger the macOS security prompt you see on a first download from GitHub (see Installation).

Staying available for scheduled tasks

Scheduled tasks only run while spwn is running, so spwn stays available in the menu bar when you close its window. Open it again from the menu-bar icon, or quit fully from that icon’s menu.