Submitted prompts can now be held, screened, rewritten or dropped

What

Claude Code has new code that can hold back a prompt after you submit it, screen it, and then let it through, rewrite it or drop it.

• A held prompt gets a "screened" verdict, which can drop it or rewrite it. The verdict is then applied to the held items. When no verdict is known, the result is marked noVerdict.
• The code handles interruptions while a prompt is held.
• The input path now passes along information about what happened to the prompt. It includes whether the prompt was forked, ranAs (the text actually run), withheld or passed, and isHeldForOrganization, which marks a prompt held for an organization. It also tracks when a hold was settled or handed on.
• userPromptHold and userPromptLine are passed into slash-command handling and into the ultraplan keyword path.

What decides whether this screening runs was not worked out.

Why

This appears to let an organization screen prompts, so what you type could be held, changed or not sent at all. If a prompt does not go through as you wrote it, this may be why.