Patterns for running long-lived processes in tmux. Use when starting dev servers, watchers, tilt, or any process expected to outlive the conversation.
96
Quality
95%
Does it follow best practices?
Impact
100%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Session reuse and send-keys pattern
has-session check
100%
100%
No inline command
100%
100%
send-keys usage
100%
100%
Session name from git
53%
100%
Existing session handled
100%
100%
Session name is basename
100%
100%
stderr redirected on has-session
100%
100%
Status message
100%
100%
Without context: $0.2837 · 1m 17s · 15 turns · 19 in / 4,371 out tokens
With context: $0.3137 · 59s · 18 turns · 25 in / 2,695 out tokens
Multiple processes as windows in one session
Single session
100%
100%
Multiple named windows
100%
100%
Window existence check
100%
100%
send-keys for all commands
0%
100%
Session name from git
25%
100%
has-session before new-session
100%
100%
No parallel sessions
100%
100%
Idempotent design
80%
100%
Status output
100%
100%
Without context: $0.2440 · 1m 13s · 13 turns · 18 in / 4,081 out tokens
With context: $0.2416 · 44s · 15 turns · 20 in / 2,451 out tokens
Safe session teardown and isolation
No kill-server
100%
100%
Session name from git
53%
100%
Session verified before kill
100%
100%
kill-session targets only project
100%
100%
Graceful no-session handling
100%
100%
Session name printed
100%
100%
No kill-window on other sessions
100%
100%
stderr suppressed on has-session
100%
100%
Without context: $0.1247 · 33s · 11 turns · 18 in / 1,677 out tokens
With context: $0.3154 · 55s · 19 turns · 24 in / 2,810 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.