@@ -24,12 +24,14 @@ Run `mc` sessions across all SDK paths to capture what real users see.
2424 Do NOT delegate analysis to the models under test.
2525 Use `tmux` so you can test interactive sessions properly.
2626
27-**tmux send-keys rules** (always follow these to avoid paste/input issues):
27+**tmux rules** (always follow these):
2828
29+- **Session naming**: always prefix tmux session names with `mc-audit-` (e.g. `mc-audit-haiku`, `mc-audit-gemini`). Never use generic names like `audit`, `test`, or `s` — they may collide with the host tmux session and kill the running mc process.
2930 - Always use `-l` when sending text: `tmux send-keys -t <session> -l 'your text here'`
3031 - Send `Enter` as a **separate** call without `-l`: `tmux send-keys -t <session> Enter`
3132 - Never combine text and `Enter` in a single `send-keys` call — without `-l`, words like `Enter`, `Escape`, `Tab`, `Space` get interpreted as key presses instead of literal text.
32-- Pattern: `tmux send-keys -t s -l 'text'` then `tmux send-keys -t s Enter`
33+- Pattern: `tmux send-keys -t mc-audit-test -l 'text'` then `tmux send-keys -t mc-audit-test Enter`
34+- Before creating a session, never run `tmux kill-session` or `tmux kill-server` — just use unique names.
3335
3436 ### Models to use (one per SDK path)
3537