Wayland is a protocol for a compositor to talk to its clients as well as a C library implementation of that protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself.
Why this server?
Allows running and interacting with graphical programs in sealed Wayland sessions, including starting a headless Wayland compositor and using accessibility trees, screenshots, and input simulation.
Why this server?
Collects focus and idle events from the Wayland compositor to track active windows and user activity.
Why this server?
Provides tools for detecting the Wayland display protocol and desktop environment identifiers, as well as runtime configuration details for the desktop session.
Why this server?
Provides explicit support for Wayland display server with automatic detection and configuration of necessary environment variables
Why this server?
Enables AI-driven desktop automation for Wayland-based systems, including visual analysis through screenshots, absolute/relative mouse control, and keyboard input simulation.
Why this server?
Enables input injection and screen capture within Wayland-based GNOME sessions, bypassing protocol-level security restrictions through a dedicated shell extension.
Why this server?
Uses Wayland protocols for virtual input and screenshots, enabling native interaction with the Wayland desktop.
Why this server?
Backend for driving apps on Wayland compositors, providing headless display isolation, input, accessibility, and logs.
Why this server?
Offers screen capture capabilities on Wayland compositors using grim (wlroots screencopy protocol), supporting region, window, and fullscreen screenshots.