You'll notice
The permission prompt for untrusted hooks in cloud sessions was reworded to be shorter and more actionable
What
When a cloud session hits a command check or hook that isn't defined in the user's own settings, and so can't be run automatically for that session, Claude Code shows a permission prompt asking for approval. That prompt's text has been rewritten to be shorter, and now tells the user how to make the check trusted going forward: by reviewing it and copying it into ~/.claude/settings.json.
Why
The clearer wording makes it easier to understand why the prompt is appearing and gives a concrete path to stop seeing it for that same check in the future.