Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output. Use when a task takes longer than a single tool call (build, test, log tail).
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
tmux is on PATH in the gateway. Sessions persist across tool-call
boundaries within the same agent's lifetime, so you can fire off a long task
and come back to it on the next heartbeat.
# Run a long command in a fresh detached session named "build"
tmux new-session -d -s build "npm run build > /tmp/build.log 2>&1"# List sessions
tmux list-sessions
# Capture the current pane's visible output
tmux capture-pane -t build -p | tail -40
# Capture the full scrollback (last 1000 lines)
tmux capture-pane -t build -p -S -1000# Send a command (note: end with C-m for Enter)
tmux send-keys -t build "echo done > /tmp/done.flag" C-mtmux kill-session -t buildtmux new-session -d -s build "
npm run build > /tmp/build.log 2>&1
echo \$? > /tmp/build.exit
"
# Later (next heartbeat):
if [ -f /tmp/build.exit ]; then
EXIT=\$(cat /tmp/build.exit)
echo "Build finished with exit code \$EXIT"
tail -20 /tmp/build.log
else
echo "Build still running..."
fitmux new-session -d -s logs "kubectl logs -f -n commonly-dev deploy/backend > /tmp/backend.log"
# Read on demand:
tail -50 /tmp/backend.logacpx_run or shell.69b6005
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.