How Vibecade Works
Vibecade is a chat-first AI game development workspace. Instead of bouncing between separate tools, you guide the build from one place and use the preview, files, and logs to steer the next decision.
The basic loop
Section titled “The basic loop”Every project follows the same high-level cycle:
- Describe the game you want.
- Vibecade creates or updates the project.
- Test the result in the live preview.
- Ask for the next change.
- Publish or export when it is ready.
What happens after you send a prompt
Section titled “What happens after you send a prompt”When you submit a prompt, Vibecade:
- interprets your request
- updates the game project
- runs the project in a cloud workspace
- streams progress into the chat
- shows the result in the preview
You do not need to wait until the end to understand what is happening. The workspace surfaces the build as it evolves.
The four parts of the workspace
Section titled “The four parts of the workspace”Use chat to tell Vibecade what to build next, what to fix, and what to preserve.
Preview
Section titled “Preview”The preview shows the running game. This is the fastest place to judge feel, controls, UI, pacing, and bugs.
The file panel lets you inspect the generated project. You can use it to understand structure, verify assets, or spot obvious mistakes.
The logs help you understand runtime issues. If the preview is blank or broken, the logs often explain why.
How iteration works
Section titled “How iteration works”The first turn is rarely the last turn. The best Vibecade projects improve through a series of targeted follow-ups:
- tighten movement
- change art direction
- add progression
- rebalance difficulty
- polish menus and HUD
- clean up bugs
The more specific your follow-up, the better the next result tends to be.
Saving and reopening
Section titled “Saving and reopening”Vibecade saves your project as you work, so you can reopen it later from My Projects and continue where you left off.
This makes Vibecade useful for:
- fast prototypes in one sitting
- longer builds that take multiple sessions
- returning to a public game after feedback
Sharing and shipping
Section titled “Sharing and shipping”Once a game is working well, you can:
- publish a web version and share a link
- keep the project public for discovery
- switch eligible projects to private on paid plans
- export for desktop
- export for mobile
For more detail, see Publish and Share.