forgev0.19
Docs pages

How forge works

A forge run is a route from your goal to reviewed code on your branch. Every station below is a page of these docs. Pick one to see what happens there, what you control, and the command that drives it.

Installnpm Plantasks Approvethe table Builddwarves Reviewqa reads Retryfindings Mergeverify Integrate--approved Memory.forge/ Steercontrol forge-uiwatch it Measuredataset

Solid lines are the run itself; dashed lines are what you can do beside it. Press a station, or use Tab and Enter. Esc clears the route.

The words forge uses

goal
What you want done, in your own words, after /forge.
run
One trip from a goal to reviewed code, with a folder of records.
task
A piece of the goal. A small goal is one task.
dwarf
The model that builds a task. You pick it with --dwarf.
qa
The model that reviews a task's diff. --qa; opus if you don't say.
finding
A problem the reviewer found: P0 data loss, security or crash, P1 wrong on realistic input, P2 an edge case, P3 minor.
wave
Tasks that can run at the same time because they don't share files.
harness
An agent CLI forge sends work through: codex, claude, openclaude, opencode, antigravity or grok.
spec
How you name a model: alias:effort:harness, like sol:xhigh:codex.

Every page

Start and run

During and after

Reference

Full reference Every flag and edge case: docs/README.md