@@ -16,13 +16,20 @@ Audit the codebase against the project's core idea (the source of truth for desi
1616 4. Check `TODO.md` for known issues already tracked — don't duplicate them.
1717 5. Verify documentation matches the idea file.
1818
19-Use `bun run dev` and `tmux` via shell to run one-shot and interactive sessions manually. Analyse console output and UI from a user's perspective.
19+Use `bun run dev` and `tmux` via shell to run one-shot and interactive sessions manually. Analyse console output and UI from a user's perspective. Follow the **tmux send-keys rules** in Phase 2 whenever interacting with tmux.
2020
2121 ## Phase 2 — Multi-provider UI probe
2222
2323 Run `mc` sessions across all SDK paths to capture what real users see.
2424 Do NOT delegate analysis to the models under test.
25-Use `tmux` so you can test interactive sessions properly. Remember to send Enter to submit, and be careful with paste handling.
25+Use `tmux` so you can test interactive sessions properly.
26+
27+**tmux send-keys rules** (always follow these to avoid paste/input issues):
28+
29+- Always use `-l` when sending text: `tmux send-keys -t <session> -l 'your text here'`
30+- Send `Enter` as a **separate** call without `-l`: `tmux send-keys -t <session> Enter`
31+- 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`
2633
2734 ### Models to use (one per SDK path)