- Shipped
- September 3, 2026 at 10:55 PM UTC
- Author
- Kamo
- Commit
- 5e040bf
Caught by running it on the machine: the terminal opened at the right path, with no command in it and no title. One race, both symptoms. `bootstrap` runs straight after a pty.fork that execs tmux, and the server takes a moment to come up and register its session. `send-keys` and `set-option` against a name tmux does not know yet fail from the far side of a subprocess, where nothing was looking — so a hand-off that had been prepared perfectly well simply never started. It now polls `has-session` until the session is really there, and refuses rather than typing into nothing if it never appears. The caller already prints that refusal into the terminal, so the member gets a usable shell and a reason instead of a shell that mysteriously did nothing. Three tests, including the one the fixtures could not previously express: with has-session failing the first few times, nothing is typed until it succeeds. 159 tests.