Playtest a Godot 4 game with a Cursor agent
A Cursor plugin and subagent lets an agent capture screenshots and click through UI flows of a Godot 4 game like a player.
What they did
You install a Godot plugin, skills, a command and a subagent. The caller gives the studio-playtester subagent a slice with criteria, a scene and an action. The agent inspects the scene's unique node names and InputMap, writes a JSON flow under res://agent/, and runs it through the plugin's CLI. Button presses go in as mapped input actions, and screenshots land in out/.
How it went
Each run ends in AGENT_OK or AGENT_FAIL, and the agent reports PASS/FAIL. A script error or unmapped input counts as a failure. The source gives no measured results beyond a boot-to-race demo.
Worth knowing
Capture and flow runs need a real game window. If the debug scene is missing, the agent returns NEED_SETUP and stops, and it won't build one.
Labels
Playtest a Godot 4 game with a Cursor agent
The agent inspects the scene's unique node names and InputMap, writes a JSON flow under res://agent/, and runs it through the plugin's CLI.
A Cursor plugin and subagent lets an agent capture screenshots and click through UI flows of a Godot 4 game like a player.
The “Material” label failed its quality check and is not used for selection.
Details
- Agents
- Cursor
- Source
- GitHub
- Source date
- undated
- Accounts
- 1
- In registry since
- Oct 12, 2026