Talk or code: the same project.

Two ways to build

Not everyone wants to see the code. And those who do don't always want to write all of it. Qwanter has two ways of working, one for each case, and you don't have to choose forever.

Vibecoding: describe it and watch it grow

This is the way to build today, and it arrives with the invite-only private beta. You describe what you want, Core plans it, Build builds and verifies it, and you keep improving it through the conversation.

• You type or dictate. Dictation works locally.
• You see the preview inside the app.
• You have versions and can undo.
• You see what it costs on every turn.

High-Tech: the professional IDE

It will arrive with Qwanter 2, after the MVP. It's a professional development environment inside Qwanter, for those who want full control: editing code by hand, reviewing every change the agent makes and working on their own repository, with the agent alongside.

What they share

Both ways work on the same project. The code lives in your repository and the project memory in its qwanter/ folder: the brief, the brand and the decisions you've already made. There's nothing to export to move from one to the other.

An example: a café owner asks Qwanter for a website with a menu and bookings, just by talking. Months later, a developer opens that same project in High-Tech, reviews the booking code and accepts an improvement the agent suggests. It's the same project and nothing has been lost.

Illustrative example · not a real case

Your code is always yours

Whichever way you use, the code is in your repository. You can open it in your editor, take it with you or carry on without Qwanter. What comes next is on the roadmap.