autopilot-playtest

Automated Playtest with Autopilot

Autopilot plays the game open in the Godot editor. You write the harness for this request, run it through Autopilot's MCP tools, and file what play showed.

Autopilot's own instructions (INSTRUCTIONS.md, named by start_run) are the detailed reference. This skill is the framework's wrapper around them.

The result is automated evidence. It is never a human playtest.

---

Setup (once per machine and project)

Rationale and verified behaviour: docs/framework/autopilot-integration.md.

• Harness. OpenCode 2.2.5, Pi 1.x and omp 18.16.0 are verified. Tool names differ by harness. In this skill, a bare name such as start_run means Autopilot's MCP tool of that name, shown as autopilot_start_run in OpenCode, mcp__autopilot__start_run in Pi and mcp__autopilot_start_run in omp. Other harnesses: stop and say so, and do not edit their config.
• Godot 4.7 or later. Autopilot's addon README states this. The addon is tested on 4.7.2, which this framework's Godot reference is pinned to. The addon has no runtime version check, so Godot 4.6 is untested.
• Addon. Install addons/autopilot/ into the game project from Autopilot's download. Enable it in Project Settings > Plugins, then commit the project.godot changes it makes (autoload AutopilotPlaytest, and autopilot/project_id). Do not copy the addon into this repository.
• Agent service and Bun. Install Autopilot's agent service, which provides the autopilot command that opencode.json runs. Install Bun, which Autopilot's default harness agent needs.
• Keys. Bring your own keys: a TypeSafe decision key and an LLM key, both in Autopilot's autopilot.env. Do not sign in to Aura.
• Sharing. In the dock's Privacy step, turn sharing off. Autopilot shares recordings, screenshots, traces and memories by default.
• Releases. Exclude addons/autopilot/* from export presets.

---

Phase 1: Preflight

1. Confirm the server is enabled for this session. In OpenCode, opencode.json → mcp.servers.autopilot must have disabled set to false. In Pi, the autopilot entry in your mcp.json must have enabled set to true and exposure set to direct. Pi's own MCP view can enable the server, and after editing the file, reconnect the server there or restart Pi. In omp, the autopilot entry in .omp/mcp.json must have enabled set to true; restart omp after editing it. If it is off, ask the user whether to enable it for this session, then stop until they answer. If the entry is missing, stop and tell the user to add it from the Autopilot section of /setup-engine. Do not edit config files yourself.
2. Readiness. The Autopilot tools join your tool list only after the MCP server starts. That took about 5 seconds in testing and can take longer on a cold start. Check that autopilot_start_run (OpenCode), mcp__autopilot__start_run (Pi) or mcp__autopilot_start_run (omp) is among your tools. If it is not, make one cheap read-only call (for example read on AGENTS.md) so the next turn sees the tools, then check again. Make at most 20 such checks. If the tool is still missing, stop and tell the user: "Autopilot's MCP server did not start. Check that the autopilot command is on PATH, then run opencode mcp list (OpenCode), pi mcp list (Pi) or /mcp list (omp). Send the request again once autopilot shows connected."
3. Confirm the game's project is open in the Godot editor with the Autopilot dock connected. If start_run says the agent service isn't running, relay its message and stop.
4. Keys: never ask the user to paste a key into this chat. If a run asks for a key, tell the user where it goes (see Setup).
5. Sharing: confirm the dock's Privacy step is off (see Setup). If the user has not confirmed this, ask before the first run.