The prompt hook never sees the prompt

In Cline CLI, a `UserPromptSubmit` hook never fires for the messages you actually send. In yolo mode it fires for Cline’s own text instead. Cline issue #14963 traces the cause. The CLI puts your message straight into the conversation and starts the run with an empty input, so it never emits the "message added" event that the prompt hook listens for.

The user-role messages that do emit that event are the runtime’s own reminders, such as "[SYSTEM] This run is not complete until you call one of these terminal completion tools". These carry no system marker, so they pass the hook’s filter. The audit logger uses the same filter, so `hooks.jsonl` records the reminder as a submitted prompt. A hook meant to audit or filter prompts sees none of the user’s prompts, and in yolo mode it logs text the user never wrote.

The report says the VS Code extension runs the hook from a different place and is not affected, and that Desktop shares the CLI’s code. The repro and the yolo-mode output are the reporter’s own, from Cline CLI 3.0.69.

Before you trust a prompt hook, send it a known prompt and check what it receives. A hook that never fires looks exactly like a hook that found nothing.