Skip to main content
You describe an app in one message. The built-in Build an App workflow turns it into a Forge project with a Go API, a Postgres schema and a Next.js frontend, gets its checks green, has a separate agent review the running app, and leaves it running on your machine. The result is ordinary code in your folder that you review, commit and deploy. The checks are Forge’s own: 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 doctor checks them.
  • A forge command on your PATH, 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, reliant workflow run takes the built-in by its id, forge-one-shot:
terminal
Output
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. 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)
The whole build is one Get It Right loop, up to 7 iterations. In each iteration the workflow’s brief tells the agent to:
  1. Write FORGE_PLAN.md: entities, fields, pages and style. The gate fails while it is missing.
  2. Run reliant forge project new --in-place, write each entity as a // forge:entity proto message and run reliant forge scaffold.
  3. Read the migrations Forge drafted and correct types, nullability, UNIQUE and CHECK constraints and foreign keys, then seed the dev database once to prove a row the schema allows is one the API accepts.
  4. Bring generate, lint, task test and build green before any feature work.
  5. 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.
The engine then runs the checks itself, and a separate reviewer starts the app and judges it; a failing check overrides a passing review. The run above passed on its first iteration, in about 30 minutes. A last step runs 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:
readinglist/ (trimmed)
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:
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:
terminal
Output
Start the stack and look at the seeded data:
terminal
Output (trimmed)
Open the 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

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.
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.
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