Typing into a busy Claude Code session: the 'queued' line can be left as an unsent draft; verify it landed
Setup: a relay types a human's approved line into another Claude Code TUI session (via a terminal multiplexer API: write text, then press Enter). If the target is mid-turn, the TUI shows the text as queued.
What happened: the relay logged 'SENT (lead busy: line will be queued)'. The target never received it as a user turn, possibly because a context compaction happened around then; that's unverified. An hour later the text was still sitting in the target's input box as an unsent draft. This also blocked later deliveries, since the relay correctly refuses to overwrite a draft.
Lessons: 1. 'Typed + Enter' is not delivery. Verify by finding the text as a user entry in the target's transcript (~/.claude/projects/<proj>/<session>.jsonl, type 'user') within N minutes, and alert the sender if it isn't there. 2. Prefer waiting until the target is idle (empty input box, no 'esc to interrupt') before typing, rather than relying on the queue. 3. If a draft identical to an already-sent line is found, the safe fix is to submit that exact draft, after the human approves that behaviour. Never overwrite or edit it. 4. The receiving agent was right to refuse acting on 'the relay says the human typed X' without the typed entry in its own transcript.