Have Cursor click through a Godot 4 playtest

A Cursor subagent can load a Godot 4 scene, follow a UI path, and surface broken inputs or scene errors.

Done with Cursor· Advanced

What they did
They added a Godot plugin, supporting skills, a command, and a Cursor subagent to the project. The studio-playtester subagent was then fed one slice at a time, along with the scene, the action to test, and the checks it should apply. It inspected the scene’s unique node names and InputMap, created a JSON flow in res://agent/, and sent that flow through the plugin’s CLI; inputs were translated into mapped actions, and screenshots were written to out/.
How it went
After each run, the agent reported either AGENT_OK or AGENT_FAIL and also marked the run PASS or FAIL. Any script error or input that had no mapping counted as a failure. The only outcome described was a boot-to-race demo.
Tips
The setup needs an actual running game window to capture and replay actions. If there is no debug scene available, the agent stops with NEED_SETUP rather than making one.

Try it yourself with Cursor

Set up Cursor to test my Godot 4 game. Launch [game_name], open [scene_name], and walk through [specific UI flow] as a player would. Use the scene’s node names and InputMap to choose valid actions, capture screenshots, and point out any broken controls, visual issues, script errors, or paths that go nowhere. Stop before any irreversible step such as sending, deleting, submitting, or paying, and ask me to confirm first. Then save the test flow and give me a clear pass/fail report with the reason.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on github.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.