Skip to content

Warn that unlocking a private screen unlocks the remote's monitors - #146

Open
Unayung wants to merge 1 commit into
omacom:mainfrom
Unayung:docs/headless-unlock-warning
Open

Unayung wants to merge 1 commit into
omacom:mainfrom
Unayung:docs/headless-unlock-warning

Conversation

@Unayung

@Unayung Unayung commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Part of #136.

Problem

The README calls --headless "a private remote screen". The headless output is one more output of the remote's Hyprland session, and the session lock covers every output. Unlocking through gliff therefore also unlocks the remote's physical monitors, and someone at the remote machine can see and use the desktop. Nothing in the docs says so.

Fix

Add a paragraph after the private-screen description. It says the private screen shares the remote's session and that unlocking through gliff unlocks the remote's own monitors too. It also says connecting can turn those monitors back on. This is the third option in #136.

Not in this PR

  • Keeping the physical outputs blanked and locked, and ignoring local input, while a headless session runs. That is the reporter's preferred behaviour. It needs a decision on how gliff should own DPMS and the session lock, and it touches the same area as Lock the remote's screen on request or when the connection ends #127.
  • A warning in the client.

Testing

Docs only. The paragraph goes after a blank line that follows the paragraph #144 edits, so the two PRs merge cleanly (checked with git merge-tree). The behaviour it describes is the one the reporter found with hyprctl -j monitors. I did not reproduce it on two machines.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UCs6nfZCNssaXtUYR7cpHg

A headless output is one more output of the remote's Hyprland session,
and the session lock covers all of them. Say so in the README, next to
the description of the private screen (omacom#136).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCs6nfZCNssaXtUYR7cpHg
@greptile-apps

greptile-apps Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] This documentation-only change appears safe to merge.

Summary

Adds a warning after the private-screen description in README.md.

  • The README warns that unlocking can expose the remote desktop.

No actionable issues found.

Unayung explicitly deferred keeping physical outputs blanked and locked, blocking local input, and adding a client warning. These need separate work.

Reviews (1) · Last reviewed commit: "Warn that unlocking a private screen unl..." · Reviewed by Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant