OpenClaw Tmux Persistent Process

Run programs that survive OpenClaw exec session cleanup and gateway restarts via tmux. Use when you need long-running servers, dev servers, tunnels (ngrok/cl...

This skill is basically a how-to for running tmux-based persistent processes and is coherent with that goal. Before installing/use: 1) Ensure tmux 2.6+ is available (the registry metadata should list tmux as a required binary — consider updating that). 2) Prefer a per-user socket path (for example under /run/user/$UID or a directory you own) or make sure /tmp/openclaw-tmux is created with restrictive ownership/permissions to avoid local symlink/TOCTOU attacks; /tmp is world-writable and can be abused if other users exist. 3) Be aware that processes started in tmux will persist across gateway restarts and can expose network endpoints (ngrok/ssh tunnels) — only run commands you trust. 4) Avoid embedding long-lived secrets on command lines (they may be visible in process listings or shell history); instead inject secrets into session environments securely. 5) The skill’s examples assume binaries like ngrok, ssh, npm, node exist; install those separately as needed. If you need tighter security, require the skill metadata to declare tmux as a required binary and change the socket location to a per-user path.

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.