OpenClaw Tmux Persistent Process
PassAudited by VirusTotal on May 11, 2026.
Overview
Type: OpenClaw Skill Name: openclaw-tmux-persistent-process Version: 1.0.0 The skill provides utility instructions and code snippets for using tmux to manage long-running background processes (e.g., dev servers, tunnels) that survive OpenClaw session cleanups. It uses a dedicated socket (/tmp/openclaw-tmux/openclaw.sock) to avoid conflicts and follows standard practices for process management without any signs of malicious intent, data exfiltration, or unauthorized persistence.
Findings (0)
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 server, tunnel, worker, or coding agent started this way may keep running after the original task or gateway session has ended.
The skill intentionally creates processes that continue after the normal OpenClaw command session ends. This is disclosed and central to the purpose, but users should notice the persistence.
Programs in tmux survive gateway restarts, exec cleanup, and session timeouts. tmux runs independently of OpenClaw
Use tmux persistence only for processes you intentionally want to keep alive, name sessions clearly, monitor them, and run the provided kill-session or kill-server cleanup commands when finished.
If an agent starts the wrong command in tmux, it may continue consuming resources, exposing a service, or changing state until stopped.
The skill documents running arbitrary shell commands inside persistent tmux sessions. This is expected for the stated purpose, but it can have lasting effects if used with the wrong command.
tmux -S "$SOCK" new -d -s "$SESSION" \
"cd /path/to/project && npm run dev"Review persistent command choices, especially tunnels and background workers, and prefer explicit user approval before starting long-running sessions.