Claude Code tmux Runner
PassAudited by ClawScan on May 10, 2026.
Overview
The skill’s stated purpose is coherent, but it relies on an external local script and can start persistent background Claude Code jobs, so users should verify the script before use.
Before installing or using this skill, inspect ~/.openclaw/scripts/claude-tmux.sh because it is not included in the reviewed package. Only approve background tasks you intend to run, monitor their status, and stop them when finished.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A task prompt may be passed into a shell command that starts a background process, so unexpected helper-script behavior could affect the local environment.
The skill is designed to run a local shell helper with user-provided task text. This is central to the purpose, but users should be aware it executes local commands.
tools: Bash, Read, Write ... ~/.openclaw/scripts/claude-tmux.sh start "Your task description" [task-name]
Approve each task before launch, keep task arguments properly quoted, and inspect the helper script before relying on it.
The safety of the main executable depends on a local script that was not included for review.
The supplied package does not include installation steps or the referenced ~/.openclaw/scripts/claude-tmux.sh implementation, so the actual script provenance is outside the reviewed artifacts.
No install spec — this is an instruction-only skill.
Verify the contents, source, and permissions of ~/.openclaw/scripts/claude-tmux.sh before running any task.
Claude Code tasks may continue running after the main chat returns, consuming resources or modifying generated files until stopped.
The skill intentionally starts long-running background Claude Code tasks. This is disclosed and includes stop commands, so it is a notice rather than a concern.
Run multiple Claude Code tasks in parallel using tmux sessions. Non-blocking, background execution with status monitoring.
Use the documented status and stop/stop-all commands to monitor and end background jobs when they are no longer needed.