Editor Overview
The Vibecade editor is built around a single project workspace. You do not need to jump between separate apps to build, test, and share your game.
Chat is where you direct the build.
Use it to:
- create the first version
- ask for design and gameplay changes
- fix bugs
- request polish
- continue a project over multiple sessions
Empty chats can suggest starting prompts, and completed turns can suggest useful next actions.
Live preview
Section titled “Live preview”The preview shows your running game.
Use it to judge:
- movement feel
- combat
- menus
- difficulty
- visual readability
- layout on different screen sizes
If the preview reloads during active work, that is normal. The project is being updated.
The file panel shows the generated project. You can use it to:
- understand how the game is structured
- inspect assets and source files
- verify that a requested change actually landed
You do not need to read code to use Vibecade well, but the option is there when you want more control.
The logs surface runtime output and build errors. They are useful when:
- the preview is blank
- the game freezes
- a recent change caused a bug
- you want a clue about what failed
Model and build controls
Section titled “Model and build controls”From the editor you can also:
- switch models
- adjust reasoning on supported models
- use voice input in supported browsers
- attach reference images on supported models
- publish when the game is ready
- export for desktop or mobile
A simple way to use the workspace
Section titled “A simple way to use the workspace”If you are new, this sequence works well:
- Prompt in chat.
- Play the preview.
- Check logs only if something looks wrong.
- Use files only when you want to inspect details.
- Repeat until the game is ready to publish.