Build

oluso build is an autonomous run whose task is to scaffold or build what you describe. It uses the same session, sandbox, wallet, and budgets as Autonomous mode. The coding session is still oluso with no command.

Command

oluso build "A small notes CLI in TypeScript"
oluso build "Add a /health route and wire it to the server" --max-iterations 12

The description is required. Flags are the same as oluso goal: --model, --mode, --thinking, --target, --scope, --by, --statement, --yes, --max-iterations (default 24), --max-tokens, and --max-spend. Stderr starts with build · Oluso Swift unless you changed the model.

What it does

1. Writes and edits files with write and edit.
2. Installs dependencies with the workspace shell (bash).
3. Runs a build or a test.
4. Reads the output and repeats until that command exits 0, or a budget, the wallet, or Ctrl+C stops the run.

The workspace the tools see is the session sandbox. When the session ends, those files are copied back to the project directory. A Docker session copies them out of the container. Without Docker, the local workspace is copied back the same way. node_modules is not part of that copy.

When it may finish

finish is refused until some bash command has exited 0 and its text includes test, build, lint, typecheck, compile, tsc, or jest. The refusal is Finish is waiting on a green build or test. Run a command that includes test, build, lint, typecheck, compile, tsc, or jest and exits 0. If there is nothing to build or test, the agent calls blocked instead. The stop line then starts with Blocked.

A successful run prints Build met on iteration N. <summary> and exits 0. The other stop lines and exit codes match Autonomous mode.