Patterns for running long-lived processes in tmux. Use when starting dev servers, watchers, tilt, or any process expected to outlive the conversation.
94
Quality
95%
Does it follow best practices?
Impact
90%
1.52xAverage score across 3 eval scenarios
Passed
No known issues
Multi-process tmux session management
send-keys pattern
0%
100%
Session name from project
0%
100%
Single session, multiple windows
0%
100%
Idempotent session guard
0%
100%
Idempotent window guard
0%
100%
All three processes covered
100%
100%
No inline command in new-session
0%
100%
Correct send-keys syntax
0%
100%
Status output
100%
100%
No tmux kill-server
100%
100%
Without context: $0.1428 · 30s · 10 turns · 15 in / 1,684 out tokens
With context: $0.2417 · 40s · 14 turns · 19 in / 2,036 out tokens
Output monitoring and readiness polling
capture-pane for output
100%
100%
capture-pane -S flag
100%
100%
rg for ready check
0%
0%
rg for error check
0%
0%
Polling loop
100%
100%
Session name from project
100%
100%
Timeout handling
100%
100%
Targets specific window
0%
100%
Case-insensitive rg flags
0%
0%
No tmux kill-server
100%
100%
Without context: $0.1899 · 45s · 14 turns · 20 in / 2,474 out tokens
With context: $0.2249 · 53s · 12 turns · 16 in / 2,723 out tokens
Safe process restart and teardown
Restart via Ctrl+C
100%
100%
Re-sends command after stop
100%
100%
kill-window for selective stop
0%
100%
No kill-server
100%
100%
Session name from project
100%
100%
No kill of other sessions
100%
100%
send-keys pattern maintained
100%
100%
Session existence check
100%
100%
Correct send-keys Enter
100%
100%
Status messages
100%
100%
Without context: $0.2760 · 1m 3s · 20 turns · 26 in / 3,531 out tokens
With context: $0.2102 · 39s · 13 turns · 265 in / 2,148 out tokens
5342bca
Table of Contents
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.