DocumentationCI/CD integration

CI/CD integration

Begin with read-only review output. Add write access only after the team understands the task boundaries, credentials, and failure behavior.

03 sections6 min readUpdated for preview
On this page
  1. 01Emit machine-readable output
  2. 02Keep credentials scoped
  3. 03Graduate write access slowly
01

Emit machine-readable output

Use JSON output, an explicit working directory, and finite turn and wall-clock limits so a CI runner can capture a deterministic result.

Command
buildstax --json --cwd . --permission-mode plan --max-turns 6 --wall-budget 120 "Review this diff for regressions and missing tests."
02

Keep credentials scoped

Provide the model key through the CI secret store, use --api-key-env when the variable has a custom name, and avoid exposing the value in arguments or logs.

03

Graduate write access slowly

A safe progression is read-only review, then patch generation on a temporary branch, then normal tests and human approval. Do not grant merge permission to the agent.