# Aura Autopilot vs AutoHotkey > Aura Autopilot scores 55.5 (C) to AutoHotkey's 53.1 (D) for desktop app control. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/aura-autopilot-vs-autohotkey - Markdown: https://www.anchorterminal.com/compare/aura-autopilot-vs-autohotkey.md (~4,800 tokens) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-01 Aura Autopilot scores 55.5 (C) on agent readiness against AutoHotkey's 53.1 (D), and leads in 3 of 7 scored categories. AutoHotkey leads on reliability, payments & pricing, maintenance & community and transparency & trust. Both do desktop app control. - Aura Autopilot: grade C, 55.5/100, rank #787 of 1251. Markdown https://www.anchorterminal.com/tools/aura-autopilot.md · JSON https://www.anchorterminal.com/api/v1/tools/aura-autopilot.json - AutoHotkey: grade D, 53.1/100, rank #872 of 1251. Markdown https://www.anchorterminal.com/tools/autohotkey.md · JSON https://www.anchorterminal.com/api/v1/tools/autohotkey.json - Best desktop and mobile app automation for AI agents: https://www.anchorterminal.com/best/desktop-automation/index.md - All 27 desktop comparisons: https://www.anchorterminal.com/compare/desktop-automation/index.md ## Which one, for what ### Aura Autopilot (C) Good for: Agent-driven playtests of Unreal, Unity or Godot games in the editor or in CI Ahead on: - Schema & documentation, 74 against 54 - Agent ergonomics, 69 against 46 - Security & auth, 53 against 24 Also in its favour: - Runs on your own machine Watch for: Run sharing is on by default and sends recordings, screenshots, agent traces with code excerpts and, for MCP runs, the user's Claude Code or Codex conversation to app.tryaura.dev ### AutoHotkey (D) Good for: An agent automating Windows desktop apps on one machine by writing short scripts. Ahead on: - Reliability, 61 against 41 - Payments & pricing, 60 against 50 - Maintenance & community, 72 against 43 - Transparency & trust, 76 against 55 Also in its favour: - No key needed to call it Watch for: Windows only, and scripts act with every right of the user who runs them ## Why the edge ### Security & auth: Aura Autopilot +29 - Aura Autopilot (53): Local-software reading, as tokeneconomizer was read: 30 for what leaves the machine and credentials, 20 approvals and sandboxing, 15 injection, 15 audit, 20 programme. Run sharing is on by default and sends recordings, screenshots, agent traces with the code the agent read and, for MCP runs, the user's own Claude Code or Codex conversation to app.tryaura.dev, after redacting secrets, paths, user and host names and email addresses. Keys sit in plain text in autopilot.env, the file tools never read *.env, and the localhost control endpoint carries a random secret (12). File tools write only the run's folder, notes.md and lib.py, and the user can stop or steer a run from the tab. `autopilot connect codex` sets default_tools_approval_mode to approve, and on Windows and macOS the sandbox is a plain child process without keys but with network and disk (10). sandbox.py names prompt injection from a game's code as the reason for the sandbox, and the frame describer is given only open questions (11). Each run keeps its agent log, harness versions, traces, decisions, report and recording, and the Feed tab shows activity (13). SECURITY.md asks for GitHub private vulnerability reporting; no security.txt on www.tryaura.dev (404), no bounty or certification found, advisories couldn't be read. Releases are signed and immutable, and pull requests need a code owner's approval (7). 53 in all. - AutoHotkey (24): No credential model. Scripts run with every right of the user who starts them, the closest case to one all-powerful key (10 of 30). No read-only mode, permission scoping or confirmation step for actions (3 of 20). Scripts read window text, controls and the clipboard, which can carry untrusted content, and no guidance on prompt injection was found (3 of 15). `ListLines`, `KeyHistory` and the debugger show what a script did, with no audit log (4 of 15). No SECURITY.md, no published advisories and no security.txt could be read. A code signing policy is linked from the home page and could not be read past the bot check (4 of 20). ### Maintenance & community: AutoHotkey +29 - Aura Autopilot (43): The launch post is dated 31 October 2026 and Aura 1.2.3 and 1.2.4 of 30 October 2026 ship Autopilot, so the last change is within 30 days (30). GitHub releases couldn't be read, and the two Aura release-note entries aren't three (0). Issue and pull-request replies couldn't be read; the project is days old, with Discord and support email as other channels (5 of 25). Not in the official MCP registry under any namespace (searched for autopilot and ramenvr) (0). Pinned dependencies, per-platform locks in packaging/, CI on three operating systems, conventional-commit checks and code-owner review (8 of 10). 43 in all. - AutoHotkey (72): 2.0.30 on 9 October 2026 (30). 2.0.27 to 2.0.30 between 28 August and 9 October 2026, plus 2.1 alphas 31 to 35 (20). The changelog credits merged pull requests from outside contributors, but pull requests from 2022 to 2025 remain open with no decision, and the forum where bugs are reported could not be read (12 of 25). No MCP server or package registry entry. Release assets are current on GitHub (7 of 15). No CI and no dependency tooling in the repository (3 of 10). ### Agent ergonomics: Aura Autopilot +23 - Aura Autopilot (69): MCP reading. 14 tools (15 for 11 to 30), with long descriptions on probe and run_harness and a long INSTRUCTIONS.md the skill says to read in full, with no toolsets (13 of 25). read_file takes offset and limit up to 2,000 lines, list_files returns at most 500, search at most 200 with a glob, frames up to 12 and run_harness takes seconds of play (16 of 20). Errors come back as isError with what to do next (open the editor, update the agent service, call wait), and headless runs exit 0, 1, 2 or 3 (16 of 20). readOnlyHint is set on the seven read tools and destructiveHint false on all, including probe, which the description says can change the game directly. One call runs at a time and a long one answers "still going" for `wait` to collect (14 of 20). Two required parameters on start_run with defaults of 10 minutes of exploration and a 30-minute limit; no SDKs, which a playtester doesn't need (10 of 15). 69 in all. - AutoHotkey (46): The command line adds no tool definitions to context, but output is whatever the script writes, with no structured format (15 of 25). Output size and filtering are up to the script. Window functions take title, class, process and exclusion criteria (8 of 20). `/ErrorStdOut` puts load-time errors on stderr and `/Validate` exits non-zero on a load error, while runtime errors open a dialog unless the script uses `OnError` or `try` (12 of 20). Keystrokes and clicks cannot be safely retried and there is no dry run beyond `/Validate` (4 of 20). One executable, scripts on standard input with `*`, and an experimental DLL host. No SDK in a second language (7 of 15). ### Transparency & trust: AutoHotkey +21 - Aura Autopilot (55): Apache-2.0 for the repository, with bundled fonts under the SIL OFL (30). The repository's code docstrings and the Unreal README say what is shared and how it is redacted, but docs/run-data.md, which they cite, isn't published. Aura's terms (TribeVR Inc., 25 June 2026) and privacy policy (27 August 2026) don't mention Autopilot, opt Aura customers into training by default with a perpetual licence to that data, and state no retention period. Runs with one's own keys go to Aura's endpoint under an install token with no account and no terms named. Sent data is never deleted (10 of 30). No deprecation policy; the protocol rule to add optional fields is a contributor guideline (6 of 20). Sharing is disclosed in the setup screen, the README and the plugin docs with three ways to turn it off, but it is on by default, the documentation page doesn't say so, and it includes the user's own agent conversation (12 of 20). 58 in all. - AutoHotkey (76): The editorial half. GPL-2.0 on the repository and on the home page (30). No privacy statement for the software. A search of the interpreter source found no network code, and the docs describe the one optional update check (15 of 30). The README says v1 is not maintained, and deprecated switches such as `/iLib` are marked in the docs, with no dated deprecation policy (10 of 20). The update check is off by default and documented with its registry switch, and no telemetry was found (18 of 20). The provenance half is computed from the provenance block. ### Reliability: AutoHotkey +20 - Aura Autopilot (41): Local-software reading, as a stdio MCP server with engine plugins. Official downloads per engine and OS from GitHub Releases, signed and listed in SHA256SUMS.txt, with Unreal 5.4 to 5.8, Unity 6000.0 or later, Godot 4.7 or later, Windows and macOS and Python 3.12 or later stated. The agent service isn't on a package registry; the plugin installs it, with uv and Bun, on first run (17 of 20). .github/workflows/ci.yml runs ruff and pytest on Linux, Windows and macOS with Python 3.12 and 3.13 plus a Codex end-to-end job, and CONTRIBUTING.md names download and uninstall end-to-end workflows. Whether runs pass wasn't checked, as github.com couldn't be read (15 of 25). Open issues couldn't be read, and the repository is days old (5 of 25). No changelog; releases are tagged v-, the plugin protocol is versioned and the contributing rules say to add optional fields rather than change existing ones (4 of 15). Python package 0.1.0 and the Unreal plugin marked IsBetaVersion (0). 41 in all. - AutoHotkey (61): Read with the local-software lines, since the owner runs the interpreter. Official builds are a zip and a setup executable on GitHub releases for 32-bit and 64-bit Windows. The supported Windows versions were on autohotkey.com, which a bot check blocked, so not confirmed (18 of 20). The repository has no CI workflow and no test suite (0 of 25). GitHub Issues was disabled from 2017 until October 2026 and now shows one open issue and ten open pull requests, the oldest from 2022. Bug reports go to the forum, which we could not read (15 of 25). A dated changelog for every release. 2.0.x releases carry fixes only and additions go to 2.1 alphas, though the changelog records regressions such as one `broken by v2.0.20` and fixed in 2.0.30 (13 of 15). Version 2.0 is the stable line (15). ### Schema & documentation: Aura Autopilot +20 - Aura Autopilot (74): MCP reading. All 14 tools (start_run, wait, probe, run_harness, snapshot, describe_frames, restart_level, report, frames and five file tools) have JSON Schema inputs, read in autopilot/mcp.py, session.py, external.py and files.py (25). No llms.txt on www.tryaura.dev (404). The agent skill, INSTRUCTIONS.md and KIT.md are Markdown written for the agent, and the README and CONTRIBUTING.md are in the repository (7 of 10). Descriptions say what each tool does and when not to use it (`frames` is for a describer subagent only, `describe_frames` is a fallback), with server instructions (17 of 20). Required fields and an enum on `kind`, but `report.outcome` is a free string with its values only in the description, numeric ranges sit in descriptions rather than the schema, and `probe` takes free-form Python (9 of 15). Prompt examples in the README and skill, plain-language errors in the MCP server and documented exit codes for headless runs (11 of 15). Version numbers and a protocol version, but no public changelog, and GitHub release notes couldn't be read (5 of 15). 74 in all. - AutoHotkey (54): Graded as a scripting language driven from the command line. No machine-readable contract for the language or the command line (0 of 25). No llms.txt found, and the documentation is HTML in the AutoHotkeyDocs repository (0 of 10). 356 function reference pages state what each function does, its parameters and when it raises an error (17 of 20). Parameters are documented with types, defaults and allowed values, in a dynamically typed language (9 of 15). Every function page has examples, and errors raised are named per function, with the `Error` class hierarchy documented (13 of 15). Versioned releases and a dated changelog back to 2003 (15). ## Score by category | Category | Weight | Aura Autopilot | AutoHotkey | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 41 | 61 | AutoHotkey +20 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 74 | 54 | Aura Autopilot +20 | | Agent ergonomics | 13% (16.2 this run) | 69 | 46 | Aura Autopilot +23 | | Security & auth | 14% (17.5 this run) | 53 | 24 | Aura Autopilot +29 | | Payments & pricing | 10% (12.5 this run) | 50 | 60 | AutoHotkey +10 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 43 | 72 | AutoHotkey +29 | | Transparency & trust | 7% (8.8 this run) | 55 | 76 | AutoHotkey +21 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **55.5 · C** | **53.1 · D** | | ## Facts side by side | Fact | Aura Autopilot | AutoHotkey | | --- | --- | --- | | Kind | MCP server | SDK + MCP | | Vendor | Ramen | AutoHotkey Foundation | | Hosted endpoint | no (local only) | no (local only) | | Transports | stdio | | | Auth | API key | None | | Pricing | Your plan | Free | | x402 | no | no | | Licence | Apache-2.0 | GPL-2.0 | | Tools exposed | 14 | none | | Read-only variant documented | no | no | | llms.txt | no | no | | Last release | none | 2026-10-09 | | Terms last updated | 2026-06-25 | no document linked | | Privacy policy last updated | 2026-08-27 | no document linked | | Customer content may train models | yes, with an opt-out | not read yet | | Terms restrict automated access | not found in the text | not read yet | | Terms restrict benchmarking | not found in the text | not read yet | | Terms or service can change without notice | not found in the text | not read yet | | Arbitration or class-action waiver | not found in the text | not read yet | | Popularity | none | 13k stars | ## How the scores have moved ### Aura Autopilot No score change since it was listed. ### AutoHotkey - +0.2 on 28 October 2026: new evidence - +0.1 on 27 October 2026: new evidence ## Verdicts **Aura Autopilot.** Apache-2.0, with typed MCP tools carrying read-only hints, a separate process for model-written code and headless exit codes for CI. It is days old with no changelog, needs a TypeSafe Jev key or an Aura account, and by default shares recordings, agent traces and the user's own agent conversation with Ramen unless turned off. **AutoHotkey.** An agent can write a script and run it through the command line, with a script read from standard input, `/Validate` and `/ErrorStdOut` for clean failures, and a function reference of 356 pages. It runs on Windows only with the user's full rights, and the repository has no CI or test suite. ## Before you call either ### Aura Autopilot 1. Check the game's project is open in the editor with the Autopilot tab connected before calling start_run; otherwise it answers that the agent service isn't running. 2. When a call answers "still going", call `wait` until it returns; don't start another tool call meanwhile. 3. Pass the user's request in their own words with kind verify, goal or explore, and read the INSTRUCTIONS.md that start_run names in parts with Autopilot's read_file. 4. Tell the user that run data is shared by default and how to turn it off (the Settings page, AUTOPILOT_SHARE=0 or -PlaytestShare=0) before the first run. 5. Never ask the user to paste a TypeSafe or provider key into the conversation; keys belong in autopilot.env or the Autopilot tab. ### AutoHotkey 1. Write output with `FileAppend text, "*"` and pipe the interpreter's output, since stdout does not appear at the console it was launched from 2. Run `AutoHotkey64.exe /ErrorStdOut /Validate script.ahk` before running a new script 3. Add `OnError` or `try` blocks so a runtime error does not leave a dialog open in an unattended run 4. Target v2 syntax. v1 is unmaintained and its scripts do not run on v2 ## Questions ### Which is better for AI agents, Aura Autopilot or AutoHotkey? Aura Autopilot scores 55.5 (C) on agent readiness against AutoHotkey's 53.1 (D), and leads in 3 of 7 scored categories. AutoHotkey leads on reliability, payments & pricing, maintenance & community and transparency & trust. ### Can an agent call Aura Autopilot and AutoHotkey without installing anything? Aura Autopilot runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for AutoHotkey. ### Are Aura Autopilot and AutoHotkey open source? Yes. Aura Autopilot is open source (Apache-2.0). AutoHotkey is open source (GPL-2.0). ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/aura-autopilot-vs-autohotkey.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aura-autopilot-vs-autohotkey.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "aura-autopilot", "b": "autohotkey"}`. From a terminal: `anchor compare aura-autopilot autohotkey` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/aura-autopilot.json and https://www.anchorterminal.com/api/v1/tools/autohotkey.json ## Other comparisons with Aura Autopilot or AutoHotkey - [Aura Autopilot vs AutoIt](https://www.anchorterminal.com/compare/aura-autopilot-vs-autoit.md) - [Aura Autopilot vs Automation Anywhere](https://www.anchorterminal.com/compare/aura-autopilot-vs-automation-anywhere.md) - [Aura Autopilot vs Beam (beam.win)](https://www.anchorterminal.com/compare/aura-autopilot-vs-beam-win.md) - [Aura Autopilot vs Robocorp](https://www.anchorterminal.com/compare/aura-autopilot-vs-robocorp.md) - [Aura Autopilot vs UiPath](https://www.anchorterminal.com/compare/aura-autopilot-vs-uipath.md) - [AutoHotkey vs AutoIt](https://www.anchorterminal.com/compare/autohotkey-vs-autoit.md) - [AutoHotkey vs Automation Anywhere](https://www.anchorterminal.com/compare/autohotkey-vs-automation-anywhere.md) - [AutoHotkey vs Beam (beam.win)](https://www.anchorterminal.com/compare/autohotkey-vs-beam-win.md) - [AutoHotkey vs Robocorp](https://www.anchorterminal.com/compare/autohotkey-vs-robocorp.md) - [AutoHotkey vs UiPath](https://www.anchorterminal.com/compare/autohotkey-vs-uipath.md) - [Aura Autopilot vs Robot Framework](https://www.anchorterminal.com/compare/aura-autopilot-vs-robot-framework.md) - [AutoHotkey vs Robot Framework](https://www.anchorterminal.com/compare/autohotkey-vs-robot-framework.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp