Unclear Which hook event accepts permissionDisplay and how the prompt uses it is not shown.
What
Hooks are your own scripts that Claude Code runs at set points. A hook can now include permissionDisplay in hookSpecificOutput, next to additionalContext, and Claude Code passes it along. It carries display details for a permission prompt, the question Claude Code asks before taking an action. Before, only additionalContext was taken from that part of a hook's output.
Why
Hooks get a way to shape what a permission prompt shows, not only what text the model sees.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up hookSpecificOutput, on Intercept and control agent behavior with hooks.
"hookSpecificOutput": {agent-sdk/hooks see the edit
Confirmed since
Anthropic's documentation has since written up additionalContext, on Explore the context window.
const takeaway = isCompacted ? 'Compaction replaces the conversation with a structured summary. System prompt, CLAUDE.md, memory, skill descriptions, and MCP tools reload automatically. Claude Code also re-reads up to five of the files mod…context-window see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which hook event accepts `permissionDisplay` and how the prompt uses it is not shown.
Anthropic's documentation agrees
Anthropic's documentation has since written up additionalContext, on Explore the context window.