Full game tester
Game Studios spent $1.7B a year on playtesting. Don't be one of them.
Fully playtest your game with AI: Ziva's Playtest Agent plays your Godot game toward the goal you set and returns a pass or fail verdict.
One real run on Godotcraft, start to verdict:
- 1The playtest QA agent is told to chop down a tree and make a crafting bench.
- 2It analyzes the game, identifying movement, pathfinding, tree blocks, and crafting.
- 3It walks towards the tree, chops a log down, picks it up, and creates the Crafting Bench.
- 4A video showcasing the playtest start to finish is analyzed by AI for pass/fail, and saved for viewing.
How it works
AI driven playtesting
You give it a suite of tests to run, like “the score goes up when the player clears a pipe”, and the AI plays until it sees that happen.
Reads your code first
Reads your code to learn the controls and plan the test. Playtesting may temporarily change project files and add diagnostic logging.
Launches it, then freezes it
Runs your game and pauses between actions to decide what to try next.
Plays, and measures every move
Uses the controls, checks screenshots and results, and records what happened.
Ends with a verdict
The AI looks at everything completed as a whole to determine if the tasks were completed successfully, and saves a video for you to review as well.
Your game runs on your machine, and your project files stay there. The agent sends what it reads and the screenshots it takes to a hosted model for thinking and image analysis.
Versus a general AI agent
Most AI agents can't play your game
Cursor, Claude Code and Copilot are great at writing the code. Without a game-engine MCP server, none of them can play the game. When one of them says "I fixed it", it is reading the source and guessing, and you may only find out otherwise when you play the game yourself.
| Capability | Cursor · Claude Code · Copilot | Ziva Playtest Agent |
|---|---|---|
| Writes and runs your unit tests | via the terminal | run_tests, headless |
| Launches and plays the actual game | no hands on the game | drives it turn by turn |
| Sends real player input | needs an engine MCP server | keys, clicks, drags, aim |
| Measures the live scene while playing | only reads the code | probes + your own signals |
| Cannot edit what it is judging | edits it, then declares success | ships with no write tools |