remote-tmux
v6.0.0`claude remote-control` toolkit: /remote-spawn launches independent Stints and manages peer-addressable sessions, with Claude app access on launches that register --remote-control
By Jongwon Choi10 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 16, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install remote-tmux for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install remote-tmux@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/jongwony/cc-pluginClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is remote-tmux/.
Plugin files
├── .claude-plugin/plugin.json└── skills/remote-spawn/SKILL.md
Included Skills1
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", "spin one up", "turn on remote-control in this directory", to spawn a Stint — a session that carries an independently managed bounded piece of work in its own context — or to list/message/retire those sessions. Current-task work whose result the caller integrates uses native subagents. Use it also whenever a message arrives from another Claude session, and whenever you are about to read the peer listing, address a peer, or judge whether one can be interrupted. It launches a backgrounded `claude` session addressable by `SendMessage` from other sessions and — on a launch that takes `--remote-control` — reachable from claude.ai/code and the mobile app as well. No script, no tmux. It carries the lifecycle of such a session up to the handshake, and the addressing, receiving, observing and retiring that apply to any session afterwards.
Plugin manifests1
{
"name": "remote-tmux",
"description": "`claude remote-control` toolkit: /remote-spawn launches independent Stints and manages peer-addressable sessions, with Claude app access on launches that register --remote-control",
"version": "6.0.0",
"author": {
"name": "Jongwon Choi",
"url": "https://github.com/jongwony"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[remote-tmux on Agent Plugins Marketplace](https://pluginsmp.com/plugins/remote-tmux)