Problem
Bare tt wait (no --events) wakes only on a turn change and silently misses messages and events. In mined Claude production-coordination sessions this was the #1 footgun — tt wait --events was used 0 times; agents hand-rolled tt events --wait polling loops instead.
Proposed fix
Either:
- (a) emit a
next/warning when tt wait runs without --events: "bare wait wakes only on a turn change; use --events --after <cursor> to also receive messages and events", or
- (b) make
--events the default for tt wait (with --after defaulting to the current tail).
Touch-points
handleWaitCommand in src/cli/turn-commands.ts (~L42–85).
Context
Follow-up CT-G from the 0.8.0 instruction hardening; the skill now says "never bare tt wait". See docs/releases/0.8.0.md.
Problem
Bare
tt wait(no--events) wakes only on a turn change and silently misses messages and events. In mined Claude production-coordination sessions this was the #1 footgun —tt wait --eventswas used 0 times; agents hand-rolledtt events --waitpolling loops instead.Proposed fix
Either:
next/warning whentt waitruns without--events: "bare wait wakes only on a turn change; use--events --after <cursor>to also receive messages and events", or--eventsthe default fortt wait(with--afterdefaulting to the current tail).Touch-points
handleWaitCommandinsrc/cli/turn-commands.ts(~L42–85).Context
Follow-up CT-G from the 0.8.0 instruction hardening; the skill now says "never bare
tt wait". Seedocs/releases/0.8.0.md.