Repository navigation
Answers sent with a typed prompt stay delivered when that prompt is blocked #4
Description
Commit: 1a8ec71 (0.1.4)
If the user types a prompt while answers are pending, the prompt.submit handler marks those answers delivered and only then calls next() (register.tsx L425-L443). If a handler further down drops or blocks that prompt (for example an organization's UserPromptSubmit hook), the answers stay delivered and never reach Claude. Nothing gives them back.
The mod's own send path already handles this: it calls undelivered() when its submitted prompt is refused (L996-L1006). The typed-prompt path has no matching step.
Possible fix: await next(...). If the result drops the prompt, or the call throws, call undelivered($, ids) before returning.
Found in an AI-assisted code review of this commit. The reviewer reproduced it against a mocked host, and the code path was then checked by hand.
Activity
tzafrir commentedon Oct 18, 2026
Good catch, thanks. Answers riding a prompt are now claimed before the prompt goes on, and given back if it doesn't reach Claude with them: a hook beneath drops it, takes the answers out, or the call fails. They then go with the next prompt or Send now, and a toast says so where the engine doesn't already show why. Fixed in #5.
Generated by Claude Code