Investigation
What the press did. The mod ran the command with $.process.run, captured its output, redacted anything that looked like a secret, and called $.session.append with a message carrying the output. The call returned without error. The pane cleared the command. Then nothing.
What session.append is for. It adds a row to the transcript. The next time Claude is asked something, that row is in the context. It is the right tool for a note Claude should know about later. It is the wrong tool for a result Claude should act on now, because it starts no turn.
Why the tests could not say so. The test kit has no session.append. The mod’s own test for the hand-back asserted the message content, not that a turn followed. There was no way to assert that in the kit.
The first live press. The operator ran git stash drop through the pane. The command succeeded. Claude stayed silent. The operator typed again, and Claude’s reply showed it had read the output. Observed once; that was enough, because the mechanism explains it fully.
| Call | Starts a turn | Right for |
|---|---|---|
$.session.append |
no | a note for later |
$.prompt.submit |
yes | a result to act on now |
$.prompt.fill |
no, the operator sends | when submit is refused |