nolindnaidoo/pixelactions

<h1 align="center"pixelactions</h1

<p align="center" <bConsume human-verified coordinates, perform the interaction, confirm it landed</b<br/ <iClick, type, chord, drag, scroll — from a chained CLI, a flow file, or a line protocol any language can drive</i </p

<p align="center" <a href="https://github.com/nolindnaidoo/pixelactions/actions/workflows/ci.yml" <img src="https://github.com/nolindnaidoo/pixelactions/actions/workflows/ci.yml/badge.svg" alt="Build Status" / </a <a href="https://docs.rs/pixelactions-core" <img src="https://img.shields.io/docsrs/pixelactions-core.svg" alt="docs.rs" / </a <a href="https://crates.io/crates/pixelactions" <img src="https://img.shields.io/crates/v/pixelactions.svg" alt="crates.io" / </a <img src="https://img.shields.io/badge/rustc-1.88+-93450a.svg" alt="MSRV: Rust 1.88+" / <a href="https://github.com/nolindnaidoo/pixelactions/blob/main/LICENSE" <img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="License: MIT" / </a <a href="https://pixelactions.dev" <img src="https://img.shields.io/badge/web-pixelactions.dev-00A0FF.svg" alt="pixelactions.dev" / </a </p

<p align="center" <img src="https://github.com/nolindnaidoo/pixelactions/raw/main/docs/assets/demo.gif" alt="pixelactions demo: a chained command clicks a field, types an address, submits, and waits until the confirmation appears — reporting each step as it lands" style="max-width: 100%; height: auto;" / </p

pixelcoords freezes your screen, lets you mark labeled regions, and writes pixel-exact coordinates with crops, drift re-location, and point verification. pixelactions reads that session and acts on it — referencing regions by label, never by raw coordinate, so a run survives the UI moving.

find  →  act  →  assert

No account, no network surface, no daemon — one small native binary that runs, acts, and exits. MIT-licensed, because the aim was to build the best executor in this category and give it away.

Useful? A star is how other developers find it — ★ GitHub · pixelactions.dev

A coordinate is only worth having if something acts on it. pixelactions is the second half of that loop: it reads a session a human marked in pixelcoords, resolves the label to a point, performs the interaction, and confirms it landed.

Actions name regions by label, never by coordinate. Nothing is injected without --yes. Every step reports whether it executed or was verified — because an OS accepting a click is not the same as the application reacting to one.

Install

macOS, with Homebrew — this pulls pixelcoords with it, so the pairing cannot drift:

brew tap nolindnaidoo/tap
brew install pixelactions

Prebuilt binaries for macOS (arm64 and x8664), Linux (x8664) and Windows (x8664) are on the releases page — download, unpack, run. Or build it with cargo:

cargo install pixelactions

Rust 1.88+ for the cargo route. pixelactions drives the pixelcoords binary for capture-time work — install both:

cargo install pixelcoords pixelactions

Building on Linux needs the xkbcommon headers, because typing on Wayland means looking a character up in the compositor's own keymap: