remote-spawn

name	remote-spawn
description	This skill should be used when the user asks to "spawn a remote-control session", "open this repo/folder in the Claude app", "remote control here", "띄워줘", "이 디렉터리에서 remote-control 켜줘", or to list/kill those sessions. It launches `claude --remote-control` in a chosen directory as a backgrounded tmux session (`rc-<name>`) reachable from claude.ai/code and the mobile app — no Telegram bridge.

Remote-Control Spawner

Spawn, list, and kill backgrounded claude --remote-control sessions — one per directory, each a tmux session rc-<name> reachable from the Claude app.

Run the script and report the result concisely:

# Spawn in a directory (name defaults to the dir's basename)
bash "${CLAUDE_PLUGIN_ROOT}/scripts/rc-spawn.sh" spawn <dir> [name]

# Spawn WITH an initial prompt — auto-submitted as the session's first message.
# To pass a prompt you must also pass a name (it is the 3rd positional arg). The
# prompt is passed to claude after a `--` separator (claude --remote-control ... -- "<prompt>").
bash "${CLAUDE_PLUGIN_ROOT}/scripts/rc-spawn.sh" spawn <dir> <name> "<prompt>"

# Resume a STOPPED session by id or name/search term (a live rc-<name> is reported, not clobbered).
bash "${CLAUDE_PLUGIN_ROOT}/scripts/rc-spawn.sh" resume <dir> <name> <session-id|search-term>

# List running sessions
bash "${CLAUDE_PLUGIN_ROOT}/scripts/rc-spawn.sh" list

# Kill one by name
bash "${CLAUDE_PLUGIN_ROOT}/scripts/rc-spawn.sh" kill <name>

• STARTED <name> → a remote-control session is now live in <dir> and appears in the Claude app. The accompanying SESSION <uuid> line is the new session's id (a lowercased UUID, passed to claude as --session-id). Relay the attach/kill hints from the output.
• RESUMED <name> → an existing session was relaunched; relay attach/kill hints as with STARTED.
• ALREADY-RUNNING <name> → a session for that name already exists (on resume: it's still live, so not relaunched).
• NOT-FOUND <name> → nothing matched on kill.

Notes to pass on when relevant:

• The session lives until its claude exits (no auto-restart by design).
• First launch in a directory Claude has never opened may show a one-time folder-trust prompt inside the tmux session — TMUX_TMPDIR=~/.tmux-sockets tmux attach -t rc-<name>, press Enter, then detach with Ctrl-b d. A queued initial prompt waits behind this trust gate and submits only after trust is confirmed.
• tmux is used (not nohup/launchd) so sessions work under TCC-protected dirs (~/Downloads, ~/Documents, ~/Desktop); kill SIGTERMs the session's own tmux pane process (not a global ps match) so SessionEnd hooks (e.g. anamnesis memory) flush before exit.