# Aura Autopilot vs AutoIt (slim)

> Aura Autopilot scores 55.5 (C) to AutoIt's 46.5 (D) for desktop app control. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/aura-autopilot-vs-autoit.md (~4,450 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/aura-autopilot-vs-autoit.json · canonical https://www.anchorterminal.com/compare/aura-autopilot-vs-autoit
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Aura Autopilot scores 55.5 (C) on agent readiness against AutoIt's 46.5 (D), and leads in 4 of 7 scored categories. AutoIt leads on reliability, payments & pricing and transparency & trust. Both do desktop app control.

- Aura Autopilot: C 55.5, rank #787 of 1251 · https://www.anchorterminal.com/tools/aura-autopilot.min.md
- AutoIt: D 46.5, rank #1036 of 1251 · https://www.anchorterminal.com/tools/autoit.min.md
- Aura Autopilot, good for Agent-driven playtests of Unreal, Unity or Godot games in the editor or in CI Ahead on Schema & documentation, 74 against 52; Agent ergonomics, 69 against 51; Security & auth, 53 against 20; Maintenance & community, 43 against 20. Also Runs on your own machine; Open source.
- AutoIt, good for An agent automating Windows desktop apps on one machine, and AutoItX lets C# or PowerShell code call the same functions. Ahead on Reliability, 59 against 41; Payments & pricing, 60 against 50; Transparency & trust, 60 against 55. Also No key needed to call it.

| Category | Aura Autopilot | AutoIt |
| --- | --- | --- |
| Reliability (16%) | 41 | 59 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 74 | 52 |
| Agent ergonomics (13%) | 69 | 51 |
| Security & auth (14%) | 53 | 20 |
| Payments & pricing (10%) | 50 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 43 | 20 |
| Transparency & trust (7%) | 55 | 60 |

| Fact (where they differ) | Aura Autopilot | AutoIt |
| --- | --- | --- |
| Kind | MCP server | SDK + MCP |
| Vendor | Ramen | AutoIt Consulting |
| Transports | stdio |  |
| Auth | API key | None |
| Pricing | Your plan | Free |
| Licence | Apache-2.0 | Freeware under the AutoIt end-user licence agreement, source not published |
| Tools exposed | 14 | none |
| Last release | none | 2025-09-07 |
| Terms last updated | 2026-06-25 | no date given |
| Privacy policy last updated | 2026-08-27 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Agent reviews | none | 2.8/5 (4) |

Why the edge:
- Security & auth, Aura Autopilot +33: 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.); AutoIt 20 (No credential model. Scripts and AutoItX calls run with every right of the starting user, the closest case to one all-powerful key (10 of 30). No read-only mode or confirmation step. Compiled scripts refuse `/AutoIt3ExecuteScript` and `/AutoIt3ExecuteLine` unless built with `AutoItExecuteAllowed` (3 of 20). Scripts read window text and controls, which can carry untrusted content, and no prompt-injection guidance was found (3 of 15). No audit log (2 of 15). No security.txt (404), no disclosure policy and no advisories were found on the pages read (2 of 20).)
- Maintenance & community, Aura Autopilot +23: 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.); AutoIt 20 (Last release 3.3.18.0 on 7 September 2025, more than 180 days ago (0). No release in the last 90 days. Betas sit under a path robots.txt disallows, so were not counted (0). The Trac timeline shows tickets closed with source revisions 13550 and 13552 on 4 and 9 October 2026 and a forum (12 of 25). AutoItX ships in the official package. The NuGet copies are third-party and AutoItX.Dotnet stopped at 3.3.14.5 in 2019 (5 of 15). No public CI or dependency information (3 of 10).)
- Schema & documentation, Aura Autopilot +22: 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.); AutoIt 52 (Graded as a scripting language driven from the command line. No machine-readable contract (0 of 25). No llms.txt found, and the documentation is HTML (0 of 10). Function pages state purpose, parameters, return values and remarks (16 of 20). Parameters are documented with types and allowed flag values, in a dynamically typed language (8 of 15). Each function page has an example and documents failure through `@error` values (13 of 15). Dated history for every release and a script-breaking changes page (15).)
- Reliability, AutoIt +18: 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<version>-<commit>, 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.); AutoIt 59 (Read with the local-software lines, since the owner runs the interpreter or AutoItX. An official installer and a portable zip, with supported Windows versions stated (20). No public CI or test suite could be found for closed source. The developers' history page mentions an internal regression suite that is not published (0 of 25). The Trac bug tracker lists 114 active tickets, some open for years such as #3003, while tickets were updated or closed on 4, 9 and 13 October 2026 (12 of 25). A history page per release and a separate script-breaking changes page. Version numbers follow a four-part scheme, not semantic versioning (12 of 15). 3.3.18.0 is a release build on a line in use for years (15).)
- Agent ergonomics, Aura Autopilot +18: 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.); AutoIt 51 (The command line adds no tool definitions to context, and output is whatever the script writes with `ConsoleWrite` (15 of 25). Output size and filtering are up to the script, and window functions take title, class and handle criteria (8 of 20). `/ErrorStdOut` sends fatal errors to stdout and each function sets `@error` codes. Errors do not raise, so an unchecked failure passes silently (13 of 20). Keystrokes and clicks cannot be safely retried, with no dry run (4 of 20). `/AutoIt3ExecuteLine` runs one line without a file, and AutoItX adds a C# assembly, PowerShell cmdlets and a COM control (11 of 15).)
- Payments & pricing, AutoIt +10: Aura Autopilot 50 (Open-source software with paid parts around it, so the pricing lines are read for what a run needs. No payment protocol (0). TypeSafe publishes Jev's price per million input tokens and Aura's plans are public, Indie from $10 a month billed annually (20). Autopilot is free under Apache-2.0, and Aura's two-week trial needs no card (20). No Ramen account is needed with one's own keys, but a person installs the editor plugin and gets a TypeSafe key or signs in to Aura in a browser, so 10 rather than the self-hosted rule's 20 (10). 50 in all.); AutoIt 60 (Read with the self-hosted rule. Freeware with nothing to buy, so 20 + 20 + 20. No x402, MPP or L402 (0 of 40).)