claude-remote-control-serverlisted

# Claude Remote Control Server Manage long-lived `claude remote-control` server mode for repos. This is for user-dispatched work from claude.ai/code or the Claude app. It is separate from delegated prompted Claude runs, which use `claude-rc-spawn`. ## Install Or Update From the target repo, install or update its service: ```bash install-claude-rc-server-service.sh ``` Install another repo with explicit names: ```bash REPO_DIR="$HOME/work/myapp" \ SERVICE_NAME=claude-rc-myapp \ SESSION_NAME="myapp@$(hostname -s)" \ SESSION_PREFIX="$(hostname -s)-myapp" \ CAPACITY=8 \ install-claude-rc-server-service.sh ``` Defaults are derived from the repo directory name and the short hostname, so the explicit form above is only needed to override them. Use one user systemd service per repo, and pick distinct `SERVICE_NAME`, `SESSION_NAME`, and `SESSION_PREFIX` values so sessions are easy to identify in claude.ai/code. `DRY_RUN=1` prints the unit it would write to stdout and exits without touching disk or systemd — preview a config change, or diff it against the live unit: ```bash svc=claude-rc-skills # the service you are comparing against DRY_RUN=1 CAPACITY=12 SERVICE_NAME="$svc" install-claude-rc-server-service.sh \ | diff - <(systemctl --user cat "$svc.service" | tail -n +2) ``` `systemctl --user cat` prepends a `# /path` line, hence the `tail`. Pass the same overrides the service was installed with, or the diff reports those as changes. Validation still runs under `DRY_RUN