pastilhasandClaude Opus 5
8d94d08d19
The agent's input is a streaming iterable, and a message pushed onto it mid-turn is picked up at the next step boundary — the running turn reads it and carries on with the added context. Verified rather than assumed: a probe pushed a sentinel four seconds into a turn busy with `sleep` calls, and that turn's own final answer quoted the late instruction and obeyed it. One turn, one result, nothing interrupted. So the design this was heading for — stop the turn, then re-send the message wrapped in "please continue, but…" — is not needed. Nothing is abandoned mid-flight, no tool call dies half-applied, and the agent is never told to stop something it was part-way through. Enter on an empty composer delivers the queue now instead of waiting for the turn to end. That keystroke was free: handleSend has always returned immediately on empty input. The queue still fills and still shows as it did, so the default behaviour is unchanged — this is the impatient path, not a replacement. Officer needed nothing: handleChat already pushes onto the live session rather than opening a new one whenever `_claudeKill` is set, which is exactly the injection. The only thing in the way was the client's own refusal to send while generating. The affordance is stated above the queue because the keystroke is otherwise undiscoverable — Enter on an empty box has never done anything, so nobody would try it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>