That dialog again? Have it handled before you see it.
Some windows exist to interrupt you on a schedule: the VPN re-auth prompt, the legacy app's "confirm session" box, the update nag you'll deal with Friday, the remote client's "are you still there?". If you press the same button on the same window every single time, that press can be automated — carefully.
First, the caveat that matters
Auto-dismissing dialogs is power-tool territory: a dialog is sometimes information. Automate only windows whose answer is genuinely always the same — "OK" on the session notice, "Reconnect" on the VPN box — and never anything that can destroy data ("Don't save", "Delete", "Format"). Every tool on this page will press exactly what you told it to, including the wrong thing, forever.
The scripting way: AutoHotkey
The classic solution is an AutoHotkey script: WinWait, Session Expired then ControlClick, Button1, wrapped in a loop. It's free and endlessly flexible — and it's programming: window titles, control names via Window Spy, edge cases when the title changes with the app's language or version. If you enjoy that, AHK remains the deepest tool in the drawer (our comparison: AutoHotkey without the code).
The no-code way: a window cue
In CueValet the same job is one rule, built by pointing:
- Cue: a window appears. Pick the window by title (match exactly or "contains", so version numbers don't break it).
- Action: what you'd do by hand. Click a spot inside that window (with cursor restore, so your real pointer snaps back), press a key like Enter or Esc, type text, or just fire a notification if you'd rather decide yourself.
- Re-arm. The rule goes back to watching, and the Tuesday popup stops being your job.
Rules live in a list you can toggle per-situation, there's a global hotkey to disarm everything instantly, and it all runs locally — CueValet has zero telemetry.
Combine cues for the fussy cases
- Window + pixel: some dialogs are the same window with different content — add a pixel colour check so the click only fires on the variant you mean.
- Timer + window: only watch during the nightly batch window, not while you're actually using the app.
- Notify instead of click: for dialogs you want to know about but decide on — CueValet taps you on the shoulder and touches nothing.
The honest fine print
- CueValet presses buttons by simulating input, and Windows flags simulated input as injected — visible to software that inspects input at a low level. For desktop dialogs this is irrelevant; in games with anti-cheat, assume it's visible.
- Apps running as administrator need CueValet running as administrator too, or Windows won't deliver the click.
Plainly. One recurring dialog, same button every time, answer never varies: automate it and reclaim the interruption. CueValet does it without a line of script — try it free for 3 days, point it at your most annoying popup, and see.
3-DAY FREE TRIAL · ONE-TIME · 2 PCs · PORTABLE · 14-DAY REFUND · WINDOWS 10/11