# Aura Autopilot vs Robocorp (slim)

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

- Full: https://www.anchorterminal.com/compare/aura-autopilot-vs-robocorp.md (~4,350 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/aura-autopilot-vs-robocorp.json · canonical https://www.anchorterminal.com/compare/aura-autopilot-vs-robocorp
- 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)

Robocorp scores 65.5 (B) on agent readiness against Aura Autopilot's 55.5 (C), and leads in 4 of 7 scored categories. Aura Autopilot leads on schema & documentation, agent ergonomics and security & auth. Both do desktop app control.

- Aura Autopilot: C 55.5, rank #787 of 1251 · https://www.anchorterminal.com/tools/aura-autopilot.min.md
- Robocorp: B 65.5, rank #363 of 1251 · https://www.anchorterminal.com/tools/robocorp.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 65; Agent ergonomics, 69 against 59; Security & auth, 53 against 44. Also Runs on your own machine.
- Robocorp, good for Python RPA on Windows desktops, browsers and documents, written or run by a coding agent. Ahead on Reliability, 87 against 41; Payments & pricing, 60 against 50; Maintenance & community, 81 against 43; Transparency & trust, 65 against 55. Also No key needed to call it.

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

| Fact (where they differ) | Aura Autopilot | Robocorp |
| --- | --- | --- |
| Kind | MCP server | SDK + MCP |
| Vendor | Ramen | Sema4.ai |
| Transports | stdio |  |
| Auth | API key | None |
| Pricing | Your plan | Free |
| Tools exposed | 14 | none |
| Last release | none | 2026-10-04 |
| 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 | 1.6k stars, 61k PyPI/wk |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Reliability, Robocorp +46: 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.); Robocorp 87 (Scored as local software. Official PyPI packages with Python 3.10 or later stated, robocorp up to 3.15 and rpaframework up to 3.14 (20). Public CI per package, with rpaframework's main and Windows workflows passing on master on 4 October 2026 and robocorp's master runs passing to 14 October (25). rpaframework has 35 open issues and pull requests and robocorp 9. Of rpaframework's 15 newest, 8 had no reply, including RPA.Windows and Java Access Bridge problems from 2024 (12 of 25). The README commits to SemVer and each package has a dated changelog (15). rpaframework is marked Production/Stable at 33.0.2 and robocorp is 3.1.4 (15).)
- Maintenance & community, Robocorp +38: 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.); Robocorp 81 (rpaframework 33.0.2 on 4 October 2026 (30). rpaframework 33.0.0, 33.0.1 and 33.0.2 and robocorp 3.1.2 to 3.1.4 since 23 August 2026 (20). Commits are frequent, but most new issues get no reply (12 of 25). Current official packages, no MCP server (10 of 15). Lockfiles, scheduled dependency checks and passing CI (9 of 10).)
- Agent ergonomics, Aura Autopilot +10: 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.); Robocorp 59 (No tool definitions in context. Output size is controlled through robocorp.log settings rather than call parameters (15 of 25). Locators, timeouts and work item iteration, but little output filtering (12 of 20). Typed exceptions such as ElementNotFound, MultipleElementsFound and TimeoutException (14 of 20). No idempotency guidance. Work items fail with a BUSINESS type, documented as not to be retried, or an APPLICATION type (8 of 20). Sensible defaults, Python and Robot Framework keyword interfaces (10 of 15).)
- Payments & pricing, Robocorp +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.); Robocorp 60 (The libraries are free and self-hosted, so 20 + 20 + 20 under the self-hosted rule. Control Room is the paid option, but its pricing on sema4.ai was behind a bot check and could not be scored. No payment protocol (0).)
- Transparency & trust, Robocorp +10: 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.); Robocorp 65 (Apache-2.0 for both repositories (30). The libraries run locally. Sema4.ai's privacy policy and terms were behind a bot check, and rpaframework.org loads Google Analytics (8 of 30). Changelogs record removals and deprecations, with no deprecation policy found (10 of 20). No telemetry code in the libraries. rcc has a do-not-track setting whose default was not read (8 of 20).)
- Schema & documentation, Aura Autopilot +9: 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.); Robocorp 65 (Graded as a library. Typed Python APIs with docstrings and keyword documentation at rpaframework.org. No machine-readable contract beyond the code (12 of 25). No llms.txt on rpaframework.org (404). The repository's agent skill and its api.md reference are Markdown written for coding agents. sema4.ai docs were unreadable (5 of 10). Keyword docs state purpose with arguments, rarely when not to use one (12 of 20). Type hints and enums on most keywords, some locator strings free-form (10 of 15). Examples throughout, and typed exceptions such as ElementNotFound (11 of 15). Dated changelogs per package and SemVer (15).)