The chat is not the workspace. The canvas is.

Scrollback is not a project

Ask an AI to build you something and it answers in a column. Reply, and the answer moves up. Reply again and the first thing it told you is somewhere above the fold, in a conversation that now has two versions of the same file in it and no way to tell which one is real. The interface is a transcript. You are trying to build a thing that has parts.

This is the quiet reason so many AI builds stall at the demo. Not the model. The shape of the window. A chat is superb at one question and increasingly poor at the twentieth, because nothing in it holds still while you think.

Put it on a canvas

GridFlow takes the conversation out of the column and puts the work on an infinite canvas. Pieces sit where you left them. You can look at two parts of the same build at once, which sounds obvious until you notice no chat window has ever let you do it.

It is not a vibe coder, and the distinction matters more than it sounds. A vibe coder produces something that looks like an app in a video. GridFlow is aimed at the far duller and far more valuable moment two weeks later, when you need to change one thing and not break the other four.

A transcript is a record of what you decided. A canvas is where you decide it.

Previews that run on an actual machine

What you build gets a live preview on a real sandbox with its own address, not an emulator pretending inside your browser tab. Real install, real server, real URL you can send to somebody. The gap between "it works here" and "it works" is where most demos quietly die, and closing it is worth more than any amount of polish on the editor.

Not every job deserves the expensive model

Here is the part almost nobody builds, because it is invisible when it works. Most tools route every request to one large model. That means you pay reasoning prices to rename a file, and you get a design suggestion from something optimised for logic.

GridFlow routes by the job. Design questions go to the model with taste. Logic goes to the model that reasons. Housekeeping goes to the small fast one, because moving a file is not a philosophical act. You are not asked to pick, and you are not billed for the difference. It just costs less to run, and the savings are the reason the free tier can exist at all.

Sessions are the unit, not tokens, so the meter is something you can hold in your head. A full turn is one. Small file work is a quarter. Five are free, no card, which is enough to find out whether the canvas suits how you think before anyone asks you for money.

Where it sits in the network

One QOL ID opens it, the same login as everything else here. There is a plugin shop rather than a feature roadmap you have to wait on, and a full CMS layer for the people who want the thing they built to be editable by someone who is not them.

It is new. It is open. The canvas is the argument.