FORGE
FORGE
2026 Open the workbench

01

FORGE out loud

Describe what you are building, out loud. FORGE asks what it needs to know, proposes a shape you can turn around on screen, and keeps the reasoning behind every decision.

02

Say it, and turn it around

Hold the space bar and describe the part. FORGE builds geometry you can rotate, section, explode and measure while you are still talking about it — and you can cut it off mid-sentence when it has taken the wrong idea.

In the room Speak, or type instead — every step has a path that does not need your voice. Interrupt whenever you like. It stops talking and keeps the work. Every dimension carries its units, its frame, and where the number came from.

03

It asks before it guesses

An ambiguous goal gets a question, not a confident wrong answer. FORGE draws out the constraints it is missing, offers you options that are actually different from each other, and says so when it thinks you are wrong.

Before anything runs Options come with the tradeoffs, and with the criteria that separate them. You can turn the arguing down. You cannot turn off dissent about safety. Where a tool has no real backend the call fails by name, rather than returning a plausible number.

04

You see what actually happened

Every change carries who asked for it, which tool made it, what it changed, whether anything checked it, and whether a person accepted it. Nothing irreversible happens while you are not looking.

Under your hand Read, write, execute, simulate, export, deploy, transact and control are granted separately. Anything irreversible waits for a named person to approve it. Finished, checked and accepted are three different words here, and it uses them that way.

05

Close it, and come back

Shut the laptop in the middle of a task. FORGE picks up from where the work actually got to, not from a summary of what was said about it — which is how an agent quietly loses an afternoon. A durable engineering partner, in the sense that it is still there tomorrow.

What survives A crash costs at most one step of the work, never the task. Tool output is kept exactly as it came back, so the evidence outlives the conversation. Pick it up on another machine; the project is the record, not the session.