DocumentationAgents and tasks

Agents and tasks

BuildStax treats a task as a bounded loop: gather context, choose a tool, observe the result, and stop when the requested outcome is proven or blocked.

03 sections6 min readUpdated for preview
On this page
  1. 01One-shot, REPL, or TUI
  2. 02Sessions are repository-scoped
  3. 03Bound the loop
01

One-shot, REPL, or TUI

A one-shot query is easiest to automate. The REPL keeps context across prompts. The TUI adds navigation and status views while using the same runtime underneath.

02

Sessions are repository-scoped

Transcripts and resumable sessions are tied to the working directory. List sessions for the current repository or provide a different root explicitly.

Command
buildstax sessions
buildstax sessions --cwd ./app --json
buildstax --resume last "continue with the focused test failure"
03

Bound the loop

Use --max-turns and --wall-budget when predictable execution matters. A bounded task should end with a result, a verification failure, or a clear blocker.