spawn-session

Spawn Session

Launch a background Claude Code session in its own git worktree, subscribe to its idle notice, and relay the report through /claude-code-hermit:watch.

Usage

/claude-code-hermit:spawn-session <prompt-or-/skill> [--name <n>] [--model <m>] [--effort <e>]

From <abs>, the project root, that composes:

claude --bg --worktree <n> --name <n> [--permission-mode <p>] [--remote-control <n>] [--model <m>] [--effort <e>] '<prompt>'

--remote-control <n> is present when config.json's remote is true and absent otherwise; --model and --effort only when the operator passed them. Four limits sit on that command:

• The helper's worktree .claude-code-hermit/ is a projection (OPERATOR.md, config.json, compiled/ only). Any file the helper must Read is passed as an absolute path in the prompt.
• A worktree carries no .claude/settings.local.json (it is gitignored, so nothing checks it out), so the helper inherits none of this hermit's permission rules. --permission-mode <p> from config.json's permission_mode is what keeps it in this session's permission class, which is also what lets its idle notice reach here rather than being held for an operator who is not watching. config.json accepts one value the CLI has no choice for, default, so it and null and an absent key all mean: leave the flag off entirely and let the helper take the box default. scripts/hermit-start.ts resolves the same value the same way; match it rather than inventing a second answer. Every other value passes through unchanged, bypassPermissions included.
• The prompt is one single-quoted argument. An apostrophe in it ends the quote, so replace every ' with '\'' before composing. Anything after the closing quote is a second command the operator never asked for.
• The launch is not pre-approved, and what the operator sees depends on the mode they run in. On auto, the shipped default, the classifier decides and no prompt reaches them on any channel. On acceptEdits or manual the native approval is relayed to their DM and is allow-once, so every spawn asks again. On bypassPermissions there is none. Say what is about to be spawned before running it either way: it is the only thing that makes the launch legible when an approval does arrive, and the only record when none does.