Build
Execute a build plan inside a Docker container.
The build domain is the headless execution surface: a plan file (the output of the planning cycle) is walked task-by-task by an AI agent inside the isolated goga container, with an optional external review pass. Which tasks it solves:
- Run plans unattended —
goga build plan.mdprepares the environment, validates preconditions (Docker, config, agent wrappers), and delegates to the build engine running in-container. - Keep state persistent — the build state survives across runs of the same plan on the same branch;
--cleanwipes it for a fresh run. - Separate the reviewer from the executor —
build.review_executorconfigures a second agent (and an env layer) for the review pass: the build runs tasks with one wrapper, then the review with another. - Scope the review diff —
base_refoverrides the review's default-branch detection;patiencestops the external review after N unchanged rounds.
The interactive, stage-by-stage counterpart of this domain is Pipelines; the SDD cycle that produces the plans is covered in Workflow.
In this directory
- CLI — the full
goga buildcommand reference - Configuration — the
build:section of.goga/config.yml - Hooks — hook points for tool packages
- API — the
goga.buildpackage facade