Skip to content

Keep the local pointer on a headless screen with --show-local-pointer - #144

Open
Unayung wants to merge 1 commit into
omacom:mainfrom
Unayung:feat/show-local-pointer
Open

Unayung wants to merge 1 commit into
omacom:mainfrom
Unayung:feat/show-local-pointer

Conversation

@Unayung

@Unayung Unayung commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Fixes #126.

Problem

On a --headless session the client hides the local pointer (#38, background in #28), so the only visible pointer is the one Hyprland draws into the frames. Every move has to reach the server and come back through the encoder and decoder before it shows, which feels sluggish even on a LAN. Some people would rather see two pointers, as other remote desktop tools show them.

Fix

A new --show-local-pointer flag. With it, the two places that set the transparent cursor on a headless session leave the local pointer alone: the one on connect, and the fallback in set_remote_cursor when the server sends no visible cursor image. A visible remote cursor image still replaces the local pointer, as on a mirrored session. Without the flag nothing changes.

It is a flag rather than an environment variable or a config.toml key, as the issue suggests: config.toml is written by gliff and not meant to be edited, and the other display choices (--headless, --output) are flags too. The README mentions it next to the private screen.

Testing

scripts/check.sh passes. Not verified live: with client and server on one nested Hyprland, the server's virtual pointer and the local pointer are the same seat cursor, so the difference does not show. The reporter's patch in the issue makes the same change at the same two sites behind an environment variable, and they report it working on v0.4.2.

The change was written with Claude Opus 5.5.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UCs6nfZCNssaXtUYR7cpHg

A headless session hides the local pointer, so the only one left is the
remote pointer drawn into the frames, and every move waits for a round
trip through the encoder before it shows. --show-local-pointer keeps the
local pointer visible as well: it moves with no delay and the remote one
trails it. The default stays as it is.

Fixes omacom#126.

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] The PR appears safe to merge.

Summary

Adds --show-local-pointer so users can keep an immediate local pointer while a headless screen shows the remote pointer.

  • Headless screens can keep the local pointer visible.

No actionable issues found. Review was based on source inspection; live cursor behavior was not tested.

Reviews (1) · Last reviewed commit: "Keep the local pointer on a headless scr..." · 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.

Option to keep the local pointer visible on headless sessions

1 participant