Aura Autopilot vs Robot Framework

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.

Robot Framework 95

Scored as local software. Official PyPI package with Python 3.8 or later and classifiers up to 3.15 (20). Unit tests and acceptance tests on CPython and PyPy run in public GitHub Actions and passed on master on 6 October 2026, still the newest commit on 17 October (25). 311 open issues and pull requests on 14 October on a project started on GitHub in 2014. Of the 15 newest, 7 had at least one reply, and none reports a crash, per the 14 October check, not re-read on 17 October (20 of 25). Release notes carry a backwards incompatible changes section and a deprecated functionality section, and the project follows major.minor feature releases with bug-fix releases (15). Version 7.5, Development Status Production/Stable (15).

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.

Robot Framework 78

Apache-2.0 (30). The framework runs locally and collects nothing found in the source. The privacy policy covers only the websites, with Google Analytics and 50 months' retention stated (18 of 30). Deprecated functionality is listed in each release's notes with the version that removes them, such as the Telnet library in 7.5 (16 of 20). No telemetry code found in a search of the source, and the docs do not say so either way (14 of 20).

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.

Robot Framework 60

Version 7.5 on 14 September 2026, 33 days before this check (20). 7.5rc1 on 4 September and 7.5 on 14 September fall in the 90 days to 17 October. 7.5b1 of 17 July is now outside the window, so two releases, short of three (0). 150 commits since 19 July, the newest on 6 October, and recent issues and pull requests get replies from maintainers within days, with some newer ones unanswered, per the 14 October check, not re-read on 17 October (20 of 25). Current official package on PyPI with no MCP server, so not in the MCP registry (10 of 15). Dependabot updates and passing CI on master, per the 14 October check (10).

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.

Robot Framework 86

Graded as a framework. JSON schemas for results, executable suites and Libdoc library specs, and XSDs for XML output, in doc/schema. There is no tool schema for an agent because no official MCP server exists (20 of 25). llms.txt, llms-full.txt and a raw Markdown copy of each page on robotframework.org (10). The User Guide explains each option and when to use it (16 of 20). Libdoc specs type keyword arguments, and keyword argument type hints drive conversion (12 of 15). Many examples, and return codes are documented in a table (13 of 15). Versioned releases with full release notes for each (15).

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.

Robot Framework 60

Free, self-hosted, nothing to buy, so 20 + 20 + 20 under the self-hosted rule. No payment protocol (0).

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.

Robot Framework 78

The command line adds no tool definitions to an agent's context, and --loglevel, --removekeywords and --maxerrorlines size the output (20 of 25). --test, --suite, --include, --exclude and --rerunfailed select what runs (20). The exit code counts failures and distinguishes data errors (252) and internal errors (255), and messages name the failing keyword (16 of 20). --dryrun validates a suite without side effects and --rerunfailed repeats only failures. Whether a keyword is safe to retry depends on the library (12 of 20). Few required arguments and a Python API, with other languages reached through the remote library interface rather than official SDKs (10 of 15).