spawn-session

Run tmux new-session with the -d flag for detachment, -c for the project directory, and launch via zsh -ic so the claude shell function loads with its channel flags. Pass a display name with the -n flag so the session is identifiable.

Call the claude-hive MCP list_peers tool with machine scope and match peers by their cwd, repo, or stable_id. If a peer already exists for the project, delegate to it with send_message instead of spawning a duplicate.

The CW_AGENT_NAME environment variable was not set at launch, so the workspace attributes comments generically. It must be passed via tmux -e at spawn time because the MCP child inherits the parent process environment and cannot be fixed afterward.

The spawned session inherited the team-lead's DISCORD_STATE_DIR, so every peer shares the same bot token and channel subscriptions. Pass a per-peer DISCORD_STATE_DIR via tmux -e, or use a shared no-discord state directory for peers without their own setup.

Claude Code may have failed to boot, often because zsh -c was used instead of zsh -ic so the claude function never loaded. Inspect the pane with tmux capture-pane and check for startup dialogs or missing channel flags in the process arguments.

Do not spawn when a peer for that project already exists in list_peers, or when the user has not explicitly requested a new session. Spawning is a visible side effect, so confirm with the user when in doubt.