Platform setup
Kact uses Accessibility to inject pointer events and inspect accessible UI elements. Run kact setup: it requests permission and opens System Settings → Privacy & Security → Accessibility when required. Grant the application that actually runs Kact: your terminal for development, or the installed binary for a login service. Then run kact setup again.
Accessibility and visual surfaces
Section titled “Accessibility and visual surfaces”Element navigation normally reads only macOS Accessibility metadata and never captures screen pixels. Interfaces with no usable accessibility controls fall back to grid navigation. navigation.elements.visual_fallback = true opts into Vision OCR and requires Screen Recording permission; see configuration for its behavior and privacy boundaries.
Native local and optional global keyboard bindings use the macOS event tap. If key capture is denied, grant Input Monitoring to Kact or the terminal that launched it.
Check configuration, Accessibility, and daemon availability without moving the cursor:
kact doctorLinux X11
Section titled “Linux X11”Install the X11 development headers to build Kact:
sudo apt-get install libx11-dev libxtst-dev
# Arch Linux and Omarchysudo pacman -S libx11 libxtstThe X11 backend needs a reachable DISPLAY and the XTest extension. It supports shell-driven movement, clicks, dragging, scrolling, and absolute movement. It does not provide overlays, accessibility-element discovery, built-in keyboard capture, or modified clicks.
Wayland is rejected when WAYLAND_DISPLAY is set. Use an X11 session for the native Linux backend.
For X11, set keybindings.navigation_enabled = false and let your window manager, compositor, or remapper invoke shell commands. Do not try to activate grid or element navigation: those need the macOS desktop backend.