Refuse at the switch every signal the hold would have emptied

LNK commented

2026-09-04 21:12:30 +00:00

Contributor

The review's C2. On a desktop that cannot verify the indicator, the grant refused screenshots and typed text and then granted clipboard, commands and websites, whose every record the hold would suppress anyway: a switch that said on and delivered nothing.

What changes. All five content signals are refused at the switch on such a desktop, with the same sentence, so the console says "cannot run here" and why. Window activity stays granted, because its timing is most of what it is for, and is reported as reduced to timing. Typing rhythm is untouched. A Mac is unaffected; this is the Wayland-without-layer-shell case.

Proof. A desktop with every protocol but layer-shell refuses exactly the five, keeps window activity and typing rhythm, and reports window activity reduced; the test fails against the old two-signal list. Linux verifier green on the pinned toolchain.

The review's C2. On a desktop that cannot verify the indicator, the grant refused screenshots and typed text and then granted clipboard, commands and websites, whose every record the hold would suppress anyway: a switch that said on and delivered nothing. **What changes.** All five content signals are refused at the switch on such a desktop, with the same sentence, so the console says "cannot run here" and why. Window activity stays granted, because its timing is most of what it is for, and is reported as reduced to timing. Typing rhythm is untouched. A Mac is unaffected; this is the Wayland-without-layer-shell case. **Proof.** A desktop with every protocol but layer-shell refuses exactly the five, keeps window activity and typing rhythm, and reports window activity reduced; the test fails against the old two-signal list. Linux verifier green on the pinned toolchain.

LNK added 1 commit

2026-09-04 21:12:30 +00:00

Refuse at the switch every signal the hold would have emptied 14db3c07d0

A desktop that cannot confirm the indicator is visible cannot capture content: that is the
hold, and it is the right rule. But the grant only refused two signals on such a desktop —
screenshots and typed text — and granted clipboard, commands and websites, whose every
record is content. The gate then held each of their records, one by one, behind a switch
that said on. A grant that can never deliver is the failure `unavailable_signals` exists to
refuse, and it was refusing it for two signals out of five.

The five are refused together now, with the same sentence, so the switch does not turn on
and the console says why. Window activity is the one left out on purpose: its titles are
content and are held, its timing is not and is most of what the signal is for, so it stays
granted and `limitations` says what it loses — the same reduction a Mac without Screen
Recording reports, for a different cause. Counts are not content and are untouched.

A Mac is not affected: its window list gives the indicator's occlusion without a permission,
so it can always verify. This is the Wayland-without-layer-shell case, which is GNOME.

Tests: a desktop with every protocol but layer-shell refuses exactly the five content
signals, keeps window activity and typing rhythm, and reports window activity reduced. The
test fails against the two-signal list — checked, by putting it back.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

LNK merged commit 928b0841c3 into main

2026-09-04 21:12:30 +00:00

LNK referenced this pull request from a commit

2026-09-04 21:12:31 +00:00

Merge pull request #15 from claude/grant-equals-hold

Rows
Columns

Refuse at the switch every signal the hold would have emptied #15