Chat

Chat is the front door to Pikku Studio Cloud. Not a step you pass through on the way to building, and not a command line with better manners — it's where you stay. You talk, it decides, and work starts happening behind it while you're still talking.

Annotated screenshot of the builder Chat: a conversation on the left where the assistant states a consequence, states a decision it has already made, and asks a single question rendered as a card with two labelled options. A "Milestones" tab beside it shows one milestone building. Callout: "One question at a time — and the answers are already written down."

It decides; you correct it

Most tools that plan an app ask you to specify it. That means asking you to know things you've never had to think about — and the vague answers you give are the vague app you get.

Chat works the other way round. It makes the decisions and shows you them being made, so your job is the much easier one of saying "no, not that". A turn looks like this:

1. What your answer implies — one line, drawing out the consequence rather than repeating what you said.
2. What it's decided — one or two calls, phrased as already made, and always reversible.
3. One question — exactly one. When the answers can be named, they arrive as a card you click rather than a prompt you type into.

There's no plan document to approve at the end. Each decision is settled as it comes up, and each one is written down the moment it's made.

Everything lands in the knowledge base

Chat writes to your project's knowledge base — and that's all it writes. It cannot touch your app's code. That isn't a safety rail bolted on, it's the division of labour: this conversation interviews and records, and the build agent writes the code from what it recorded.

Which is why the record can be trusted. There's no separate summary that could drift from what was actually decided.

It starts building without asking

There's no Build button. When the conversation has settled enough for a milestone to be real, it gets written down and dispatched to the builder in the background, and you get one plain sentence saying so.

The conversation doesn't pause for it. You'll be answering questions about the fourth milestone while the first is already on screen — and you can ask how a build is going at any point.

The one thing you're asked before a milestone is built is whether you want to see the screen first. Yes gets you a couple of real sketched options in the Design tab to choose between; "just build it" skips straight to building.

Three conversations, one of them yours

Behind the tab strip there are actually three conversations, and the console groups the other two under "Chat drives these":

	What it is	What it writes
Chat	The interview. Where you live.	The knowledge base
Build	Builds a dispatched milestone	Your app's code
Design	Sketches screen options before a milestone is built	Screen sketches

They run at the same time, each in its own session, so building never blocks talking.

You can open Build or Design by hand — it's occasionally useful to watch, or to nudge a build directly. But they're deliberately secondary, and there's a real cost to driving one yourself: while you're occupying a session, a dispatch that lands comes back busy with nothing done. If you're not sure which to use, use Chat.

Ask it anything, not just for changes

It reads your actual project, so it answers as well as builds:

• "How does my signup flow work right now?"
• "Why did we decide only owners can delete a booking?"
• "How's the build going?"

That last one is answered from the real build, not from what it remembers dispatching — a build that's stuck looks exactly like a build that's fine if all you read is your own notes.

If you change your mind

Say so. Everything lands in a private sandbox that has no route to your live app, so there's no risk in changing direction. Decisions are recorded as reversible, and reversing one is a sentence.

"Done" always means it was built. A decision recorded in the knowledge base is a decision recorded — the app hasn't changed yet, and Chat will tell you which of the two just happened.

It speaks your language

If you're working in another language, Chat holds the whole conversation in it — replies, questions, and the options on every card. What gets written down stays in English, because those notes are the brief handed to the builder and the tests generated from them. You read your language; the machinery reads its own.

Where to go next

• Knowledge — the record every decision lands in.
• Milestones — how a conversation becomes working software.
• App preview — watch what you asked for actually run.
• Publishing — the separate step that takes it live.