Design in code, review together.
Build with any AI.Review it like real product work.
Forge is a Git-native workspace that turns raw AI-built prototypes into clean, version-controlled releases stakeholders can actually review.
- Models
- Claude Code, Codex, or anything local. Picked per task, swapped without ceremony.
- Truth
- Your repository. Forge never grows a database of record behind your back.
- Reviewers
- They open a link. No installs, no seats to buy, no tools to teach.
01 The shift
Design moved into code. The review system stayed behind.
Teams that prototype with AI gain executable interfaces — and lose the things a design file quietly provided: shared context, structured feedback, an approval that means something. Forge rebuilds that system where the work actually lives now. The repository.
02 The loop
An opinionated loop, not another agent terminal.
Forge guides work through a lifecycle. Every step leaves a record in the repo — one a teammate can read six months later and still understand why it looks the way it does.
01Frame
Capture the problem, the constraints, and the supporting material as files in the repo, next to the interfaces they describe.
02Explore
Take competing directions onto their own branches and build each with your agent. They stay side by side as real, runnable interfaces — you compare working screens, not thumbnails.
03Check
Run quality checks before anyone outside the team sees the work, so stakeholders review the design, not the typos.
04Freeze
Pin an exact, immutable version. What reviewers see never shifts underneath their comments.
05Review
Publish a guided review. Stakeholders comment on real screens, real states, and real flows — from a link, with nothing to install.
06Resolve
Triage feedback into decisions and tasks, execute the accepted ones locally with any model, and show every reviewer what happened to their comment.
03 Spoken here
Git underneath. Design language on top.
Designers shouldn’t need Git internals to keep a defensible record. Forge runs the standard mechanics and names them after the work.
04 Forge Cloud
The repo stays home. The review goes out.
Forge Cloud hosts the one part of the process that needs other people. You publish a frozen version; a stakeholder opens a link, types the six digits you sent them, and comments on the actual screen. Their words come back into your repository as feedback you can triage — and when you address one, the next version tells them so.
Stays on your machine
- Source code and Git history
- Your coding agent and its credentials
- Artifacts, todos, and decisions
- Building and freezing a version
- Exported review history
Runs in Forge Cloud
- Hosted review rooms
- Invited reviewers, PIN-gated
- Pinpoint comments and threads
- The resolution trail back to each reviewer
05 Downstream
Engineers receive a repository, not a redline.
When a version is approved, Forge prepares the handoff from the repo itself: the exact checkpoint, a component inventory, scenario and seed data, the observed data model, every decision with its reasoning, and the questions that remain open. Developers consume it through Git — no Forge account, no new portal.
06 The method
Opinions, written down.
Automation proposes before it promotes.
Human decisions are explicit.
Every reviewed version is immutable.