/sv skill: seamless task handoff to sandboxed Claude

[jesserobbins]

Summary

A Claude Code skill (/sv) that hands off the current task to a sandboxed Claude running inside sandvault. One command: clone the repo, generate a deploy key, pass the task context, open a new terminal, and Claude picks up where you left off.

How it works

1. User is working with Claude on a repo
2. Types /sv
3. Claude summarizes the task and writes $SHARED_WORKSPACE/handoff.md
4. sv-clone clones the repo with a deploy key, injects the handoff as CLAUDE.md
5. A new terminal window opens with a launch animation
6. Sandboxed Claude starts with full task context and push access

What's built (dev branch)

Branch: feature/ssh-deploy-keys-sv-clone (PR #134, builds on #133)

In sv-clone (PR #134):

• Auto deploy keys for any GitHub repo (no flags)
• Task handoff file injection ($SHARED_WORKSPACE/handoff.md -> CLAUDE.md in clone)
• Rsync error fix in guest/home/configure

In ~/.claude/skills/sv/ (local skill, not in repo):

• SKILL.md — skill definition for /sv slash command
• sv-vibes.sh — launch animation (starfield warp, SandVault chrome logo, Claude star entering vault, party mode, env info, random tips)
• Detects iTerm2 vs Terminal.app for window launch

Why

The sandvault user runs in isolation. That's the point. But switching context from "working with Claude" to "working with Claude in a sandbox" has friction: clone the repo, set up credentials, re-explain what you're doing. This eliminates all of it.

• Deploy key: scoped push to one repo, no host key sharing
• Handoff: task context transfers automatically
• Terminal: new window with animation, env info at a glance
• Zero flags, zero config

Status

Dev branch — depends on #133 (sv-clone standalone script). The /sv skill lives in user config, not the repo.

[jesserobbins]

@webcoyote okay I am lazy and having fun with this. Try it out!

[jesserobbins]

It mostly works!

[jesserobbins]

Okay this is awesome you should try it

[jesserobbins]

Status update — 2026-04-24

Shipped:

• Add per-repo SSH deploy keys to sv-clone #139 — sv-clone with auto deploy-keys for any GitHub repo (merged)
• Add /sv Claude Code skill for handing off tasks to sandvault #140 — /sv Claude Code skill (draft, open for review)

What changed since this issue was opened:

• Handoff mechanism pivoted. sv-clone no longer injects handoff.md as CLAUDE.md — that approach never worked for local-path clones (git clone --no-hardlinks doesn't copy untracked files). The skill now writes the briefing to /Users/Shared/sv-$USER/handoff-<repo>.md and passes the path to the sandboxed Claude as its first prompt via sv-clone <repo> -- claude -- "Read ... and continue.". No changes to sv-clone required.
• Skill lives in the repo now. sv build symlinks skills/sandvault/sv into ~/.claude/skills/sandvault/sv when Claude Code is present. Not just in user config.
• Animation dropped in Add /sv Claude Code skill for handing off tasks to sandvault #140 — @webcoyote flagged cosmetic bugs on [preview] Add /sv Claude Code skill for sandvault task handoff #136, and it's not load-bearing. Happy to restore it if you want the fun back (noted in Add /sv Claude Code skill for handing off tasks to sandvault #140).
• Namespaced under sandvault/ per @webcoyote's review on [preview] Add /sv Claude Code skill for sandvault task handoff #136 to avoid /sv skill-name collisions.
• Zero flags, zero config target still holds: /sv → new terminal → sandboxed Claude resumes the task.

Closing candidate once #140 lands.