linux-input-overlay-rust

Intercept Linux input events and render text overlays on X11 and Wayland.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/hafley66/claude-research --skill linux-input-overlay-rust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linux-input-overlay-rust
Source: https://github.com/hafley66/claude-research/tree/main/skills/linux-input-overlay-rust
Command: npx skills add https://github.com/hafley66/claude-research --skill linux-input-overlay-rust

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Intercept Linux input events, read on-screen text, and render overlays to annotate or augment the user interface across X11 and Wayland.

Core Features & Use Cases

  • Input interception via XRecord on X11 and evdev on Linux
  • Text extraction using AT-SPI and OCR tooling (Tesseract)
  • Overlay rendering in X11 and Wayland contexts with compositor considerations
  • Guidance for Rust implementations using rdev, enigo, and related crates

Quick Start

Trigger an input-hook workflow to capture keystrokes or focus events and render a live text overlay on the desktop.

Frequently Asked Questions about linux-input-overlay-rust

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I intercept Linux input events and render text overlays on the desktop?

You can intercept Linux input events and render desktop text overlays by using rdev to listen or grab inputs, extracting on-screen text via AT-SPI or Tesseract OCR, and drawing overlays with compositor considerations for X11 and Wayland.

Can I use Rust rdev to capture keystrokes across both X11 and Wayland?

Yes, Rust rdev can capture keystrokes across X11 and Wayland by utilizing XRecord on X11 and evdev on Linux, allowing you to trigger input-hook workflows that focus events for live text extraction.

What is the best way to extract on-screen text for Linux automation and accessibility?

The best way to extract on-screen text for Linux automation and accessibility is combining AT-SPI for direct text extraction and Tesseract OCR for visual elements, enabling accurate overlay rendering.

Does rendering overlays on Wayland require specific compositor permissions?

Rendering overlays on Wayland requires specific compositor considerations and permissions, because Wayland's security model restricts direct screen access unlike X11, necessitating compositor-specific protocols for overlay integration.

How does AT-SPI text extraction compare to Tesseract OCR for Linux input overlays?

AT-SPI extracts structured text directly from accessibility interfaces for precise input overlays, whereas Tesseract OCR processes screen pixels visually, making AT-SPI faster for native apps and OCR necessary for graphical environments lacking accessibility data.