You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.282,
ImprovementsSection of the release
What
The prompt.fill hook call lets a plugin put text into the box where you type your message. When it could not do that, it used to return only isFilled: false. It now also returns a refusal value that says why:
"dialog": a dialog was open over the prompt, so nothing was filled.
"no_composer": there was no prompt box to fill.
Claude Code's debug log shows the same reason where it used to say only "not filled".
Why
Plugin authors can now tell a prompt blocked by an open dialog apart from other failures, which makes it easier to retry at the right moment or report a clear error.
