Guide · August 2026

A pixel & window trigger tool.

Some of the most useful automation on Windows starts with watching the screen: a spot that turns a certain colour, or a window that finally appears. This is a plain-English look at how those two triggers work, what people use them for, and how CueValet handles them.

What a pixel trigger is

A pixel trigger watches one point on your screen and fires when its colour matches — or simply changes. Under the hood it reads the colour value at an exact screen coordinate and compares it, many times a second, against the colour you're waiting for. That's it: no access to the app's internals, no reading its files, just the same pixels you can see. It's a surprisingly good stand-in for “has the state changed?” whenever an app shows that state as a colour — a status light, a progress bar, a badge going from grey to green.

What a window trigger is

A window trigger watches for a window to appear rather than a colour. You give it part of a window's title; when a window whose title contains that text shows up, the rule fires. It's the clean way to handle the dialogs you keep having to dismiss — a “Reconnect”, a “Session expired”, a “Save As” — without staring at the screen waiting for them.

Common uses

  • A build or CI light turns green (or red). Watch the indicator; when it flips, get a notification or launch the next step — instead of alt-tabbing to check.
  • A “Reconnect” or “Session expired” dialog appears. The window-appears trigger clicks OK for you so a dropped connection doesn't sit there waiting.
  • An idle or incremental single-player game. Tap a key on a timer, or click when a bar refills, while it grinds in the background.
  • Watching a dashboard for a colour. A tile you'd otherwise keep glancing at — let the pixel trigger alert you the moment it changes.

One neutral note on online games. Simulated input isn't invisible. Anti-cheat systems can look at input patterns and flag or detect automation, and Windows itself tags software-generated input as injected. Whether automating anything at all is allowed is a matter between you and that game's own rules — CueValet makes no “undetectable” claim. Single-player and offline grinds are the uncontroversial fit.

How CueValet does it

CueValet keeps both triggers point-and-click:

  • Pick the point off the screen. Click the exact spot and CueValet reads its colour for you — no typing hex values by hand.
  • Match on change or on a specific colour, with a tolerance setting so anti-aliasing and slight gradients don't cause misses or false hits.
  • Window trigger by title text. Type part of a window title; the rule fires when a matching window appears.
  • Guard-rails, built in. A minimum gap between fires, and any rule that starts firing too fast pauses itself — a flickering pixel never becomes a machine-gun of clicks.
  • Then do something: click a point, press keys, type text, open an app/file/URL, or show a notification. One master hotkey (F10) arms every rule; it all lives in the system tray with a discreet log, as one portable .exe with no telemetry.

The short version: pixel and window triggers turn “something on screen changed” into an action, no code required. CueValet picks the point and colour straight off the screen, adds tolerance so real screens don't fool it, and caps runaway rules with guard-rails. $19.99 once, 2 PCs, portable, 14-day refund.

ONE-TIME · 2 PCs · PORTABLE · 14-DAY REFUND · WINDOWS 10/11