Claude Remote Launcher
superbereza/claude-remote-launcher
Lança sessões Claude Remote Control em tmux com URL de acesso
Ver no GitHubSkill que spawna sessões de Claude Code Remote Control em panes tmux detachados, gerando URLs para acesso remoto. Permite iniciar novas sessões Claude a partir de agentes ou CLI sem interromper a sessão atual.
Instalação
npx convez-ai superbereza/claude-remote-launcher1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Agents iniciarem sessões Claude Code em novos projetos automaticamente
- Desenvolvedores gerenciarem múltiplas sessões Claude de um terminal único
- Sharing de sessões Claude em projetos via URL de remote-control
Veredito

Ferramenta prática para orquestração de sessões Claude via terminal. Funciona bem em pipelines de agentes, mas depende de tmux e convenções de projeto — nicho bem definido.
README
A tradução para o português deste README ainda está na fila.
claude-remote-launcher
A tiny skill + CLI that spawns a Claude Code Remote Control session in a detached tmux pane. By default it just confirms the session started (the remote chat appears on your device); pass --url to also print the claude.ai/code link.
Designed so an agent (or you) can launch fresh Claude sessions in existing or brand-new project folders without leaving the current session. The skill is wired up for Claude Code, Cursor, Codex and Gemini from one source (see Install).
Install
Install the skill via the plugin (option 1 or 2); add the standalone shell CLI (option 3) if you also want to run claude-remote by hand.
1. As a Claude Code plugin (this repo is its own marketplace)
/plugin marketplace add superbereza/claude-remote-launcher
/plugin install claude-remote@claude-remote-launcher
2. From an aggregate marketplace
/plugin marketplace add superbereza/superbereza-skills
/plugin install claude-remote@superbereza-skills
3. The claude-remote CLI on your own shell (optional)
git clone https://github.com/superbereza/claude-remote-launcher ~/dev/claude-remote-launcher
cd ~/dev/claude-remote-launcher
./scripts/install.sh # symlinks ~/.local/bin/claude-remote → bin/claude-remote (~/.local/bin must be on PATH)
For running claude-remote by hand (incl. on a remote server). The skill comes from the plugin (option 1/2), so scripts/install.sh only puts the CLI on PATH — it doesn't symlink the skill.
Other agents
The same skills/ directory is exposed to Cursor (.cursor-plugin/), Codex (.codex-plugin/) and Gemini (gemini-extension.json → AGENTS.md). One skill, one source — see AGENTS.md.
Usage
# Existing folder — chat title defaults to the folder name
claude-remote ~/dev/myproject
# New folder (auto-created and pre-trusted)
claude-remote ~/dev/scratch-experiment
# Custom session name (= the remote-control chat title, used verbatim)
claude-remote ~/dev/myproject debug-auth
# Also print the claude.ai/code URL
claude-remote ~/dev/myproject --url
Default output (status only):
SESSION: cc—myproject
STATUS: remote-control active
ATTACH: tmux attach -t 'cc—myproject'
With --url the STATUS line becomes URL: https://claude.ai/code/.... Exit code is 1 if the remote-control URL doesn't appear within 30s.
Subcommands
| Command | Action |
|---|---|
claude-remote <path> [name] [--url] | Spawn (default; same as spawn) |
claude-remote spawn <path> [name] [--url] | Spawn, explicit |
claude-remote ls | List running cc— tmux sessions |
claude-remote kill <session> | Kill one |
claude-remote kill --all | Kill all cc— sessions |
claude-remote refresh <session> | Re-issue /remote-control inside an existing pane → fresh URL, same chat |
claude-remote --version | Print version |
The session name is the remote-control chat title, used verbatim — nothing is
prepended automatically, so include a device/ prefix yourself if you use that
convention (e.g. claude-remote ~/dev/x "mac-mini/x").
Disconnecting from claude.ai/code only drops the remote view; the local claude process keeps running until you kill the tmux session. The trust entry written to ~/.claude.json is left in place after killing sessions, so re-launching in the same folder is fast.
How it works
- Resolves the absolute path and detects whether the folder is new.
- Creates the folder with
mkdir -pif missing. - Pre-trusts the folder by atomically writing
hasTrustDialogAccepted: trueinto~/.claude.jsonunder the project entry. - Starts a detached tmux session in the folder.
- Runs
claude --dangerously-skip-permissionsinside the pane (interactive TUI). - Waits for
bypass permissions on(bottom-bar indicator) — the TUI is ready. Trust dialog is skipped thanks to step 3. - Sends
/remote-control <name>slash command to enable Remote Control (name defaults to the folder). - Polls
tmux capture-pane(with-Jto join wrapped lines) forhttps://claude.ai/code/...(timeout 30 s) to confirm it came up. - Prints the status (or the URL with
--url). Tmux session keeps running after the script exits.
Why slash command, not server mode
claude remote-control (server mode) bundles all sessions inside a single process — when the server's OAuth token rotates (~24 h), the daemon dies and takes every session with it (see #53635, #53563).
The slash-command approach this script uses keeps the conversation as a plain Claude session backed by <uuid>.jsonl. If Remote Control drops, run claude-remote refresh <session> to re-issue /remote-control inside the existing tmux pane — fresh URL, history preserved. If the claude process itself dies, you can claude --resume <uuid> --dangerously-skip-permissions and /remote-control again.
Requirements
claude≥ 2.1.51 (Remote Control support), logged in with a Claude subscriptiontmuxpython3(used for absolute-path resolution and atomic JSON edits)
Uninstall
./scripts/uninstall.sh
Removes the ~/.local/bin/claude-remote symlink. Repo and ~/.claude.json are not touched.
OpenCode
This skill also supports OpenCode — see .opencode/INSTALL.md.