Skip to content

FAQ

Yes. macOS currently provides overlays, accessibility targeting, keyboard capture, modified clicks, and shell actions.

It supports shell-driven pointer actions in X11. It does not provide native X11 overlays, element discovery, keyboard capture, or modified clicks.

No. Wayland and Windows have no native Kact backend.

Yes. kact start runs a background local daemon. kact daemon keeps it in the foreground.

Yes. Enable custom bindings, or have an external shortcut tool call the CLI. Global Kact shortcuts are off by default.

What is the difference between move, move-to, and held movement?

Section titled “What is the difference between move, move-to, and held movement?”

move is an immediate relative adjustment. move-to is an immediate absolute placement. move-start and move-stop create continuous directional movement for integrations that have separate press and release events. Add --glide to move or move-to for an opt-in one-shot animation to a fixed target.

No. Plain move and move-to remain immediate. Glides are cancellable and never queue, so they are useful when a visible transition is wanted without changing automation behavior.

Run kact config path. By default it is ~/.config/kact/kact.toml unless XDG_CONFIG_HOME is set to an absolute path.

Use kact stop to stop motion and release buttons, kact deactivate to also hide navigation, and kact quit to stop the daemon.

Can Kact use a configuration without restarting?

Section titled “Can Kact use a configuration without restarting?”

Yes. Valid changes reload automatically by default. Set system.hot_reload = false to turn that off, then use kact reload after editing. Reloading ends active navigation and releases held input so changed bindings cannot leave a key or button held.