Describe The Site. Then Read What It Wrote.
Forge is the site builder inside your dashboard: a chat on the left, your project's real files in the middle, and a live preview on the right. It writes Next.js, wired to your own backend, and it shows you every line before anything goes out.
Three Steps, And You See All Three
This is the whole loop. There is no stage where the tool goes quiet and comes back with a finished website you have to take on trust.
Say What You Want
In a sentence, not a ticket. A page, a section, a change to something already there. You can set how much effort a run should spend before you send it.
Watch It Work
The file tree moves as files are written, the console prints the build, and the preview reloads on the result. Nothing happens behind a spinner.
Read It, Then Publish
Open the diff in the editor. If it is right, publish, and the site goes out. If it is not, say so in the next message and the change is one more commit.
A Workspace, Not A Prompt Box
Forge takes the whole window, because a chat, an editor, a file tree and a running preview do not fit beside a sidebar. Six panels sit behind the preview, and each one answers a question you would otherwise leave the tool to answer.
Files
The project's real tree. Open anything, read it, edit it by hand where that is faster than asking.
Console
Install and build output as it happens, so a failure is a message you can read rather than a red state.
History
Every run is a commit with a message. Look back at what changed and when it changed.
Routes
The site as a graph of its pages, which is the fastest way to notice the one you forgot to build.
Branding
Your colours, type and radius as CSS variables the generated code already reads from.
Security
What the project is allowed to reach, and which keys it holds, in a panel rather than in a file somewhere.
It Writes Into A Project You Keep
Not a page in somebody’s builder that exports to HTML at the end.
What Forge edits is an ordinary Next.js App Router project using the same SDK you would install by hand, against the same backend your dashboard runs on. The catalog it renders is your catalog. The orders it takes are the orders in your orders screen.
Every run lands as a commit, so the history is a history rather than a series of overwrites, and the code is the thing you take with you if you ever decide to finish it in your own editor. Nothing about the project depends on Forge continuing to exist.
What that leaves you owningThree Things It Will Not Do Behind You
An agent with write access to your site is only worth having if you can say what it is not allowed to do on its own.
Nothing Is Silent
Every change is a commit with a message, in a history you can read back.
Nothing Runs Unmetered
The allowance is shown before a run starts, per organization, on the plan you are on.
Nothing Publishes Itself
A build is not a deploy. The site goes out when you press publish, and not before.
What This Page Is Not Promising
The useful version of this claim, rather than the flattering one.
Forge does not remove the need to look at what was built. It writes code that compiles and it shows you the result, and it will still get a layout wrong, name something oddly, or solve the request you typed rather than the one you meant. Reading the diff is part of the loop, not an optional step for careful people.
It is also not a replacement for a designer. It will build the site you describe, at the quality of the description, which is why the fastest way to a good result is knowing what you want on the screen before you ask for it.
Open It And Ask For A Page.
Forge lives at /dashboard/website. Create an organization, take your keys, and describe the first page out loud.
Forge is metered per organization. The dashboard shows the remaining allowance before a run starts, and what a plan includes is on the pricing page.