This guide takes you from a blank dashboard to a published game.

Step 1: Describe your game

From your Dashboard, type your game idea into the prompt box. Detail pays off — a strong first prompt covers:
  • Genre & perspective — “top-down dungeon crawler”, “side-scrolling platformer”
  • Art style — “dark pixel art with torchlight”, “vibrant low-poly 3D”
  • Core mechanics — “sword combat, collect gold, find the exit on each floor”
  • Win/lose conditions — “lose when health hits zero”
You can also attach reference images for the art style and pick a model (Muranyi 3.5 is the balanced default). See Prompting for what makes prompts work.

Step 2: Review the plan

New games start in plan mode by default: before building, the AI lays out what it intends to make — mechanics, scenes, art direction, scope.
  • Happy with it? Hit Approve & Build.
  • Want changes? Type modifications and approve with changes — the build follows your amended plan.
More in Plan mode.

Step 3: Watch the build

The AI agent now builds your game — writing code, creating scenes, generating all assets (images, 3d models, audio & more), then testing. Builds can take tens-of-minutes, because the agent is doing real engineering work (see How Tesana works). You can watch its progress live in the chat panel. If the AI needs a decision from you mid-build, it pauses and asks you. Answer and the AI continues.

Step 4: Play and iterate

When the build lands, your game is playable immediately in the Studio’s preview pane. Play it, then keep going with follow-up prompts:
  • “Make the player jump 20% higher”
  • “Add background music and a coin-collect sound”
  • “The enemies clip through walls on level 2 — fix that”
One focused change per prompt gets the best (and cheapest) results. For bugs, describe what you did, what you expected, and what happened instead — and attach a screenshot from the preview. See Debugging your game.

Step 5: Publish

When it’s ready to share, publish it:
  1. Open your game’s settings (gear icon in the Studio).
  2. Set up the store page — poster, screenshots, tagline, description (Storefront).
  3. Flip visibility to Published (Publishing your game).
Your game gets a public play link and a place in the marketplace. Paid plans can also export standalone builds and the full source code.

What’s next?

Prompting

The skill that determines everything else

Models

Muranyi Fast vs 3.5 vs Atomos — when to use which

How credits work

Understand the meter before your first big build

Versions & revert

Every build is saved — you can always go back