GitHub issue #15645 in cline/cline, opened 2026-11-10 by HansChundekad, records a report that in the interactive CLI with auto-approve all on (the default), a plugin beforeTool result of policy autoApprove false is ignored and the tool runs without a prompt, so a plugin cannot require user approval for a risky tool call while auto-approve all is on; with auto-approve all off, the same plugin does get a prompt, even for tools that are normally auto-approved; the report points to requestToolApproval in apps/cli/src/runtime/interactive/approvals.ts, where the auto-approve-all check returns before the request policy is read, and suggests skipping the shortcut when the policy is explicitly false, showing the prompt or denying when headless. Versions cited: Cline CLI 3.0.74 with @cline/core 0.2.0 on macOS arm64.
Verbatim Excerpts from Cited Records
“In the interactive CLI with auto-approve all on (the default), a plugin's `beforeTool` result `{ policy: { autoApprove: false } }` is ignored: the tool runs without a prompt.”
“A plugin can't require the user's approval for a risky tool call while auto-approve all is on.”
“An explicit `autoApprove: false` from a hook shows the approval prompt, even with auto-approve all on.”
“The tool call is approved without a prompt.”
Counter-record: Issue open as of the fetch; only 2 comments exist, so this is a thin thread. linear-code[bot] (2026-11-10) linked the report to CLINE-3769. Tidehyc (2026-11-13) independently reproduced the behavior on current main, confirming that with auto-approve all on the approval request returns approved without ever calling the approver, in both interactive and headless runs, while with auto-approve all off the approver is consulted as expected and headless denies; Tidehyc verified the plugin policy does reach the approval request, so requestToolApproval is the operative gate, and the root cause matches the report. Tidehyc also flagged a fix subtlety before implementing: approvals.test.ts currently asserts the present behavior for the stale required-approval case, and a naive shortcut skip would break it because per-tool defaults written by applyInteractiveAutoApproveOverride look the same as a hook-supplied policy at that point, so Tidehyc asked whether hook-supplied policies should be marked separately or the stale-toggle behavior changed, and asked for maintainer direction first. No maintainer reply and no fix appear in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #15645 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.