vspawn

# /vspawn The user **explicitly invoked `/vspawn` (Claude) or `$vspawn` (Codex)** to request spawning a **standalone child session** under the current **vlx-term** session, passing the task in as its first message. The new child session runs as a **brand-new claude/codex process**, and **by default runs in the current directory without a worktree** (to open a dedicated git worktree for the child task, use `/vspawn-tree`, or add `--worktree` to this command). > ⚠️ This is **not** an in-process sub-agent, and **not** a background Task: it is a real, visible, interactive, > resumable session tab in the vlx-term left-panel tree, run by its own process, leaving the current session > undisturbed. User input: $ARGUMENTS ## Planning and execution mode When the user requests this workflow or supplies `--plan-execute`, keep the current session as the initiator. Pass the expanded task to `vspawn --plan-execute`; VelaTerm creates a new planner/reviewer, which later dispatches work to its own persistent executor. Add `--split-tasks` when the user requests automatic decomposition into multiple tasks. The new planner then proposes the split for a separate user review; do not split or execute the task in the initiating conversation. Do not perform the planning or execution here, and do not use in-process subagents. For a skill invocation that uses both `--plan-execute` and `--split-tasks`, **automatically add `--yes`** unless the user explicitly requests the initial configuration dial...