VyroAI

Loading...

Game Studio — Overview

Describe a browser game, approve the plan and play it inside the IDE as one HTML5 file. Which games work well, and why the preview needs an index.html.

From idea to playable

Describe a game — "a snake game with power-ups", "a space shooter with waves" — approve the plan, and the AI builds it as a single self-contained HTML5 game. Your game is the screen: on a Game or Web App project the running game fills the editor area instead of sitting in a strip at the bottom, and it re-runs the moment the AI edits a file. Refresh, Open in new tab, Download game and Publish to Arcade are always in reach, and the code is one click away under the Code tab.

What works well

Canvas games shine here: arcade, puzzle, platformer, clicker, typing games. Everything ships in one file — no installs, no servers, playable on phones too.

The preview needs a file called index.html

The panel builds its preview from index.html and nothing else. Without a file by that exact name you get "No index.html found — Create an index.html file to see a live preview" and a blank panel, however complete the rest of the project is.

This is the thing that catches people importing a game they wrote elsewhere: rename your entry file to index.html (right-click it in the file tree → Rename) and the preview appears.

Games built here are given the right name automatically, so it only comes up on imports.

How the live preview refreshes

The preview is rebuilt 600 ms after your last edit, so a burst of AI changes redraws once rather than flickering through every keystroke. If it ever looks stale, Refresh in the panel toolbar rebuilds it on the spot.

It runs in a locked sandbox: scripts may run, but the game cannot reach your account, your files or the page around it.

Iterate like a designer: play, then just say what felt wrong ("jumping is floaty", "enemies too fast") and regenerate.

Where to next

1 of 2 in Game Studio · Last checked 1 September 2026 · Previous: Saved Brands