Notes on AIVA Agent

We made AIVA Agent for a narrow habit: you describe an app in normal words, you see it run while you wait, you ship it when it feels right. No repository tour first. No config wall before the first screen.

Open the workspace and say what you want—a landing page, a small internal tool, a page you would have scribbled on the back of a receipt. The preview is a real build, not a picture of one. When the layout or copy is off, you say so in the same thread and it adjusts. Publish when you are done; the project lands on yourname.aiva-agent.com. Hand that link to whoever needs to click it.

Where it fits

Good for starting from zero, for one-person products, for demos you need tomorrow. Handy when you would rather argue about copy and flow than about folder structure.

Less handy when you already have a large codebase, hard compliance rules, or a team that lives in pull requests. Those setups still want their own pipeline. We are not trying to replace that.

Accounts

Google or X login is there if you want projects tied to a profile. You can build without it; login mainly matters when you care about history and publish records showing up in one place.

When something breaks

Previews run in hosted dev environments. They time out. A tab left open too long may show an empty frame—refresh and run the build again. Long generations can drop if the connection hiccups; retry the prompt. Annoying, ordinary, fixable.

If you only remember one line: describe the app, watch it form, publish the link. Everything else is detail around that loop.