How the assistant builds your app

When you send a request, the assistant doesn't write random code and hope it works. Instead, it follows a methodology that mirrors what a professional engineer does: understand, plan, execute, verify, and repair. Understanding this cycle helps you track its work and trust the result.

Smart routing

First, the assistant assesses your request: is it a simple task (small change) or complex (full feature)? Based on that, it chooses the right approach — direct execution for the simple, detailed planning for the complex. This balances speed and quality and saves your credits.

The manageable plan

For large tasks, the assistant creates a plan broken into numbered steps and shows them to you. You can follow each step's status as it moves from "pending" to "in progress" to "completed". If you need to, you can defer a step and resume it later — the work is organized and transparent, not a black box.

Project Doc during the build

With the first build request for a new project, Codey automatically creates a Project Doc in the web workspace. The specification fills in section by section alongside execution: features, planned images, and visual direction appear first, then the project's actual images and identity replace the early concept — without holding up the build.

Live execution

During execution, you see the assistant work moment by moment in the chat: which file it's writing, which tool it's using. You don't have to follow the details, but they're available if you want to understand what's happening.

Self-repair

This is one of the platform's most powerful features. After writing code, the assistant verifies that the app builds successfully. If an error appears, it reads it, understands it, and fixes it itself — then verifies again. All of this happens automatically before you see the result, so what you see in the preview works.