Macronaut → AutoHotkey alternative

An AutoHotkey alternative you don’t have to write code in

AutoHotkey is a programming language. That is its strength and it is also the reason most people who need it never end up using it. Macronaut does the common half of the same job with a screen of numbers you fill in — or, when a job needs more than that, by recording what you do and letting you wire the steps together on a canvas.

The same job, both ways

An auto-clicker you can start and stop with F8. In AutoHotkey v2 that is a script you write, save as a .ahk file, and run:

#Requires AutoHotkey v2.0

running := false

F8:: {
    global running := !running
    if running
        SetTimer(DoClick, 100)
    else
        SetTimer(DoClick, 0)
}

DoClick() {
    Click
}

Neither of those is hard. But the left-hand one asks you to know that a directive goes at the top, that global is needed inside a function, that a timer is how you repeat something, and that 0 is how you turn a timer off. If you already know those, you lost nothing. If you do not, you have four things to learn before your mouse clicks once.

What AutoHotkey does better

This part is not close, and pretending otherwise would waste your time:

• It is a real language. Variables, functions, arrays, string handling, file I/O, COM automation, sending Windows messages directly to a control. Macronaut has a script with branches and loops; that is nowhere near the same reach.
• Twenty years of community. Almost any problem you have has a forum thread with a working answer in it. Macronaut is one person.
• Tiny. A fraction of the download, and it has been packaged and repackaged everywhere for twenty years.
• Remapping keys and building custom hotkeys across the whole system, which is arguably what it is best at and is not what Macronaut is for at all.

What Macronaut does better

• Nothing to learn first. The window it opens on is an auto-clicker with the numbers already on it. Or press Record, do the thing once, press stop — what you did is now a script you can edit, reorder and re-run.
• You can see it. A script is a diagram, not code, so a colleague can read it, and so can you in six months. Debugging is watching which node lights up.
• Reading the screen is built in. Wait-for-image, wait-for-text through Windows’ own OCR, and wait-for-pixel are steps you drop in, not libraries you find and wire up.
• Input that games accept. Three backends — ordinary injection, SendInput scancodes, and an Interception kernel driver — switchable from a dropdown when a target ignores the first one.
• It is one file. No installer, no runtime, no admin rights.

Which one should you use?

Use AutoHotkey if you want system-wide hotkeys and remapping, if your task needs real logic or touches files and other programs, or if you write code already and the syntax costs you nothing.

Use Macronaut if the task is “do these clicks and keystrokes, watch for that thing to appear, then carry on”, if you want to hand the automation to someone who does not code, or if you have genuinely been meaning to learn AutoHotkey since last year and have not.

They also coexist perfectly well. Nothing stops you keeping AutoHotkey for your keyboard remaps and using Macronaut for the repetitive screen work.

Trying it

Macronaut is a single 78 MB file for Windows 10 and 11. No installer, no account, and every feature is free.

Windows will say “Windows protected your PC” on first run. It says that for any app without a signing certificate — click More info, then Run anyway.

Also worth comparing: Macronaut against TinyTask, if what you want is to record something rather than write it.

Wrong about something here? AutoHotkey moves and I would rather this page were accurate than flattering — gerbenvanpoucke0@gmail.com.