dontAsk denials can note a tool could be approved, and are settled like background-agent denials

What

dontAsk is a permission mode in which Claude Code does not show permission prompts. Actions that would normally need your approval are refused instead. The way these refusals are recorded and followed up has changed:

• When a tool would have asked for permission in dontAsk mode, the refusal can now include an "ask" hint if the tool could have been approved. Before, it only recorded that the dontAsk mode caused the refusal.
• A step settles a question that was never put to you. It used to run only for refusals from background agents, which are agents working on their own without you watching. It now also runs for refusals caused by dontAsk mode.
• Sometimes a background agent's refusal overrides an approval from a hook. A hook is a script you configure that can approve or block actions. In that case the refusal now records hookAllowIgnored: true. That fact is passed to the settling step, together with whether the refusal came from a mode.

Why

A program hosting Claude Code gets more detail about an action refused in dontAsk mode, such as whether it could have been approved. That refusal now also goes through the step that settles the unasked question, where before this step was skipped for it.