generate, lint, build and task test. Forge derives the wiring from the proto and the migrations (Two sources of truth), so the agents write the domain.
Before you begin
- Reliant v1.21.3 or later, signed in (Sign in and tokens), with a connected machine (Run a machine from the terminal).
- Go, Node.js and Docker on that machine.
reliant forge project doctorchecks them. - A
forgecommand on yourPATH, if you will run the stack yourself afterwards; see Troubleshooting. - An empty folder for the project. The workflow creates the project in place.
- Model credit: a run takes tens of minutes on a flagship model, with up to six sub-agents at once. In an organization, a run asks before it moves to your own AI account (
reliant workflow funding).
1
Start the workflow
In the app, open a new chat, choose Build an App in the workflow selector and send your description. From the terminal, In a chat, the agent may ask about the data model and the look before it writes its plan, and the run pauses after each iteration for your review.
reliant workflow run takes the built-in by its id, forge-one-shot:terminal
Output
unattended=true says no one is there, so the agent decides instead of asking. The run is listed under Runs in the app.2
Follow the run
terminal
Output (trimmed)
- Write
FORGE_PLAN.md: entities, fields, pages and style. The gate fails while it is missing. - Run
reliant forge project new --in-place, write each entity as a// forge:entityproto message and runreliant forge scaffold. - Read the migrations Forge drafted and correct types, nullability,
UNIQUEandCHECKconstraints and foreign keys, then seed the dev database once to prove a row the schema allows is one the API accepts. - Bring
generate,lint,task testandbuildgreen before any feature work. - Fan out one sub-agent per part of the app (an entity’s pages, a backend concern, the dashboard), six at a time, then integrate their work and run the gate again.
reliant forge env up dev, posts the app’s link from reliant preview-url, and the chat becomes an ordinary agent chat.3
Read what it built
The folder is a complete Forge project. From the one-sentence prompt above:Every book belongs to the signed-in user, and a test checks one user cannot read another’s list. A call without a token is refused:
readinglist/ (trimmed)
ListBooks response
4
Verify it yourself
The run leaves the app running. Stop it, then check the code with the same tools the gate used:Start the stack and look at the seeded data:Open the
terminal
Output
terminal
Output (trimmed)
web URL, and run reliant forge env down dev when you are done.5
Review and commit
The workflow creates a git repository but commits nothing. Read
FORGE_PLAN.md and the code, then commit. To extend it, add a table or ask in the same chat.What this does not do
- It does not deploy. The app runs on your machine only. Deploy it with Deploy a Go API with managed Postgres, or say “Deploy it.” in the same chat, which is now an ordinary agent chat.
- It does not commit or open a pull request.
- A pass means the checks are green and the reviewer found the plan’s high-priority features working. Lower-priority features and hardening findings (error handling, validation, tests) are recorded in the review, not required to pass.
- The “Build an app” button on the Apps page and the home screen is something else. It opens an ordinary agent chat with a starter prompt that asks the agent to build and deploy. Choose the workflow in the selector to get the loop on this page.
Troubleshooting
Didn't Fully Pass
Didn't Fully Pass
The loop used all 7 iterations without a pass. The project stays in the folder, and the reviewer’s last feedback names what is missing.
Stopped — External Issue
Stopped — External Issue
The blocker was tooling or the environment, such as an app that would not start. Run
reliant forge project doctor and reliant forge env up dev in the project to see it.forge: not found in .forge/logs/dev/api.log
forge: not found in .forge/logs/dev/api.log
The API’s hot-reload config calls
forge by name. If you only have reliant forge, put a two-line script named forge on your PATH that runs exec reliant forge "$@", then start the stack again.Next steps
Build a Go and React app by hand
The same kind of project, one command at a time
Deploy a Go API with managed Postgres
Put the app on a URL
How forge generate works
What Forge writes from the proto and the migrations
Get It Right
The loop this workflow runs