Repository navigation
feat(computer): wait for a Hyprland session and list its windows through its IPC - #552
Merged
earakely-scale merged 1 commit intoNov 9, 2026
Conversation
…ugh its IPC A computer app's server waited for X's socket and listed windows with xprop, which on Hyprland sees only XWayland's: a native Wayland app's Ready(window=True) never held. On Hyprland, read from HYPRLAND_INSTANCE_SIGNATURE, the session is up once its Wayland display's socket and its IPC's are there, and its windows are its mapped clients as `hyprctl -j clients` lists them, native and XWayland alike: the class (a Wayland app ID, or an X window's WM_CLASS class), the title, and as the instance, which a Wayland window hasn't, the program's file name, as on Windows. A boot app waits for a Hyprland session as it waits for an X display, and hyprctl, like xprop, is killed when a listing is cut short. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/fd-5340-o3-wayland-in-the-protocol-a-hyprland
branch
November 9, 2026 05:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A computer app's own server waits for the desktop session before it launches the app, and decides
Ready(window=True)from the session's windows. Both were X11-only: it waited for X's socket and listed windows withxprop. On Hyprland,xpropsees only XWayland windows, so a native Wayland app's window readiness never held, and without XWayland the wait was skipped. This is the session-layer half of Omarchy computers' Wayland support; the probe's GTK fixture went in with #547.On Hyprland (
HYPRLAND_INSTANCE_SIGNATUREset), incomputer/_session_posix.py:The session is up once its Wayland display's socket (
$XDG_RUNTIME_DIR/$WAYLAND_DISPLAY) and its IPC's ($XDG_RUNTIME_DIR/hypr/<signature>/.socket.sock) are there.Its windows are its mapped clients as
hyprctl -j clientslists them, native Wayland and XWayland alike:class: a Wayland app ID, or an X window'sWM_CLASSclass;title;instance: a Wayland window has none, so this is its program's file name, as on Windows.A listing whose IPC doesn't answer is empty. Like
xprop,hyprctlis killed when a listing is cut short.A boot app waits for a Hyprland session as it waits for an X display (
app_runtime.start).X11, macOS and Windows are unchanged. Commands an app or driver runs already get the session's environment, because the driver's and apps' services run in the graphical session (their units restarting with it is the Omarchy base's job), so
run_in_sessionneeds no change.Docs:
Launch.window's comment and the protocol README's paragraphs on launch readiness and the session.Testing
xpropandhyprctl.ruff check .is clean.wait_until_upreturned with the session up.windows()listed a native Wayland GTK window (classFixtureDesk, instancepython3.14) and a Tk window under XWayland (classBenchlab, title "Bench Lab").Launch(command=["nautilus", ...], window={"class": "org.gnome.Nautilus"}, ready=Ready(window=True))answered not ready before its launch and ready after it.xpropshowed only the Tk window.Not in this PR
What the driver's skill tells an agent on Omarchy (tiling, workspaces, its menu on Super+K), and the recording frame rate under llvmpipe.
FD-5340 (under FD-5336)
🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge; no actionable issues were found.Summary
Adds Hyprland support to computer app startup and window readiness.
Acknowledged scope: earakely-scale assigns restarting services with the graphical session to the Omarchy base and explicitly intends program filenames for
instanceon Hyprland, including XWayland windows.Diagram
%%{init: {'theme': 'neutral'}}%% flowchart TD A[App server starts] --> B{Hyprland session?} B -->|Yes| C[Wait for Wayland and IPC sockets] B -->|No, X display set| D[Wait for X socket] C --> E[Launch boot app] D --> E E --> F[Check window readiness] F --> G{Hyprland session?} G -->|Yes| H[Read mapped clients with hyprctl] G -->|No| I[Read X windows with xprop] H --> J[Match class, instance and title] I --> JReviews (1) · Last reviewed commit: "feat(computer): wait for a Hyprland sess..." · Reviewed by Greptile