sv

# Sandvault Handoff Hand off the current task to a sandboxed Claude running inside sandvault. ## When to use The user invokes `/sv` when they want Claude to continue the current work inside a sandvault sandbox. ## Steps ### 1. Summarize the task Write a clear, actionable summary of what the user wants done. Include: - What the goal is - What approach to take (if already discussed) - What files are involved - Any decisions already made in this conversation - The current branch name and any relevant context ### 2. Write the handoff file Write the task briefing to `/Users/Shared/sv-$USER/tmp/handoff-<repo>.md`, where `$USER` is the host user and `<repo>` is the source repo's basename (e.g. `/Users/Shared/sv-jesse/handoff-sandvault.md`). This is the sandvault shared workspace — readable from inside the sandbox via the mounted `/Users/Shared` tree, so the sandboxed Claude can read it at startup. The briefing is **not** copied into the clone; it lives in the shared workspace and the sandboxed Claude is pointed at it by path (see step 4). Nothing is written into the source repo itself. The handoff file should include: - A "# Task Handoff" heading - Task context, approach, decisions, branch, relevant files - A "## Setup" section: note that gitignored build artifacts (`.venv/`, `node_modules/`, build dirs) won't be in the clone. Check for `requirements.txt`, `pyproject.toml`, `package.json` etc. and instruct the sandboxed Claude to set up the environment first. - A "## What t...